Flow of Work SCRUM

In this lesson, we dive into the Scrum workflow—a favored strategy for organizations that follow the Scrum methodology in managing sprints. By moving tasks from the product backlog into sprints, Scrum supports an iterative approach to development. The product backlog, organized by features and epics, feeds into a workflow with distinct states such as "New," "Approved," "Committed," "Done," and "Removed."

Scrum templates are particularly advantageous for managing complex projects that constantly evolve. They support rapid iterative development and provide teams with the flexibility to adapt quickly to changing requirements. Emphasis on team autonomy fosters self-organization and independent decision-making. Regular feedback from stakeholders ensures that product development aligns with user needs and business objectives.

Scrum workflows also incorporate epics, which serve as high-level overviews of large goals or initiatives that span multiple sprints or release cycles. These epics are subsequently deconstructed into smaller, more manageable components:

• Features: Subsets of epics representing specific functionalities or requirements.
• Product Backlog Items (PBIs): Individual items—such as features, bugs, or tasks—that are prioritized for sprint work.
• Tasks: Specific actions derived from PBIs, including coding, testing, or documentation, which track the remaining work.
• Bugs: Issues identified during or after development; they are treated as PBIs and prioritized for resolution.
• Impediments: Obstacles that may occur at any phase and need prompt resolution to maintain workflow continuity.

The Scrum process employs a Kanban board for tracking PBIs and bugs, while a task board is used to manage tasks that track remaining work.

Lifecycle of a Backlog Item in Scrum

The lifecycle of a backlog item in Scrum begins when a new entry—be it a feature, bug, or task—is added to the backlog to capture a requirement or change.

1. New Backlog Item: The journey starts with the creation of a backlog item.
2. Product Owner Approval: The product owner reviews the item to ensure that it aligns with project goals and warrants further development.
3. Sprint Commitment: Once approved, the item is pulled into a sprint where the development team commits to its completion, transitioning the item to the "Committed" state.
4. In-Progress Tasks: As work advances, additional tasks might be identified and added to the backlog to support the completion of the item.
5. Completion: When all criteria and acceptance conditions are met, the backlog item is marked as "Done."
6. Removal: In certain cases, if a backlog item no longer aligns with business objectives—either before or after approval—it may be removed from the backlog.

This overview encapsulates the iterative and collaborative nature of the Scrum process. By clearly defining the stages from creation to completion, Scrum offers a flexible and efficient framework that promotes continuous improvement and adaptive planning.

For further insights into agile methodologies and Scrum best practices, explore additional resources:

• Scrum Guide
• Agile Alliance
• Atlassian Agile Tutorials