Public:Scrum

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
Developers	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.

Ceremony Event 1 : Sprint Planning

The Product Owner will come with objective in mind and a tentative list for the upcoming spring. Product Owner, Developers will discuss and Scrum Master will facilitate to decide upon: WHAT, WHO, WHEN, HOW. Scrum team will decide on the final list of work to be worked upon in the current sprint.

Ceremony Event 2 : Daily Scrum

Meeting is to help the developers to improve collaboration, knowledge and accoutability towards the sprint backlog and promote quick decision making. Developers often meet immediately with peer for a detailed discussion.

Ceremony Event 3 : Sprint Review

Product Owner presents the progress towards the Product Goal and explains what Product backlog items are "Done" and what has not been done. Key chanllenges are presented by the scrum team to the stakeholders.

Ceremony Event 4 : Sprint Retrospective

Discussion with in the scrum team to inspect itself with regards to the individuals, interactions, quality, process, tools. Scrum Team will plan to increase product quality by improving the work progress or Definition-of-done. Scrum master sets the stage ensures the meeting is positive, productive and engate every team member in gathering, filtering, generating insights on Improvements. Pros & COns are discussed and action items for improvements are planned for the next sprint.

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 SPRINT GOAL using Burn down chart, review the work, discuss impediments, ADAPT a plan and update the sprint backlog	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 / Task Board	Increment, Product Backlog, Sprint Backlog	Improvements on Individuals, Interactions, Process, Tools, Definition of Done
Outputs	Sprint Backlog	Updated sprint backlog	Review of the Product Backlog, Budget, Timeline, Progress check against Product Goal	List of Action Items for improvement

Characteristics for the 3 roles in Scrum:

Product Owner:

1. Understanding of the market, Skepticism, Independent Thinker
2. Good in communication (Ability to say no)
3. Negotiation
4. PO should be good networker, work with partners (industry leader, visionery)
5. Very much available to the team (to accept and refine the backlog items)

Developers (Design, Engg, DevOps...)

1. Team members should be full time on a project.
2. Should not be shared across projects. At any given time member should be allocated to only one project.
3. Cross-functional and self-organized, team members to have core skills and ability to deliver the backlog items which are picked for the sprint

Scrum Master:

1. Probing on best performance out of the team
2. Should be Change Agent, team can communicate with out hesitnation (SM should be approachable)
3. Good networker
4. Active learner (willing to try out new approaches so team can get onto a high performance)
5. Enforcer of the agile discipline
6. Is NOT / Does not a MicroManage the team
7. Does not order / influence using authority