Scrum Framework Overview

Scrum

This section is specifically about the Scrum framework, as it's one of the most popular Agile methodologies.

Scrum is a lightweight set of practices that helps teams deliver value through adaptive solutions. It was inspired by complex product development. In Scrum, the team works together closely throughout a sprint, which lasts a maximum of four weeks. Let's dive into some key aspects of Scrum: Events, Sprints, and Artifacts.

Events

In Scrum, there are five types of events:

• Sprint: A short period during which specific work has to be completed and made ready for review. This process may repeat.
• Sprint Planning: An event where what will be done during the next Sprint is planned; the Product Owner presents the highest priority work to the Development Team based on current market conditions. The goal is to maximize productivity for every Sprint.
• Daily Scrum: A meeting of the entire Development Team held daily to plan details of the work, resolve any issues that came up between meetings, and make sure the Development Team stays focused on its priorities.
• Sprint Review: A meeting at the end of each Sprint, where progress is reviewed. The objective is to show the results of the latest Sprint, evaluate the work done, and plan for the upcoming Sprint. This review should result in a concrete plan to achieve maximum success in the next Sprint.
• Sprint Retrospective: A meeting after every Sprint to discuss the past Sprint and get everyone on the same page regarding improvements and changes to the team's processes. It's important that all members participate and take responsibility.

These events help ensure that the team works cohesively towards their goals and continuously improves their processes.

Sprint Planning

Sprint planning is a crucial part of Scrum, as it sets the stage for what will be accomplished in the current Sprint. During this event, the Development Team meets to decide what they will do during the current Sprint, while Product Backlog items from previous Sprints can be revisited later to maintain quality adjustments. Here are the steps involved in sprint planning:

Step 1: Refine the Top Product Backlog Items

The Development Team refines the top Product Backlog items so that they are clear enough to commit to. This includes breaking down larger features if necessary.

Step 2: Select the Items

The Development Team selects items from the refined Product Backlog that they think they can accomplish within the timebox of one Sprint. These items form the Sprint Backlog. They also estimate the remaining effort required to complete them.

Step 3: Create a Sprint Plan

The Development Team creates a plan for delivering the product Increment and realizes the potential capabilities of the Increment.

Step 4: Assign Stories to Specific Members

Stories will be assigned to individual developers or pairs. Developers assign tasks to themselves to implement the code needed to satisfy the acceptance criteria for the selected Product Backlog item.

Artifacts

Artifacts are tangible representations of abstract concepts used in Scrum and include:

• Product Backlog: All the enhancements or new functionality described as User Stories. Each Item represents a conversation between the developer and the client.
• Sprint Backlog: A list of high-value items that have been selected for the Sprint with the intent of completing them and making them ready for review. Only items in the Sprint Backlog are eligible for selection in the Daily Scrum.
• Increment: The sum of all the potentially releasable functionality developed during all the Sprints since the last 'release'. An Increment must be usable, so the team could release it as a working software system.

By using these three artifacts, Scrum enables the Development Team to maintain a constant flow of value to stakeholders while continually improving itself.