I saw the following web site: www.poppendieck.com/overview.htm.
I'm concerned that the Microsoft Solutions Framework and Visual Studio 2005 Team System categorise people into interchangeable "roles" and not as individuals with their own interests and aspirations.
Reducing a project into a series of tasks to be undertaken by an interchangeable "developer" and a series of tasks to be undertaken by a "tester" may seem efficient, but will mean that a developer undertaking a task does not develop an understanding the project and hence ensure it is as good as it can be for its users.
People also feel happier if they are in control of what they are doing, not being controlled. Happier "developers" care about their work and how it affects users.
It's important to know what is going on, but scheduling systems should track both the progress of a project and the progress of people towards their personal objectives, and then help suggest a direction, not control. Control may speed up initial development, but the overall quality will fall, leading to greater testing and support costs later.
No comments:
Post a Comment