Towards a New Theory — A Look at Scrum
March 27th, 2003 by HalScrum has emerged as one of the leading approaches for delivering software projects on time, on budget, and performing as intended. It is one of a class of methods known as agile development. Koskela and Howell (K&H) take a look at Scrum as an example of a project delivery approach that strays from convention conforming instead to 'new' theory, The Theory of Project Management: Explanation of Novel Methods.
First, I'm no scrum master. I'll do my best with this, but PLEASE correct me in a comment or by email if I've misunderstood.
Scrum
Scrum is a dynamic integrated planning and execution process for delivering software projects. Teams work in highly collaborative ways. They shun the usual practice of detailed up-front requirements analysis and specification writing. Instead, the scrum approach works in one-month intervals — sprints — to deliver a working feature set. One sprint is followed by another until the completed system is delivered.
Tasks are derived and offered up by the performer of the task in daily scrum meetings. The teams' heightened level of communication and coordination more than compensate for the traditional detailed planning and structured work break-down structures.
Theory of the Project
K&H explain the theory of the project operating with this approach as principally flow and value generation. The teams' attention is on producing and delivering what they understand is of value to the customer. Any more than that is not value, particularly when additional features get in the way of completing a feature set that can be put into use. The Scrum approach keeps the team focussed on just one project avoiding multi-tasking and the consequent delays and remobilizations.
Theory of Management
The Scrum approach relies extensively on managing as organizing to set the conditions for the team to conduct themselves while system requirements evolve and they manage development. Effective execution relies on the competence of team members to conduct coordination conversations — language/action perspective. Control is accomplished through continued adjustments learning from one task completion after another. K&H call this the scientific experimentation model.
Comments
Scrum evolved in response to a dissatisfaction with project delays, budget busts, and buggy bloated software. K&H ascribe theory to make sense of how Scrum has been successful. Tomorrow I will offer some summary comments on their paper.
Read more about the agile approach at The Agile Alliance and the Agile Manifesto.
Related Posts
- Scrum and Last Planner™: Novel Methods Explained? Lauri Koskela and Greg Howell expound on Scrum and Last Planner™ as "practical responses to the failure of convent...
- Day Two Daily Scrum Another great day of work. We got through the Daily Scrum in 13 minutes (without standing). I asked for a weekly ret...
- I Hired a Certified ScrumMaster Why would a lean projects guy hire a Scrum software development ScrumMaster? Short answer: it seemed like a good idea...
- Another Scrum Day of Learning We had our first Daily Scrum. It took 16 minutes. I minute too long. Our ScrumMaster asked each of us the 3 Scrum q...
- Towards a New Theory of Project Management The Theory of Project Management: Explanation to Novel Methods After reviewing their argument for calling the underlying...
