Agile is a popular software development methodology use today. Scrum and eXtreme Programing (XP) are two types of agile methodology. Sutherland (in Lacey 2012) states that 75% of the agile software development use Scrum framework and around 17% of the scrum team use XP engineering practices. Scrum framework looks extremely simple however it is found to be hard to implement effectively.
Scrum is a lightweight and simple process framework used for developing complex products. It is not a process, methodology or engineering practices.
Scrum is a lightweight and simple process framework used for developing complex products. It is not a process, methodology or engineering practices.
Scrum's 5 Core Values
- Focus
- Respect
- Commitment
- Courage
- Openess
Scrum Project Roles
- Scrum master - The scrum master works as a facilitator of the team. He ensures that the team is functioning as expected.
- Product owner - The product owners is the person who drives the project.
- Scrum Team - Team who actually do the development.
Scrum Artifacts
- Product backlog - This artifact consists of all the select requirements that need to be met. The requirements are sorted according to its priority.
- Sprint backlog - The requirements stated in the product backlog is grouped into Sprints so that it can be completed in 2-4 weeks. This artifact consists of the requirements that is to be met on a particular sprint
- Burndown chart - This chart provides the current status snapshot during a scrum project. It shows amount of work that needs to be completed and the time remaining. In 2011, it was agreed that burndown charts are not mandatory artifacts.
Scrum Meeting
- Release planning - This meeting is carried out before starting a sprint. For that sprint that is n weeks long requires n x 2 hrs of release planning.
- Daily Scrum meeting - This is 15 minute stand-up meeting that is carried out daily at the start of day. The purpose of the meeting is to facilitate free communication and understandings among team members. Three important questions discussed by each team members are:
- - What I did yesterday?
- - What I will do today?
- - What are possible obstacles that I face today?
- Sprint Review - This meeting is conducted after the completion of a sprint. In this meeting the client feedback is the most important. In other words, client is expected to approve the product released.
- Spring Retrospective - This meeting is more internal to the Scrum team and product owner is kept out of this meeting. Possible questions addressed in this meeting are:
- - What went well in last sprint?
- - What needs improvement?
References
- Lacey M 2012, The Scrum Field Guide, Practical advice for your first year, Addison-Wesley. Foreword by Jeff Sutherland.
Comments
Post a Comment