What Are Agile & Scrum?
Agile is an umbrella term used to describe a general approach to software development. Though there are many agile incarnations, all agile processes, including Scrum emphasize teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change.
This post talks about the basic elements of Scrum, and a little understanding for a team to get started with Scrum Model for their project development.
Elements of Scrum
Sprint
A sprint or an iteration is the basic unit of development in scrum, which generally lasts for a period of 2-4 weeks (decided in advance). At the end of the sprint, the team is able to deliver an integral unit of the product which is potentially shippable.
ROLES
Scrum Master
The scrum master organizes scrum events, helps remove any impediments, helps maintain scrum principles in the team.
Development Team
The development team is responsible for developing the product. The size of the team must be 7 ± 2.
Product Owner
The Product Owner writes user stories, communicates with stakeholders to understand business needs, and maintains the product backlog in order of priority.
SCRUM CEREMONIES
Sprint Planning
During Sprint Planning, the team commits to the work to be done in a sprint. In exchange, the Product Owner agrees not to change the scope of the work expected of the team during the sprint. When the team makes this "deal", it empowers the team to take ownership over the sprint and its success. A Scrum team should be committed to the success of the sprint, willing to do whatever it can to carry it out effectively.
Sprint Retrospective
A sprint retrospective meeting is facilitated by the Scrum Master. The team reflects on their practice, congratulates each other on their successes, and refocuses themselves on any improvements they can make. Two main questions are asked in the sprint retrospective: What went well during the sprint? What could be improved in the next sprint?
Sprint Review
In a sprint review meet, the team reviews the work that was completed, and plans for the remaining work. It is demonstrated to the stake holders.
Daily Scrum Meeting (Stand-up Call)
This event occurs daily for 15 minutes where each of the member of the team shares their status (What did I do yesterday, What will I do today and impediments, if any). It is facilitated by the scrum master, who also notes and helps in resolving the impediments.
Backlog Grooming Meeting
It is also called as Backlog refinement. It is the ongoing process of reviewing product backlog items and checking that they are appropriately prioritized and prepared in a way that makes them clear and executable for teams once they enter sprints via the sprint planning activity.
SCRUM ARTIFACTS
Product Backlog
The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed. Items added to a backlog are commonly written in story format (called user stories).
Agile is an umbrella term used to describe a general approach to software development. Though there are many agile incarnations, all agile processes, including Scrum emphasize teamwork, frequent deliveries of working software, close customer collaboration, and the ability to respond quickly to change.
This post talks about the basic elements of Scrum, and a little understanding for a team to get started with Scrum Model for their project development.
The term "scrum" originated from the game of rugby, and the culture of team work behind this sport. It's about "we", not "me". Rugby has one simple rule which defines game play more than any other: there is no forward passing. In order to work the ball down the field, it must be passed many times from player to player, as the team attempts to push through their opponent’s defense and score.
Elements of Scrum
Sprint
A sprint or an iteration is the basic unit of development in scrum, which generally lasts for a period of 2-4 weeks (decided in advance). At the end of the sprint, the team is able to deliver an integral unit of the product which is potentially shippable.
ROLES
Scrum Master
The scrum master organizes scrum events, helps remove any impediments, helps maintain scrum principles in the team.
Development Team
The development team is responsible for developing the product. The size of the team must be 7 ± 2.
Product Owner
The Product Owner writes user stories, communicates with stakeholders to understand business needs, and maintains the product backlog in order of priority.
SCRUM CEREMONIES
Sprint Planning
During Sprint Planning, the team commits to the work to be done in a sprint. In exchange, the Product Owner agrees not to change the scope of the work expected of the team during the sprint. When the team makes this "deal", it empowers the team to take ownership over the sprint and its success. A Scrum team should be committed to the success of the sprint, willing to do whatever it can to carry it out effectively.
Sprint Retrospective
A sprint retrospective meeting is facilitated by the Scrum Master. The team reflects on their practice, congratulates each other on their successes, and refocuses themselves on any improvements they can make. Two main questions are asked in the sprint retrospective: What went well during the sprint? What could be improved in the next sprint?
Sprint Review
In a sprint review meet, the team reviews the work that was completed, and plans for the remaining work. It is demonstrated to the stake holders.
Daily Scrum Meeting (Stand-up Call)
This event occurs daily for 15 minutes where each of the member of the team shares their status (What did I do yesterday, What will I do today and impediments, if any). It is facilitated by the scrum master, who also notes and helps in resolving the impediments.
Backlog Grooming Meeting
It is also called as Backlog refinement. It is the ongoing process of reviewing product backlog items and checking that they are appropriately prioritized and prepared in a way that makes them clear and executable for teams once they enter sprints via the sprint planning activity.
SCRUM ARTIFACTS
Product Backlog
The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed. Items added to a backlog are commonly written in story format (called user stories).
Sprint Backlog
The sprint backlog is the list of work the development team must address during the next sprint. The list is derived by selecting product backlog items from the top of the product backlog until the development team feels it has enough work to fill the sprint.
Burn Down Chart
The sprint backlog is the list of work the development team must address during the next sprint. The list is derived by selecting product backlog items from the top of the product backlog until the development team feels it has enough work to fill the sprint.
Burn Down Chart
- Sprint Burn Down Chart- It is chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress. It also provides quick visualizations for reference. During the sprint, each member picks up tasks from the sprint backlog and works on them. At the end of the day, they update the remaining hours for tasks to be completed. In such way the actual burndown chart is updated day by day.
- Release burn-down chart- The release burndown chart is the way for the team to track progress and provide visibility. The release burndown chart is updated at the end of each sprint by the scrum master. The horizontal axis of the release burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint.
0 comments:
Post a Comment
Please share your views here