NEWS AT SEI
This library item is related to the following area(s) of work:Software Product Lines
This article was originally published in News at SEI on: February 1, 2005
In 1981 Jack Welch assumed the position of CEO at General Electric (GE). He quickly unveiled an aggressive strategic redirection that transformed GE into 14 distinct businesses focused on three "strategic circles": core manufacturing, technology-intensive businesses, and services. [Tichy 89] He coupled his business overhaul with an initiative to revitalize the work force. He was passionate about his vision, and he relentlessly drove it to completion. But he didn't stay at the vision and strategy level of organizational management; he got involved in GE daily operations. In fact he never hired a chief operating officer (COO) despite the immensity of the enterprise he ran. He interacted directly with GE workers at all levels. He believed in his staff, listened to them, and gave them abundant feedback. He made them part of his solution, and embraced their good ideas. He broke down the walls between managers and subordinates. He was interested not only in his success but in GE's success. He spent years selecting, nurturing, and pruning a set of candidate successors. Welch's innovative strategies and management style transformed GE into a "highly productive, labor-efficient powerhouse with a staggering $200 billion-plus market capitalization." [Slater 98] Under Welch GE soared to the top of the Fortune 500.
My brother has been a high school football coach for over 35 years. His teams have amassed 19 championship and five unbeaten seasons. The high school even named the football stadium after him. He has encyclopedic knowledge of football and athletic ability to match, but it's more than his knowledge and skills that have made him a legend. He does all of the workouts with his team and keeps the training rules he sets for them. He gets to know each player and relentlessly drives them all to achieve their potential and then some. He is always in the game, not just directing it. One season he "fired" more than half of his first-string players for breaking in-season training rules. Despite vehement pressure from parents, the school board, and administrators, he refused to reverse his decision. As a result, the team was purged of its finest talent, and some of the remaining players had to play both offense and defense. He worked tirelessly with the skeleton squad, challenging them and spurring them on. He believed they could succeed, but more importantly, he made them believe they could succeed. And they did; they went to the championship playoffs.
Now what could Jack Welch and my brother possibly have in common? Simple: they are both leaders. And what do leaders have to do with software product lines? Everything: you can't just manage a software product line operation, you have to lead it. Managers control. Leaders spur an emotional energy that fuels an organization to succeed despite downturns and obstacles. Ron Temple led Cummins Engine Co. boldly through turbulence to success with its product line approach for engine-control software. Jaak Urmi did the same for CelsiusTech. In fact, there is a leader behind each story of successful product line adoption that we have studied at the SEI. And of the failed product line efforts we have seen, most either lacked a leader or lost one.
If product line management must lead to succeed, then we ought to take time out to describe the qualities of a leader. We have only to study the role models such as Welch, my brother, Temple, and others. Leaders are
Given these qualities, what do leaders in product line settings do that sets them apart? They
This is a long list that goes beyond what most would call management. Jack Welch refused to call himself a manager. He preferred the term "business leader." To him a leader is a teacher, a cheerleader, and a liberator, not a controller [Tichy 89]. If you are choosing the individual to be at the helm of a product line effort, choose a leader. If you are the person in charge, take heed.
Linda Northrop has over 30 years of experience in the software development field as practitioner, manager, consultant, and educator. She is currently director of the Product Line Systems Program at the Software Engineering Institute (SEI). The Product Line Systems Program works in the areas of software architecture, component, and product line engineering. Her current publications are in the areas of software product lines, software architecture, and object technology. She is co-author of the book, Software Product Lines: Practices and Patterns.
She is a frequently invited speaker at technical and corporate conferences and was featured in a television special on object technology aired by the British Broadcasting Company. Most recently she was a keynote speaker for the International Conference on Software Engineering 2001, the Aspect-Oriented System Development Conference 2002, and was selected as the 2001 Carnegie Science Center Award of Excellence for Information Technology recipient.
Before joining the SEI, she was associated with both the United States Air Force Academy and the State University of New York as professor of computer science, and with both Eastman Kodak and IBM as a software engineer. As a private consultant, she also worked for an assortment of companies covering a wide range of software systems. She chaired the first Software Product Line Conference (SPLC1) in 2000 and SPLC2 in 2002. Linda is the OOPSLA Steering Committee Chair and was OOPSLA 2001 Conference Chair. She is a member of ACM and the IEEE Computer Society, and formerly the Computer Sciences Accreditation Commission.
The views expressed in this article are the author's only and do not represent directly or imply any official position or view of the Software Engineering Institute or Carnegie Mellon University. This article is intended to stimulate further discussion about this topic.
For more information
Please tell us what you
think with this short
(< 5 minute) survey.