Empirical process control


While thinking about methods for delivering useful software on the hands of users comes to mind different schools of thought and my conclusion so far is that anyone of them could work, depending exclusively on the skills of the people in the team, of course.


Another significant difference is the cost balance at the end of effort, not just about money but about the shape of what we have in the end in comparison with what we have in the beginning. A development method in a particular project could be delivering software with unacceptable costs in team morale or customer satisfaction.


Empirical process control for the software development process is one of those ideas to try in the search for better cost balance for development projects.


“A new way of thinking and perceiving has to be learned and adopted, and an old way of thinking and perceiving has to be discarded” –Ken Schwaber
http://www.controlchaos.com/scrumorigins.pdf


Take a look.

Comments (0)

Skip to main content