Guide to Scrum Core Practices
By Ray Claridge
Being apprehensive prior to joining my first agile scrum team,
I spent many hours surfing the web for some kind of process model (mainly so I knew what I was letting myself into).
Because of the nature of agile/scrum and the fact there are so many different flavours to it, this was more difficult than first thought.
However, with my experience and a little help from the web,
I have managed to put together a list of core practices that make up the scrum process.
Core Scrum practices are:
- Backlog. Product, Release, Sprint Backlog - lists of all requested/required functionality for the product, release and sprint respectively. Product Owner/Manager responsible for the backlog management and maintenance.
- Iterative development.The whole project gets divided into sprints usually 2 to 4 weeks duration each. Sprints have fixed duration to enable regular deliveries and helps development teams to focus on a shippable product in the end of each sprint.
- Scrum meetings. Daily time boxed meetings where team members answers the following questions: What you did yesterday? What has impeded your work? What you plan to do today?
- Burn Down Charts. Scrum Sprint Burn Down chart shows implementation progress during a single sprint. It provides answers on the following questions: When sprint could be completed based on previous progress? What is the most possible scrum team Velocity in future sprints?
- Sprint review meeting. Provides an inspection of project progress at the end of the every Sprint. The goal is to improve development process by introducing new practices, changing existing practices, etc.
0 comments »
Post a Comment