Scrum Framework, Scrum Artifacts, Meetings, Roles, Sprint Planning, Burndown Chart and Scrum Case Study
Unit 3 focuses on Scrum. Scrum is an Agile framework used to develop software in short iterations called sprints. This unit covers Scrum framework, artifacts, meetings, activities, roles, sprint planning, daily scrum, sprint review, retrospective, user stories, acceptance tests, burndown chart and Scrum case study.
Scrum is an Agile framework used for managing complex software projects. It divides development work into small time-boxed iterations known as sprints.
Scrum framework consists of roles, artifacts and events that help teams deliver software incrementally.
| Scrum Element | Includes |
|---|---|
| Roles | Product Owner, Scrum Master, Development Team |
| Artifacts | Product Backlog, Sprint Backlog, Increment |
| Events | Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective |
Responsible for product vision, product backlog, priority and business value.
Helps the team follow Scrum, removes blockers and supports continuous improvement.
Cross-functional team that designs, develops, tests and delivers working software.
Product backlog is a prioritized list of all features, requirements, bug fixes and improvements needed in the product.
Sprint backlog contains selected product backlog items that the team commits to complete in a sprint.
Increment is the working software produced at the end of a sprint.
| Meeting | Purpose |
|---|---|
| Sprint Planning | Select work for the sprint and define sprint goal. |
| Daily Scrum | Short daily meeting to discuss progress, plan and blockers. |
| Sprint Review | Demonstrate completed work and collect feedback. |
| Sprint Retrospective | Discuss what went well, what went wrong and improvements. |
Scrum team simulation means practicing Scrum process in a project-like environment. It helps students understand team roles, sprint planning, backlog handling and sprint review.
Product planning defines product vision, goals, features and roadmap.
Release planning decides which features will be delivered in a particular release and when.
Team selects user stories from product backlog and creates sprint backlog.
Team develops, tests and integrates selected work during sprint.
Team demonstrates completed work to stakeholders and receives feedback.
Team discusses improvements for next sprint.
User story is a short requirement written from the user's point of view.
Acceptance tests define conditions that must be satisfied for a user story to be considered complete.
User Story: As a student, I want to download PDF notes.
Burndown chart is a graphical representation showing remaining work in a sprint over time. It helps track progress and predict whether sprint work will be completed on time.
Daily Scrum is a short daily meeting, usually 15 minutes, where team members discuss progress and blockers.
Suppose a team is developing an online RGPV notes website.
| Product Backlog | Sprint Backlog |
|---|---|
| Complete list of product requirements. | Selected work for current sprint. |
| Managed by Product Owner. | Managed by Development Team. |
| Continuously updated. | Fixed during sprint as per sprint goal. |
| Long-term product work. | Short-term sprint work. |
| Topic | Exam Importance |
|---|---|
| Scrum Framework | Very High |
| Scrum Roles | Very High |
| Scrum Artifacts | High |
| Sprint Planning | High |
| User Stories | High |
| Burndown Chart | Medium |
| Daily Scrum | Medium |