10 May 2016

Agile Tutorial - What is Scrum framework?

Scrum is a time-boxed, iterative and incremental agile software development framework. It is the most commonly used Agile methodology in the software industry.

The Scrum approach to Agile software development marks a dramatic departure from waterfall model. Scrum emphasizes collaboration, functioning software, self-organized team, and the flexibility to adapt to emerging business realities.

It is inspired by empirical inspect and adapt feedback loops to cope with complexity and risk. It uses real-world progress to plan and schedule releases. Time is divided into short work cadences, known as Sprints or Iterations. These are typically two week long. At the end of each sprint, stakeholders and team members meet to see a potentially shippable product increment and plan its next steps. This allows direction to be adjusted based on completed work, and not on a plan or speculation or predictions.

Scrum is a simple set of roles, responsibilities and meetings that never change. It is a charter of 3 pillars, 3 roles and 3 artifacts.

3 pillars/foundations of Scrum -
  • Transparency/Visibility
  • Inspection
  • Adaptation
3 roles in Scrum
  • Development Team - Self-organizes to get the work done.
  • Product Owner - Responsible for the business value of the project.
  • Scrum Master - Ensures that the team is functional and productive and is following scrum.
3 artifacts in Scrum
  • Product Backlog - Ordered and Prioritized list of ideas for the product.
  • Sprint Backlog - Set of work from the Product Backlog that the team agrees to complete in a sprint. It is broken down into individual definable tasks.
  • Product Increment - Required result of every sprint. This is an integrated version of the product kept at high enough quality to be shippable.
Scrum ceremonies
  • Sprint Planning - Before the sprint, the team meets with the product owner to choose a set of work to deliver during the sprint.
  • Daily Stand-Up - During the sprint, the team meets each day to share progress and impediments.
  • Sprint Review - After the sprint, the team demonstrates what is has completed during the sprint.
  • Sprint Retrospective - After the sprint, the team looks for ways to improve the product and the process.

No comments: