Unit III: Introduction to Scrum
Scrum is an Agile framework used to develop, deliver and continuously improve complex products through short, iterative cycles. Scrum emphasizes transparency, inspection and adaptation.
The Scrum process organizes work into fixed-length Sprints. During each Sprint, the Scrum Team works toward a Sprint Goal and produces a usable product increment.
Agile Scrum Framework
Scrum provides a lightweight framework for managing complex product development. It establishes accountabilities, events, artifacts and rules that help teams inspect progress and adapt their work.
Scrum Values
Commitment
Team members commit to achieving their goals and supporting each other.
Focus
The team focuses on the work and goals of the current Sprint.
Openness
Team members and stakeholders remain open about work, progress and challenges.
Respect
Scrum Team members respect each other's abilities, responsibilities and contributions.
Courage
Team members have the courage to address difficult problems and make necessary decisions.
Scrum Roles / Accountabilities
A Scrum Team consists of the Product Owner, Scrum Master and Developers. Together they work as a cohesive unit focused on creating a valuable product increment.
Product Owner
Responsible for maximizing product value and effectively managing the Product Backlog.
Scrum Master
Helps establish Scrum, supports the team and helps remove impediments to effective Scrum practice.
Developers
Create the usable product increment and possess the skills necessary to perform the work.
Product Owner Responsibilities
- Develop and communicate the Product Goal.
- Create and clearly communicate Product Backlog items.
- Order Product Backlog items.
- Ensure that the Product Backlog is transparent and understood.
- Represent stakeholder and customer interests.
Scrum Master Responsibilities
- Help the team understand Scrum theory and practice.
- Support the team in improving effectiveness.
- Help remove or address impediments.
- Facilitate useful Scrum events when appropriate.
- Support the Product Owner and organization in applying Scrum.
Scrum Artifacts
Scrum artifacts represent important work or value. They are designed to maximize transparency of key information.
Product Backlog
An ordered list of everything known to be needed for the product.
Sprint Backlog
Contains the Sprint Goal, selected Product Backlog items and the actionable plan for delivering the increment.
Increment
A usable, valuable step toward the Product Goal that meets the applicable Definition of Done.
Scrum Meetings / Events
| Event | Purpose | Main Participants |
|---|---|---|
| Sprint Planning | Establish the Sprint Goal and plan the work for the Sprint. | Scrum Team |
| Daily Scrum | Inspect progress toward the Sprint Goal and adapt the plan. | Developers |
| Sprint Review | Inspect the Sprint outcome and discuss future adaptations. | Scrum Team + Stakeholders |
| Sprint Retrospective | Plan ways to improve quality and effectiveness. | Scrum Team |
Scrum Team Simulation
Scrum Team simulation is a practical learning activity in which students or team members assume Scrum accountabilities and perform a simplified Sprint.
- Assign Product Owner, Scrum Master and Developer roles.
- Prepare a small Product Backlog.
- Conduct Sprint Planning.
- Select and organize Sprint work.
- Conduct short Daily Scrum discussions.
- Demonstrate the completed increment.
- Conduct a Sprint Retrospective.
Scrum Planning Principles
Goal-Oriented
Planning should establish a clear objective for the Sprint and product.
Collaborative
Scrum Team members collaborate to understand the work and create a realistic plan.
Adaptive
Plans can be updated as more information becomes available.
Value-Focused
The team prioritizes work that contributes meaningful product value.
Product and Release Planning
Product planning provides direction for product development, while release planning identifies a high-level set of functionality expected to be delivered.
Sprinting
A Sprint is a fixed-length period during which the Scrum Team works toward a Sprint Goal and creates a usable product increment.
Sprint Planning
Sprint Planning initiates the Sprint by establishing why the Sprint is valuable, what can be accomplished and how the selected work will be completed.
- Define the Sprint Goal.
- Review and select suitable Product Backlog items.
- Discuss the selected work with the team.
- Develop an initial plan for delivering the work.
Sprint Execution
During Sprint execution, Developers perform the work needed to create a usable increment. The team continuously collaborates, tests, integrates and adapts its plan as necessary while protecting the Sprint Goal.
Development
Implement selected product functionality.
Testing
Verify the developed functionality and identify defects.
Integration
Integrate completed work into the product.
Inspection
Continuously inspect progress and adapt the plan where necessary.
Sprint Review
The Sprint Review is used to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team and relevant stakeholders discuss what was accomplished and what should happen next.
Sprint Retrospective
The Sprint Retrospective focuses on improving the team's quality and effectiveness. The team identifies useful changes and decides how to apply improvements in the next Sprint.
User Story Definition and Characteristics
A User Story is a concise description of a desired capability written from the user's perspective. It explains who needs something, what they need and why they need it.
Common User Story Format
Valuable
The story should provide meaningful value to users or stakeholders.
Testable
Its expected behavior should be verifiable.
Understandable
The story should be clear enough for the team to discuss and refine.
Estimable
The team should be able to estimate its relative effort.
Acceptance Tests
Acceptance tests define conditions that a user story should satisfy to demonstrate that the expected behavior has been achieved.
Example
User Story: As a registered user, I want to log in so that I can access my account.
Acceptance Conditions:
- Valid credentials should allow successful login.
- Invalid credentials should display an appropriate error.
- The user should be directed to the appropriate account area after successful authentication.
Verifying User Stories
A user story can be verified by checking its acceptance conditions and confirming that the implemented functionality behaves as expected.
- Review the story and its acceptance criteria.
- Develop the required functionality.
- Execute appropriate tests.
- Compare actual behavior with expected behavior.
- Record and resolve identified defects.
Burn Down Chart
A Burn Down Chart is a visual representation of the amount of work remaining over time. It can help the team understand whether progress is generally aligned with the expected Sprint or release trajectory.
Vertical Axis
Represents remaining work, such as story points or tasks.
Horizontal Axis
Represents time, such as Sprint days.
Ideal Progress
Shows a reference trajectory for reducing remaining work.
Actual Progress
Shows how the team's remaining work changes during the Sprint.
Daily Scrum
The Daily Scrum is a short event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
Key Discussion Areas
- Progress toward the Sprint Goal.
- Current work and upcoming work.
- Obstacles or impediments affecting progress.
- Adjustments required in the plan.
Scrum Case Study
Case Study: Online Food Ordering System
Consider a team developing an online food ordering system. The product needs user registration, restaurant search, food selection, cart management and order tracking.
Product Goal: Develop a convenient online food ordering experience.
Product Backlog: Registration, login, restaurant search, menu browsing, cart, payment integration and order tracking.
Sprint 1: The team selects registration, login and basic restaurant search functionality.
Sprint Review: Stakeholders inspect the working functionality and provide feedback.
Retrospective: The team discusses what worked well, what caused difficulties and which improvements should be applied in the next Sprint.
Quick Revision
Scrum: Agile framework based on iterative product development.
Three Main Accountabilities: Product Owner, Scrum Master and Developers.
Three Main Artifacts: Product Backlog, Sprint Backlog and Increment.
Major Sprint Events: Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
Burn Down Chart: Shows remaining work against time.
Daily Scrum: Short event for inspecting progress toward the Sprint Goal and adapting the plan.
Important RGPV Exam Questions
- Explain the Agile Scrum Framework in detail.
- Explain Scrum roles and their responsibilities.
- Explain Scrum artifacts.
- Explain Scrum meetings/events and their objectives.
- Explain Scrum Team simulation.
- Discuss Scrum planning principles.
- Explain Product Planning and Release Planning in Scrum.
- Explain Sprint Planning and Sprint Execution.
- Explain Sprint Review and Sprint Retrospective.
- Define User Stories and explain their characteristics.
- Explain Acceptance Tests and verification of User Stories.
- What is a Burn Down Chart? Explain its purpose and interpretation.
- Explain the Daily Scrum meeting.
- Explain Scrum using a suitable case study.
- Explain the complete Sprint lifecycle with a suitable diagram.
- Differentiate between Product Backlog and Sprint Backlog.
Handwritten Notes
Get exam-oriented handwritten notes for CD604(B) Agile Software Development Unit III, including Scrum diagrams, definitions, important concepts, examples and RGPV-focused questions.