Skip to main content

Scrum Framework - 5 Events in Scrum Framework - By Ankur Mistry

In my previous articles, we have discussed 3 Roles and 3 Artifacts in Scrum. In this article, we are going to discuss 5 events in the Scrum Framework.

There are Five events in Agile Scrum Framework.
  1. Sprint Planning
  2. Daily Scrum
  3. Sprint Review
  4. Sprint Retrospective
  5. The Sprint

    (Figure: Life cycle of Scrum from http://www.agiletroop.com/product/life-cycle-of-scrum/)
Sprint Planning is the event in which the Product Owner presents the ordered product backlog to the development team.
As the word suggests, 'Sprint Planning' means we are going to plan the work to be done in the Sprint.
There are two main parts - 'What' and 'How'.
  • 'What' can be done in this Sprint?
  • 'How' will the selected work get done?
What can be done in the Sprint -
  • In this part, the Product Owner presents the product backlog items with high business value tasks as a first priority to the development team.
  • All team members collaborate to understand the work.
  • The development team has all rights for taking the number of items in the sprint; Product Owner or Scrum Master cannot force team for more tasks.
  • Sprint has Sprint Goal that is decided in the Sprint Planning phase and helps dev team to focus on more details of the tasks and what really needs to be accomplished.
How the selected works gets done -
  • In the second part of Sprint planning, the development team plans on how to produce the next product increment.
  • The development team does planning and design to make sure that they will achieve Sprint Goal.
  • Product Owner may remain available during the planning if the team has any questions.
  • Scrum Master also helps the team in case any arrangements need to be done for achieving the Sprint Goal.
Summary
  • Who will participate - Development Team, Product Owner, and Scrum Master.
  • When - At the beginning of the sprint
  • Time-box - Maximum of eight hours for the four weeks Sprint.
  • Input - Product backlog, latest product increment, the definition of done, team capacity, past performance.
  • Output - Sprint goal, sprint backlog, a clear understanding of work to be done during the sprint, transparency.
Daily Scrum is a daily standup meeting between Scrum Team. It's a 15-minute time-boxed daily event generally held at the same place and the same time.
In this meeting, development team explains -
  • What did I do yesterday?
  • What will I do today?
  • Are there any issues or Impediments?
Development team inspects the progress towards the Sprint goal in the daily standup. The everyday 15-minute meeting with the team helps each member to work together in a self-organized way, and they learn collaboration.
Scrum master makes sure that the each member participates in the daily standup. This helps the team in terms of better communication, decision-making, and improved level of knowledge.
The team learns inspection and adoption.
Summary
  • Who will participate - Development Team, Scrum Master (Product Owner – Optional)
  • When - Everyday same place, same time
  • Time-box - 15 mins Max.
  • Input - 3 questions - "What did I do yesterday?", "What will I do today?" and "Are there any issues or Impediments?"
  • Output - Clear idea about the progress towards Sprint goal, any issues or Impediment idea in the earlier stage.
Sprint Review is held at the end of each Sprint. The main purpose of the Sprint review is to inspect the incremented product created in the Sprint and adapt the product backlog if needed.
The Development Team demonstrates the work that it was done. During the review meeting, Scrum Team and Stakeholders collaborate to discuss what was done in the Sprint and what to do next.
It will give valuable feedback to the subsequent Sprint planning. Sprint review meeting is an informal meeting, not a status update meeting.
Summary
  • Who will participate - Development Team, Scrum Master, Product Owner and Stakeholders
  • When - End of the Sprint and before sprint retrospective.
  • Time-box - Four hours for one month's Sprint.
  • Input - Product Increment, Changes to the product backlog during the Sprint.
  • Output - Updated product backlog, New Idea, clear picture of tasks and product.
Sprint Retrospective is the chance for the Scrum team to inspect itself and create a plan for improvements to be taken care in the next Sprint.
The main purpose of the Sprint retrospective is,
  • Inspect how the sprint went with regard to process, tool, and people.
  • Identify items that went well and potential improvements.
  • Create an action plan to implement improvements in the scrum team.
Scrum Master encourages the team to improve. In the Scrum process framework, practices of processes make tasks more effective and enjoyable for the next Sprint.
Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself.
Summary
  • Who will participate - Development Team, Scrum Master, Product Owner
  • When - at the end of the sprint after sprint review.
  • Time-box - Three hours for one month's Sprint.
  • Input - Results from the sprint, Sprint Events
  • Output - Lesson learned, Improvements, and action list for the next sprint.
Sprint is the heart of Scrum. It's a time-box of one month or 2 weeks and a container of all other events (Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective).
A new Sprint starts immediately after the end of the existing Sprint. During Sprint, the team works together to create a potentially shippable product increment.
  • Sprint enables predictability.
  • Sprint limits risk.
  • Sprint duration should be consistent during the development effort.
  • Sprint ends when time box expires.
During the sprint no changes made in sprint goal, quality goal do not decrease and scope may be renegotiated between the Product Owner and Development Team as more is learned.
Cancelling a Sprint
A Sprint can be canceled before the Sprint duration is over. only the Product Owner can cancel the Sprint he has the authority to cancel
Product owner may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete.
Hope you like this article. Please let me know your feedback in the comment section.

Reference
  • https://www.scrumalliance.org/
  • http://staragile.com
  • http://www.agiletroop.com/product/life-cycle-of-scrum/

Comments

Post a Comment

Popular posts from this blog

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres
Post a Comment
Read more

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum.  What is Agile Agile is a  Method  of project management that is characterized by dividing module in to tasks and t asks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method.  What is Scrum Scrum is an incremental agile software development framework  (Agile Framework).   Agile Scrum Process in Short. Product Backlog:  A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog. Sprint Planning:  In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list. Setting Capacity and Sprint:  Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User. Scrum Master’s role:  Is to make sure team focused on its goal. End of the sprint:  
Post a Comment
Read more

The Burn Up Charts In Scrum By: Namrata Parik

I would like to propose a less-taken path in my maiden article to track the progress in scrum. We usually do it using the burn down chart which is relatively easier to understand as compared to the burn up chart. These charts help the team and stakeholders to see and track the progress at any point in the release process or sprint. Burn-down chart provides us the information showing the progress based on the remaining hours or story points from top to bottom. (The burn-down chart can be plotted using story points, task count or the remaining effort) This chart is a plot of expected remaining and actual remaining, this is the most used chart in scrum and since it has only two lines it is considered to be a simple chart. It does not cover the scope creep. So sometimes what might look like ‘no work ‘ done by the team may actually be a result of scope creep. The chart below reflects that the team has not done any progress in Sprint 5 and 6 as the story points remain the same. Image
Post a Comment
Read more