A world in flux
12½ years ago, in February 2001, 17 software developers met in Snowbird, Utah and formulated the manifesto for Agile Development:
“We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more
(presented in bold).”
In this edition of Best Practice we focus on the subject of Scrum, the most popular and most commonly used agile method – a process tool and project method gaining ground everywhere.
There are unmistakable advantages in using this method and we will try to highlight some of these. Unlike ”the good old”
waterfall method, Scrum is tailored to a world which is in constant motion, where predictability is a foreign concept and where businesses and IT projects must be adaptable, scalable and quickly able to change focus and functionality.
Like all other processes and methods the Scrum model however, also has its limita-tions and should be used in the correct context on the right projects. Processes for the sake of the process, methods for the sake of methods, have never produced results. Orthodoxy and bigotry have never contributed to sustained progress and results – only imagination and freedom has achieved that.