What is scrum
What is scrum
Scrum is a very popular framework for implementing agile project management.
Although some people think that agile and scrum is the same thing, this is wrong.
While there are many frameworks for implementing agile, scrum is the most outstanding owing to its specific concepts and practices categorized into roles, timeboxes and artifacts.
Generally, the components of the scrum framework are:
1. Three roles: Product owner, scrum master and scrum development team
2. Sprints: A project iteration of less than a calendar month
3. Scrum events/ceremonies: Sprint planning meeting (what and how meetings), daily scrum meetings, sprint review meeting and sprint retrospective meetings.
4. Scrum artifactsa) Product Backlog:
a prioritized backlog with end user requirements; the product owner is responsible for this
b) Sprint backlog:
Elected items from the product backlog. It’s like a mini-plan for achieving the sprint goal and delivering the product increment👇.
Forecast the functionalities in the next increment and what needs to be done to deliver that functionality. The development team are responsible for this.
c) Product increments:
At the end of each sprint, the new product increment should be in a functional state and meets the scrum team’s definition of “Done”. If all works well and the team’s estimation stays on track, the increment has all sprint backlogs’ items, meeting the team’s definition of done.
The Scrum Events:
Sprint planning meeting: (Time Box: 8 hours for a one month sprint).
Planning Meetings are held at the beginning of each sprint which lasts a maximum of 8 hours (for 1 month sprints). It is attended by product owner, scrum master and scrum team.
The PO submits and describes the prioritized product backlog and explains to the team about the sprint goal and product backlog’s top items.
The team agrees on which prioritized items to complete during the upcoming sprint and then shifts these items from the product backlog to the sprint backlog.
Daily scrum meeting: (Time Box: 15 minutes)
Every day, during the sprint, the scrum master, scrum team and or product owner (optional) must attend a daily scrum meeting of less than 15 minutes.
During these day to day scrum meetings, the team members talk about what they worked on the previous day, what they’ll work on that day and identify any setbacks to progress.
This daily scrums synchronize the scrum team’s work plus their project knowledge, communication and decision making is enhanced.
Sprint review: (Time Box: 4 hours for a 1-month sprint)
At the end of each sprint, review, the team demonstrates the new functionality to the PO scrum master, customers and other stakeholders/sponsors interested in providing feedback that may perhaps influence the following sprint.
The relevant stakeholders express their impressions and clarify whether their user stories/requirements are well implemented. The PO ascertains whether the product is really “Done”.
This feedback loop could lead to changes to recently released functionality or just lead to revising or adding items to the product backlog.
Sprint retrospective meeting: (Time Box: 3 hours for a 1-month sprint)
The Sprint retrospective meeting is another event in scrum attended by the entire scrum team at the end of each sprint.
The entire team comes together to reflect on the sprint that has just ended as well as spot any improvement measures needed.
They generally talk about how to make their work more effective and efficient in the future.
While the sprint review is on the product, sprint retrospective meetings focus on the process.
Refrences
Paul VII. Agile Product Management: User Stories: How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum (scrum, ... development, agile software development) (pp. 7-8). Pashun Consulting Ltd.. Kindle Edition.
Comments
Post a Comment