What is Scrum

Scrum is a framework to implement Agile methodology for developing, delivering, and sustaining complex products, with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing, and advanced technologies.

Scrum Principles

1) Empirical Process Control

In Scrum, decisions are made based on observation and experimentation rather than on detailed upfront planning. Empirical process control relies on the three main ideas of transparency, inspection, and adaptation.

2) Self Organization

Scrum believes that employees are self-motivated and seek to accept greater responsibility. So, they deliver much greater value when self-organized.

The preferred leadership style in Scrum is "servant leadership", which emphasizes achieving results by focusing on the needs of the Scrum Team.

3) Collaboration

Scrum is a methodology that applies Agile values and principles. Like Agile, Scrum was first used by software developers. However, it has spread and is now used by other product developers, entrepreneurs, and anyone else trying to take on a complex project.

Usually, Scrum involves a collaborative team made up of five to seven people. There are three roles within the Scrum team: the Product Owner, the Scrum Master, and the general team members. The team members will be the ones doing the work of developing the product.

4) Time Boxing

Many people approach their work one task at a time and concentrate on each until they complete it, however long this takes. Timeboxing is different because it encourages you to focus on time instead of tasks. To use this time-management tool, you allocate a certain number of hours or days, called a "timebox," to each activity. You then use this time – and only this time – to complete the task.

Timeboxing is a simple and effective way to manage your own, and your team members, daily workload. For yourself, this ensures that you don't spend too long on a task that isn't worth the effort. For team members, it helps to ensure that they don't over-engineer solutions and that they don't, unintentionally, blow the budget you have available for the work.

5) Value-Based Prioritization

Prioritizing can be defined as determining the order and separating what must be done now, from what needs to be done later.

Scrum uses Value-based Prioritization as one of the core principles that drive the structure and functionality of the entire Scrum framework. It benefits projects through adaptability and iterative development of the product or service. More significantly, Scrum aims at delivering a valuable product or service to the customer on an early and continuous basis.

6) Iterative Devlopment

This principle defines iterative development and emphasizes how to better manage changes and build products that satisfy customer needs. It also delineates the Product Owner's and organization's responsibilities related to iterative development

Scrum Master

• Manage the team
• Enable Communication among all other roles
• Shields team from distraction
• Take care that scrum framework will be followed correctly

Scrum Product Owner

• Responsible for the value in each product increment
• Maintain product backlog
• A single voice, not a committee
• Accepts or rejects work results

Developer Team

• Responsible and committed to meet sprint goals
• Cross-functional team
• 5-7 team members

Sprint

• It is a duration of time after that team had to give an increment or feature of product

• It can be of 2 weeks to 1 month

Meetings

1. Sprint planning
2. Daily standup
3. Sprint review
4. Sprint retrospective
5. Sprint backlog refinement

Sprint Planning

• Time boxed meetings
• Team selects and understands work to be done in a sprint
• Start with ordered product backlog
• Scrum team discuss to understand each item and what is required to complete this sprint

Daily Standups

• Short 15 min meeting occur daily held at the same place and the same time
• Time boxed meetings
• Talk about Yesterday's accomplishments and what they are going to do today

Sprint Review

• Held at the end of every sprint
• Objective is to Demonstrate the functionality of the product and what has been achieved in a particular sprint
• Generally everyone is present to review the product
• Product performance compared against original sprint goals that were discussed in the sprint planning

Sprint Retrospective

• Discuss what went right and what went wrong
• Talk about what improvements needed to be made and What should be done in future

Sprint Backlog Refinement

• Last type of scrum meeting
• Categorize and prioritize the backlog
• Backlog refinement reduces the need for long sprint planning

Sprint/Product Burndown Chart

• Graphical representation of work left to be completed vs time