10.1.1.96.6671 - focus Project management style is a...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
40 IEEE SOFTWARE Published by the IEEE Computer Society 0740-7459/05/$20.00 © 2005 IEEE Most software professionals have no laws of physics or properties of materials to constrain their problems or solutions. They are bound only by human imagina- tion, economic constraints, and platform performance. (Some embedded-software developers are an occasional exception.) In a software project, you can change al- most anything at any time: plans, people, funding, milestones, requirements, de- signs, and tests. Requirements—probably the most misused word in our industry— rarely describe anything that is truly re- quired. Nearly everything is negotiable. Metrics and measures for software prod- ucts have no atomic units and are highly subjective. Economic performance more typical in service industries (measured by a user’s perceived value rather than the cost of production) has proven to be the best measure of success for software. These observations probably sound counter- cultural to project managers who use engineer- ing mindsets to produce airplanes, bridges, heart transplant valves, nuclear reactors, sky- scrapers, and satellites (unless these projects in- clude significant software content or are first- of-a-kind systems). However, they do apply to movie producers—professionals who regularly create a unique and complex web of intellectual property limited only by vision and creativity. I prefer to describe software management as a discipline of software economics rather than software engineering . Software projects are rarely concerned with established and mature engineering tenets. Rather, a software manager’s day-to-day decisions (like those of movie pro- ducers) are dominated by value judgments, cost trade-offs, human factors, macro-economic trends, technology trends, market strength, and timing. To deal with these more subjective deci- sions, I recommend using a steering leadership focus Successful Software Management Style: Steering and Balance S oftware project managers are more likely to succeed if they use techniques that are more like managing a movie production than an engineering production. “Heresy!” some might shout. “Software projects need more disciplined engineering management, not less.” Before you dismiss my claim as an insult to the profession, consider these observations (a related discussion appears elsewhere 1 ): project management Walker Royce, IBM Software Group Project management style is a significant determinant separating successful projects from failures. Contrary to conventional wisdom, steering leadership is better than detailed plan-and-track leadership.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
style that comprises active management involve- ment and frequent course correction. An iterative approach The economic performance of software projects is difficult to capture in one simple metric, but in the last five years, approxi- mately one in three has delivered on budget and on schedule with any sort of predictabil- ity. 2 I suspect the economic performance of movie productions looks pretty similar.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/22/2011 for the course ITC 101 taught by Professor Cuibap during the Three '11 term at Charles Sturt University.

Page1 / 8

10.1.1.96.6671 - focus Project management style is a...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online