What is "Scrum"?
When developing a product with a team, there will be few common problems like organizing the team, product scope change, team member not sure what to do next and redoing things that the other member had done.
In order to solve theses kind of problems we can use scrum.
Scrum is a iterative and incremental agile software development framework which is used to manage product development. Where we can easily address these kind of questions , what other members should do?, what we need to?, are we on right track to complete the product in given time? And is the product owner happy with the progress?
2. In the sprint planning, the team pulls a small chunk from the top of that list, a sprint backlog, and plan how to implement those requirements.
3. Team has a certain amount of time — a sprint (usually two to four weeks) — to complete that small chunk.
4. Team organize a meeting everyday (Daily scrum) to assess the progress of the scrum, explaining what things are completed and what are the things that we are going to do today, check whether someone needs help with there work and discuss how the sprint progressing.
5. The ScrumMaster keeps the team focused on its goals.
6. At the end of the sprint, the work should be ready to hand to a customer.
7. The sprint ends with a sprint review and retrospective.
8. And start the next sprint by getting the next chunk from backlog.
Product owner
Product owner represent the stakeholders and conveys what the customers needs from this product to the team. Product owner writes the requirements in customers perspective (User stories) in backlog and prioritize them, Scrum team should have a one product owner.
Development team
Development team are the ones who are responsible delivering the product.
Scrum master
Scrum master is the one who keeps the team focused on the goal. He is accountable for removing obstacles that will affect the team to deliver product on time. And ensure that the team is following agreed scrum processes.
Daily scrum
Each day during a sprint, the team holds a daily scrum (or stand-up) with specific guidelines:
All members of the development team should come prepared.
The daily scrum starts precisely on time even if some development team members are missing, should happen at the same time and place every day is limited (timeboxed) to fifteen minutes.
During the daily scrum, each team-member answers three questions:
What did I do yesterday that helped the development team meet the sprint goal?
What will I do today to help the development team meet the sprint goal?
Do I see any impediment that prevents me or the development team from meeting the sprint goal?
Backlog
Wish list of the product owner. Product owner add his requirements for the product as user stories and prioritize them.
Review and retrospective
At the end of each Sprint Sprint Review and the Sprint Retrospective are been held.
At the Sprint Review, the team:
Reviews the work that was completed and the planned work that was not completed
Presents the completed work to the stakeholders (a.k.a. the demo)
Guidelines for Sprint Reviews:
Incomplete work cannot be demonstrated
The recommended duration is two hours for a two-week Sprint (pro-rata for other Sprint durations)
At the Sprint Retrospective, the team:
Reflects on the past Sprint
Identifies and agrees on continuous process improvement actions
Guidelines for Sprint Retrospectives:
Two main questions are asked in the Sprint Retrospective: What went well during the Sprint? What could be improved in the next Sprint?
The recommended duration is one-and-a-half hours for a two-week Sprint (pro-rata for other Sprint durations)
This event is facilitated by the Scrum Master
Sprint Backlog
A prioritized list of tasks to complete during the Sprint.
Sprint
A time period (typically 1–4 weeks) in which development occurs on a set of Product Backlog Items that the team has committed to—commonly referred to as a time-box or iteration
Spike
A time boxed period used to research a concept or create a simple prototype. Spikes can either be planned to take place in between Sprints or, for larger teams, a spike might be accepted as one of many Sprint delivery objectives. Spikes are often introduced before the delivery of large or complex Product Backlog Items in order to secure budget, expand knowledge, or produce a proof of concept. The duration and objective(s) of a spike is agreed between Product Owner and Development Team before the start. Unlike Sprint commitments, spikes may or may not deliver tangible, shippable, valuable functionality. For example, the objective of a spike might be to successfully reach a decision on a course of action. The spike is over when the time is up, not necessarily when the objective has been delivered.
Tasks
Work items added to the Sprint Backlog in Sprint Planning, or during the Sprint, with an estimate of hours to complete. Generally, each task should be small enough to be easily completed within a single day.
Definition of done (DoD)
The exit-criteria to determine whether a Product Backlog Item is complete. In many cases the DoD requires that all regression tests should be successful. The definition of "done" may vary from one Scrum Team to another, but must be consistent within one team.
Velocity
The total effort a team is capable of in a Sprint. The number is derived by evaluating the work (typically in user story points) completed in the last Sprint. The collection of historical velocity data is a guideline for assisting the team in understanding how much work they can likely achieve in a future Sprint.
When developing a product with a team, there will be few common problems like organizing the team, product scope change, team member not sure what to do next and redoing things that the other member had done.
In order to solve theses kind of problems we can use scrum.
Scrum
Scrum is a iterative and incremental agile software development framework which is used to manage product development. Where we can easily address these kind of questions , what other members should do?, what we need to?, are we on right track to complete the product in given time? And is the product owner happy with the progress?
This is how the scrum works
1. A product owner creates a prioritized list called a product backlog where he will add what he needs in the product.2. In the sprint planning, the team pulls a small chunk from the top of that list, a sprint backlog, and plan how to implement those requirements.
3. Team has a certain amount of time — a sprint (usually two to four weeks) — to complete that small chunk.
4. Team organize a meeting everyday (Daily scrum) to assess the progress of the scrum, explaining what things are completed and what are the things that we are going to do today, check whether someone needs help with there work and discuss how the sprint progressing.
5. The ScrumMaster keeps the team focused on its goals.
6. At the end of the sprint, the work should be ready to hand to a customer.
7. The sprint ends with a sprint review and retrospective.
8. And start the next sprint by getting the next chunk from backlog.
Product owner
Product owner represent the stakeholders and conveys what the customers needs from this product to the team. Product owner writes the requirements in customers perspective (User stories) in backlog and prioritize them, Scrum team should have a one product owner.
Development team
Development team are the ones who are responsible delivering the product.
Scrum master
Scrum master is the one who keeps the team focused on the goal. He is accountable for removing obstacles that will affect the team to deliver product on time. And ensure that the team is following agreed scrum processes.
Daily scrum
Each day during a sprint, the team holds a daily scrum (or stand-up) with specific guidelines:
All members of the development team should come prepared.
The daily scrum starts precisely on time even if some development team members are missing, should happen at the same time and place every day is limited (timeboxed) to fifteen minutes.
During the daily scrum, each team-member answers three questions:
What did I do yesterday that helped the development team meet the sprint goal?
What will I do today to help the development team meet the sprint goal?
Do I see any impediment that prevents me or the development team from meeting the sprint goal?
Backlog
Wish list of the product owner. Product owner add his requirements for the product as user stories and prioritize them.
Review and retrospective
At the end of each Sprint Sprint Review and the Sprint Retrospective are been held.
At the Sprint Review, the team:
Reviews the work that was completed and the planned work that was not completed
Presents the completed work to the stakeholders (a.k.a. the demo)
Guidelines for Sprint Reviews:
Incomplete work cannot be demonstrated
The recommended duration is two hours for a two-week Sprint (pro-rata for other Sprint durations)
At the Sprint Retrospective, the team:
Reflects on the past Sprint
Identifies and agrees on continuous process improvement actions
Guidelines for Sprint Retrospectives:
Two main questions are asked in the Sprint Retrospective: What went well during the Sprint? What could be improved in the next Sprint?
The recommended duration is one-and-a-half hours for a two-week Sprint (pro-rata for other Sprint durations)
This event is facilitated by the Scrum Master
Sprint Backlog
A prioritized list of tasks to complete during the Sprint.
Sprint
A time period (typically 1–4 weeks) in which development occurs on a set of Product Backlog Items that the team has committed to—commonly referred to as a time-box or iteration
Spike
A time boxed period used to research a concept or create a simple prototype. Spikes can either be planned to take place in between Sprints or, for larger teams, a spike might be accepted as one of many Sprint delivery objectives. Spikes are often introduced before the delivery of large or complex Product Backlog Items in order to secure budget, expand knowledge, or produce a proof of concept. The duration and objective(s) of a spike is agreed between Product Owner and Development Team before the start. Unlike Sprint commitments, spikes may or may not deliver tangible, shippable, valuable functionality. For example, the objective of a spike might be to successfully reach a decision on a course of action. The spike is over when the time is up, not necessarily when the objective has been delivered.
Tasks
Work items added to the Sprint Backlog in Sprint Planning, or during the Sprint, with an estimate of hours to complete. Generally, each task should be small enough to be easily completed within a single day.
Definition of done (DoD)
The exit-criteria to determine whether a Product Backlog Item is complete. In many cases the DoD requires that all regression tests should be successful. The definition of "done" may vary from one Scrum Team to another, but must be consistent within one team.
Velocity
The total effort a team is capable of in a Sprint. The number is derived by evaluating the work (typically in user story points) completed in the last Sprint. The collection of historical velocity data is a guideline for assisting the team in understanding how much work they can likely achieve in a future Sprint.
Comments
Post a Comment