How Scrum Works: An Overview of Agile Framework

Introduction :

It is process used to build the software in Agile Model. This framework has important things in it, including Scrum Team, Product Backlog, Sprint Backlog and Events including Sprint Planning Meeting, Daily Standup Meeting, Sprint Review Meeting & Retrospective Meeting.

We’ll learn each of all Scrum framework’s things.

Scrum Team :

A Scrum Team is a cross functional group of professionals who work collaboratively to deliver features or user stories in a sprint.

It is divided into two parts : Core Team & Shared Team.

CORE TEAM :

The Core Team includes the Scrum master, developers, and testers. They do the main work of building and testing the product.

SHARED TEAM :

The Shared Team include scrum members like the Business analyst, Product owner, Architect, Designers, Database admin, Network admin. They support the Core Team by providing guidance, resources, and expertise.

The Scrum master leads entire Scrum Team & he facilitates everyone to complete their assigned tasks.

Product Backlog :

A Product Backlog is a prioritized list of stories or requirements that need to be developed for the complete project.

The people like Product owner, Business analyst, Architect & Scrum master are involved in building the product backlog.

Sprint Backlog :

The Sprint backlog is a list of tasks that the Scrum Team plans to finish in the current sprint. It tells what the team will work on during that time.

Sprint Planning Meeting :

1. The whole Scrum Team joins the meeting includes the Product Owner, Scrum Master, and Developers.

2. The Product Owner shows the most important work called user stories from the Product Backlog.

3. The team talks about the stories to understand what needs to be done.

4. The Developers choose which stories they can finish in the next Sprint. This list becomes the Sprint Backlog.

5. The team breaks each story into smaller tasks.

6. The team can guess how long each task will take, usually in hours. This is called as Story Point.

7. The Scrum Master helps guide the meeting, but does not tell people what to do. The team decides together who will do what.

Daily Standup Meeting/ Role Call Meeting/ Daily Scrum Meeting :

1. The entire Scrum Team attends the meeting.

2. The meeting is run by the Developers & Testers.

3. The Scrum Master only facilitates but doesn’t lead the meeting.

4. Each team member quickly answers 3 key questions

   • What did I do yesterday?

   • What will I do today?

   • Are there any problems blocking my work?

5. If anyone has a issue, The Scrum master notes down all in a Document called Impediment Backlog & later he will tries to resolve it.

6. The meeting should be short between 10 to 15 minutes maximum.

7. It is usually held at the start of the workday.

8. Everyone is encouraged to stand during the meeting to keep it short and focused.

Sprint Review Meeting :

1. The Sprint Review is held at the end of the Sprint with the Scrum Team and stakeholders.

2. The team gives a demo of the work completed during the Sprint.

3. The Product Owner and stakeholders give feedback and discuss what was done and what is still needed.

4. The Product Backlog is updated based on feedback, helping decide what to work on next.

Retrospective Meeting :

1. The entire Scrum Team meets after the Sprint to discuss what went well, what didn’t go well and what can be improved.

2. The team talks openly about processes, teamwork, tools, and anything that affected the Sprint.

3. The team may write down key points or actions in a Retrospective document.

4. In next sprint the team refers to this document to avoid past mistakes and repeat good practices.

5. Also they discuss about next sprint development.

Summary Point :

Scrum is an Agile framework used to develop software through collaboration, iteration, and feedback. It involves key roles, artifacts like Product and Sprint Backlogs, and events like Sprint Planning, Daily Standups, Sprint Review, and Retrospective. The goal is to deliver working software in short cycles while continuously improving the process.