How Scrum Works??

To start with, lets discuss some common Issues in the Waterfall Model

The Waterfall model, while structured and linear, often encounters several challenges that can hinder project success. Some common issues include:

• Vague Requirements: Requirements are often not well-defined or detailed, leading to misunderstandings and gaps in the project scope.
• Unrealistic Expectations: Setting impractical deadlines, estimates, and scopes can lead to project delays and compromised quality.
• Changing Requirements: Frequent changes to requirements, also known as scope creep, disrupt the planned flow and add complexity to the project.
• Defects and Issues: The discovery of defects and issues late in the development cycle can significantly impede progress and require costly fixes.
• Disappearing Resources: Key personnel may be reassigned or unavailable when needed, causing delays and knowledge gaps.
• Support Issues: Ongoing support and maintenance requirements can divert resources and attention away from project work, impacting overall progress.

Introducing Scrum

Scrum, developed by Ken Schwaber and Jeff Sutherland, is a lightweight framework designed to help individuals, teams, and organizations create value through adaptive solutions to complex problems. It empowers self-managing, cross-functional teams to work collaboratively and efficiently.

Key features of Scrum include:

• Iterative Work Cycles: Scrum operates in iterations, promoting continuous improvement and adaptability.
• Business Flexibility: The framework allows for changes in requirements, providing the flexibility to address evolving business needs.
• Developer Certainty: Within each iteration, developers have a clear and stable set of objectives, ensuring focus and consistency in their work.

Scrum fosters an environment where teams can thrive, innovate, and deliver high-quality results.

Scrum Accountabilities, Rules, Timeboxes, and Artifacts

Accountabilities (Roles)

• Scrum Master:

a. Facilitates the Scrum process and ensures that the team follows Scrum practices.

b. Removes impediments and fosters an environment for high performance.

c. Acts as a coach for the team, Product Owner, and organization.

• Product Owner:

a. Represents the stakeholders and the voice of the customer.

b. Manages and prioritizes the Product Backlog.

c. Ensures the team delivers value to the business.

• Developers:

a. Self-managing professionals who create the product increment.

b. Responsible for delivering a potentially releasable increment at the end of each Sprint.

c. Collaborate and organize work within the Sprint.

Scrum Events

• Sprint:

A timeboxed iteration, typically lasting 1-4 weeks.

During the Sprint, a usable and potentially releasable product increment is created.

• Sprint Planning:

A session at the beginning of the Sprint where the team plans the work to be performed.

The Product Owner presents the top priority items from the Product Backlog.

The team collaborates to define the Sprint Goal and the work needed to achieve it.

• Daily Scrum:

A daily 15-minute meeting for the team to inspect progress towards the Sprint Goal.

Team members discuss what they did yesterday, what they will do today, and any impediments.

• Sprint Review:

Held at the end of the Sprint to inspect the increment and adapt the Product Backlog.

The team presents the work done, and stakeholders provide feedback.

• Sprint Retrospective:

A session after the Sprint Review to reflect on the past Sprint.

The team discusses what went well, what could be improved, and how to improve in the next Sprint.

Artifacts

• Product Backlog:

An ordered list of everything that is known to be needed in the product.

Managed by the Product Owner and evolves as new requirements are discovered.

• Sprint Backlog:

The set of Product Backlog items selected for the Sprint, plus a plan for delivering the product increment and achieving the Sprint Goal.

Managed by the Developers.

• Increment:

The sum of all the Product Backlog items completed during a Sprint, integrated with previous increments.

Must be in a usable condition regardless of whether the Product Owner decides to release it.

Build Initial Product Backlog

Release Planning Meeting

Release Burndown

Sprint Planning Meeting

Sprint

Daily Scrum

Sprint Burndown

Sprint Review

Increment

Sprint Retrospective