SCRUM Framework
In today’s date SCRUM is considered as practical & more valued Agile methodology. It is easy to use & deliver incrementally high quality software on time & budget. In this article we will quickly take a look at what all steps involved in SCRUM framework like What is Product Vision, Product Backlog, Sprint Backlog, Daily SCRUM, A Sprint Burndown and Sprint Retrospective meeting etc.
In today’s date SCRUM is considered as practical & more valued Agile methodology. It is easy to use & deliver incrementally high quality software on time & budget. In this article we will quickly take a look at what all steps involved in SCRUM framework like What is Product Vision, Product Backlog, Sprint Backlog, Daily SCRUM, A Sprint Burndown and Sprint Retrospective meeting etc.
Project Vision:
The goal of the project vision is to align the team around a central purpose. It is very important for the Agile SCRUM team to know what they are aiming for. Based on vision Product Owner creates ordered prioritized wish list. Requirements are broken down into User Stories by the Product Owner.
The goal of the project vision is to align the team around a central purpose. It is very important for the Agile SCRUM team to know what they are aiming for. Based on vision Product Owner creates ordered prioritized wish list. Requirements are broken down into User Stories by the Product Owner.
Product Backlog:
The Product Backlog is a ordered & prioritized list of item that all need to include in the product. It is dynamic & during the project items may added or deleted from this list. All items are ordered prioritized in this list. The highest priority items are completed first.
SCRUM Framework
The Product Backlog is a ordered & prioritized list of item that all need to include in the product. It is dynamic & during the project items may added or deleted from this list. All items are ordered prioritized in this list. The highest priority items are completed first.
SCRUM Framework
Sprint Backlog:
In the Sprint planning meeting the team picks list of User stories from Product Backlog. These selected items moved from Product backlog to Sprint backlog. All sprint backlog user stories are discussed items from the product backlog and team member committed to complete the assigned task within Sprint Timeboxed. Each user story is divided into smaller detailed tasks. In Sprint team work together collaboratively to complete Sprint tasks.
In the Sprint planning meeting the team picks list of User stories from Product Backlog. These selected items moved from Product backlog to Sprint backlog. All sprint backlog user stories are discussed items from the product backlog and team member committed to complete the assigned task within Sprint Timeboxed. Each user story is divided into smaller detailed tasks. In Sprint team work together collaboratively to complete Sprint tasks.
Daily SCRUM:
The Daily SCRUM is not used as a problem-solving or issue resolution meeting. In the Daily SCRUM each of the team members should answer three questions:
- What did you do yesterday?
- What will you do today?
- Are there any obstacles in your way?
In the Daily SCRUM team share the conflicts, obstacle or impediment faced in their tasks & any possible solutions on that. On daily basis this meeting holds on same time, same location hold by Agile SCRUM team. Ideally “The Daily SCRUM” is conducted in the morning which helps to plan task for whole day. As Agile process & Sprint is time-boxed, similarly Daily SCRUM meeting should be time-boxed to 15 minutes max. In this meeting discussion should be quick and relevant. The SCRUMMaster always helps to maintain the focus of team to its Sprint goal.
The Daily SCRUM is not used as a problem-solving or issue resolution meeting. In the Daily SCRUM each of the team members should answer three questions:
- What did you do yesterday?
- What will you do today?
- Are there any obstacles in your way?
In the Daily SCRUM team share the conflicts, obstacle or impediment faced in their tasks & any possible solutions on that. On daily basis this meeting holds on same time, same location hold by Agile SCRUM team. Ideally “The Daily SCRUM” is conducted in the morning which helps to plan task for whole day. As Agile process & Sprint is time-boxed, similarly Daily SCRUM meeting should be time-boxed to 15 minutes max. In this meeting discussion should be quick and relevant. The SCRUMMaster always helps to maintain the focus of team to its Sprint goal.
A Sprint Burndown:
Sprint Burndown measures remaining Sprint Backlog items across the time of a Sprint. It is very effective visual indicator to get correlation between work remaining at any point of time & the actual progress of team. Prior to Daily SCRUM meeting, Sprint Burndown chart should be updated, so it will help to understand the progress of Sprint daily & makes any adjustments if needed.
Sprint Burndown measures remaining Sprint Backlog items across the time of a Sprint. It is very effective visual indicator to get correlation between work remaining at any point of time & the actual progress of team. Prior to Daily SCRUM meeting, Sprint Burndown chart should be updated, so it will help to understand the progress of Sprint daily & makes any adjustments if needed.
Shippable Product:
The end of the Sprint can turn into an increment of potentially shippable functionality hand over to customer. This shippable functionality should be well-structured, well-written code, thoroughly tested and user operation of the functionality is documented. At the end of the Sprint features committed in Sprint are demonstrated to all stakeholders & they provide the valuable feedback to moving product in correct direction.
The end of the Sprint can turn into an increment of potentially shippable functionality hand over to customer. This shippable functionality should be well-structured, well-written code, thoroughly tested and user operation of the functionality is documented. At the end of the Sprint features committed in Sprint are demonstrated to all stakeholders & they provide the valuable feedback to moving product in correct direction.
Sprint Retrospective:
At the end of each Sprint review and Retrospective meeting should be conducted to know what went good & bad in Sprint. Participants for this meeting is Team, SCRUMMaster & Product Owner(Listner). This meeting also timeboxed to 2-3 hours. Using this approach each team member is asked to identify specific things that the team should:
- Start doing
- Stop doing
- Continue doing
Iterations are a key feature of the SCRUM process. In the next Sprint again team choose the chunk of User stories from the Product backlog & Sprint cycle started with new Sprint goals again. These cycles are continue doing unless and until Product backlog is finished or Deadline reaches or budget is used up. Agile SCRUM is ensure that all high priority task ordered top in the Product backlog so those can get completed first before the project ends.
At the end of each Sprint review and Retrospective meeting should be conducted to know what went good & bad in Sprint. Participants for this meeting is Team, SCRUMMaster & Product Owner(Listner). This meeting also timeboxed to 2-3 hours. Using this approach each team member is asked to identify specific things that the team should:
- Start doing
- Stop doing
- Continue doing
Iterations are a key feature of the SCRUM process. In the next Sprint again team choose the chunk of User stories from the Product backlog & Sprint cycle started with new Sprint goals again. These cycles are continue doing unless and until Product backlog is finished or Deadline reaches or budget is used up. Agile SCRUM is ensure that all high priority task ordered top in the Product backlog so those can get completed first before the project ends.
0 comments:
Post a Comment
Note: only a member of this blog may post a comment.