As the start of my new series looking at the basic elements of Scrum, it seems best to start with the end … the end goal. The end goal of Scrum is a team which is smoothly and effectively delivering business value on a regular basis. Some will say that this is the goal of most, if not all, methodologies, but Scrum is the most effective in achieving this goal IMO. As a developer, it is also the methodology which I have found to be the most fun! But more on that later.
Now Scrum is really a pretty simple process to follow and there are a number of resources around on the web which can supply details. What I’m going to try and delve into is not only the basic rules and mechanisms of the process, but I will give you advice from my experience on the things that do and don’t work. As with all advice YMMV. During the series we will be straying into human psychology, communication methods, testing methodologies, user-centred design and a number of other topics that may look unconnected, at first glance.
The basic parts of scrum are:
Some specific further topics which merit some discussion are:
- Burndown charts
- User stories
- Team velocity
- Release planning
- Continuous integration
- Variations on the estimation process
I’ll link from here to my posts, as they’re published.