Public:Scrum: Difference between revisions

From Docs | Smarter.Codes
imported>Anand
mNo edit summary
imported>Anand
mNo edit summary
Line 100: Line 100:
|-
|-
|Attendees
|Attendees
|Scrum Team + Others(On Invitation only)
|Scrum Team + Others(Only on Invitation)
|Developers
|Developers
|Scrum Team + Stakeholders
|Scrum Team + Stakeholders
|Scrm Team Only
|Scrm Team Only
|-
|DACI
|Driver: Scrum Master<br> Approver: Product Owner<br> Contributors: Developers<br> Informed: Stakeholders
|Driver: Scrum Master<br> Approver: - <br> Contributors: Developers<br> Informed: Product Owner
|Driver: Scrum Master<br> Approver: Stakeholders <br>Contributors: Product Owner<br> Informed: Developers
|Driver: Scrum Master<br> Approver: Product Owner <br>Contributors: Scrum Team<br> Informed: -
|-
|-
|Inputs
|Inputs

Revision as of 17:34, 26 September 2022

Introduction:

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. This guideline documentation will highlight the key areas to be focused to roll-out Scrum framework for Internal Products and Consulting Projects at Smarter.Codes.

3-5-3-5 Rule of Scrum:

3 Roles 5 Events 3 Artifacts 5 Values
Product Owner Sprint Product Backlog Openness
Scrum Master Sprint Planning Sprint Backlog Courage
Scrum Team Daily Scrum Increment (Iteration) Respect
Sprint Review Focus
Sprint Retrospective Committment


Product Vision: A long term strategic business goal for the product

Key Action 1: Define the Product Goal:

As per scrum there will be only one product goal at a given point of time. But for Startup studio like Smarter.Codes we could have a monthly or quarterly intermediate goals to achieve the product vision step-by-step..

Key Action 2: Product Backlog Refinement

Product Backlog refinement is the act of breaking down and further defining Product Backlog items (PBI) into smaller more precise items (User Stories).

Refinement Meeting:


Key Action 3 : Define the Sprint Goal:

Immediate measurable goal based on value delivered as features/increment to achieve the current monthly/quarterly Product Goal.

Key Action 4 : Sprint Planning

Text

Key Action 5 : Daily Scrum

Text

Key Action 6 : Sprint Review

Text

Key Action 7 : Sprint Retrospective

Text

Summary of Agile Ceremonies:

Details / Ceremony Sprint Planning Daily Scrum Sprint Review Sprint Retrospective
Duration Max 8 Hours for 1 month sprint 15 Mins Max 4 Hours Max 3 Hours
Purpose Decide 'WHY' are we doing this Sprint, 'WHAT' are we doing to do in the Sprint, 'HOW' are we going to do the work chosen for this Sprint Inspect the progress towords the GOAL and ADAPT the plan Inspect the Outcome of the Sprint and Determine future adaptation Way to Improve Effectiveness & Quality by Creating an ACTION List
Attendees Scrum Team + Others(Only on Invitation) Developers Scrum Team + Stakeholders Scrm Team Only
DACI Driver: Scrum Master
Approver: Product Owner
Contributors: Developers
Informed: Stakeholders
Driver: Scrum Master
Approver: -
Contributors: Developers
Informed: Product Owner
Driver: Scrum Master
Approver: Stakeholders
Contributors: Product Owner
Informed: Developers
Driver: Scrum Master
Approver: Product Owner
Contributors: Scrum Team
Informed: -
Inputs Product Backlog, Capacity, Past Performance, Last Increment, Definition of Done Sprint Backlog Increment, Product Backlog, Sprint Backlog Improvements on Individuals, Interactions, Process, Tools, Definition of Done
Outputs Sprint Backlog Sprint Backlog Review of the Product Backlog, Budget, Timeline, Progress check against Product Goal List of Action Items for improvement