Project management methodology and Software engineering literature and articles flourish and flocks of consultants live from those! Still, overall, projects are late, and software quality remains poor. Do we believe CMMI and PMMI will help improving delivery or quality or are they just a waste of money?
My belief is that software development is about knowledge and in particular about business process knowledge acquisition: a software is the capitalized knowledge on a business process. Software embeds an intimate expertise of the concerned business process with the value proposition to make it more efficient: if you do not believe this, look at most software firms marketing material.
The way software is built reflects this knowledge accumulation. In big corporations, software remains in place for many decades and become so difficult to replace since the whole organization is organized to fit the software (or is it the other way around originally?).
Human beings do not fit traditional methodology and the lifecycle model. Specifications are a snapshot at a given time and within a moving context but delivery happen much later than the original needs in a sometimes drastically different environment.
Also, in real life, a development team does not know its goals and communicate poorly (the bigger the poorer). They risk no penalties for doing things wrong.
With methodology and tools, people build bigger software, not better software.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment