flowcracker scrum ceremonies
TRANSCRIPT
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum
Speed, Scale, Skills, Simplicity
http://www.flowcracker.com
1
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Principle Consultant – Durgaprasad B. R
2
Durgaprasad B. R 20+ Years of IT experience B. E (E & C), Alumni of
IIM,Bangalore Certifications
PMI-PMP, PMI-ACP SCP from Scaled
Agile Academy
Durgaprasad B. R 20+ Years of IT experience B. E (E & C), Alumni of
IIM,Bangalore Certifications
PMI-PMP, PMI-ACP SCP from Scaled
Agile Academy
Developer, Project/ProgramManager, Location DeliveryHead, Agile Coach
Industries: Telecom,Healthcare, ConsumerElectronics, Automotive
Past few Clients: Avaya,Nortel, ALU, Microsoft,Qualcomm, Intel, Toshiba,Continental
Technologies: WebTechnologies, Embedded,Legacy large systems
Developer, Project/ProgramManager, Location DeliveryHead, Agile Coach
Industries: Telecom,Healthcare, ConsumerElectronics, Automotive
Past few Clients: Avaya,Nortel, ALU, Microsoft,Qualcomm, Intel, Toshiba,Continental
Technologies: WebTechnologies, Embedded,Legacy large systems
Led large Telecomprograms, IP Switches,Voice Messaging System,Contact Center, ConsumerElectronics products,Automotive productdevelopment
Well versed in new agetechnologies as well as sun-set technologies
Trained and coachedindividuals and teams onAgile, Kanban, Scrum andSAFe methodologies
Regular public workshopson PMP, ACP and SAFeCertifications
Led large Telecomprograms, IP Switches,Voice Messaging System,Contact Center, ConsumerElectronics products,Automotive productdevelopment
Well versed in new agetechnologies as well as sun-set technologies
Trained and coachedindividuals and teams onAgile, Kanban, Scrum andSAFe methodologies
Regular public workshopson PMP, ACP and SAFeCertifications
http://www.flowcracker.in/about-durgaprasad-b-r/Contact: [email protected]. Cell: 9845558474
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
LeanDevelopment
Toward beingSAFe™
Agile Scrum
KanbanXP – ExtremeProgramming
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
THE OATH OF NON-ALLEGIANCE
I promise not to exclude from consideration any idea based on its source, but toconsider ideas across schools and heritages in order to find the ones that best suit thecurrent situation.
- DURGAPRASADhttp://oathofnonallegiance.com/
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
LeanDevelopment
Toward beingSAFe™
Agile Scrum
KanbanXP – ExtremeProgramming
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum MasterResponsible for ProcessSupport the teamRemove Impediments
Product OwnerPrioritizationVoice of CustomerOwns the Product Backlog
Scrum TeamCross FunctionalDeliver Each Sprint
ProductBacklog
Daily Scrum(15 min)- 3 Questions
2-4 weeks Sprint
Refine ProductBacklog
(8-10% for nextSprint)
PotentiallyShippable Product
IncrementMinimumReleasableFeatures
(Use burndowncharts & dashboards
to track progress)
Scrum FLOW
TDD, ATDD, SimpleDesign, Coding Standards,
Pair Programming,Refactoring, CI, CD,Test Automation,
………. .
EngineeringPractices
I & A
ReleasePlanning
SprintPlanning
(2-4 hr)PrioritizationTask Breakdown & EstimateTeam CommitmentSprint Backlog
SprintRetrospective(2-3 hr)- Continuously
Improve
SprintReview(2-4 hr)Demo
SprintBacklog
VisionVision
AnalyzeDesignBuild
IntegrateTest
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
CeremoniesCeremony Frequency DurationStrategy Typically once a year 4-16 hoursRelease Planning 1st day of every release 4-8 hoursSprint Planning 1st day of every iteration 2-4 hoursSprint Backlog Grooming Mid Sprint or every week 1-2 hoursSprint Review Last day of the iteration 1-2 hoursRetrospective Last day of the iteration 1-2 hoursDaily standup/Scrum Every day 15 minutes
Effective ceremonies/routines build habit and habit's build character(both for team and individuals)
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Strategy
Agenda• Involve all stakeholders and list
down their interests• Question why this is required
Attendees:PO, SM, Team, Key StakeholdersWhen: Typically once a yearDuration: 4-16 hours, done offsiteInput:Market Reports, Customer Feedback,Management inputs, Current statusOutput:Vision and strategy, Key assumptions andissues, Delivery datesKey Obstacles:Poor understanding of market needs andmarket sizingPoor stakeholder interests and commitment
To define program strategy, vision, goals
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Release Planning
Agenda• Review meeting agenda & guidelines• PO reviews product vision, strategy
and goals, key dates & milestones• PO presents draft prioritized product
backlog,• MMF Set planning & analysis• Clarity team questions• Teams perform
– High level Estimate of user stories (storypoint/ideal days etc.)
– Estimate Initial capacity, velocity– Finalize release plan which contains
delivery objective• Record Key decisions, assumptions,
risks and issues• Stakeholders consensus is achieved
Attendees:PO, SM, Team, Key StakeholdersWhen: 1st day of every releaseDuration: 4-8 hoursInput:Vision and Strategy, Key assumptions andissues, Delivery dates, VelocityOutput:Release Plan, assumptions/issues, Deliverydates, Release backlogKey Obstacles:Lack of acceptance of team based estimation& planning, realization that the plan is notfrozen and will change, Inability to negotiatescope, time and budget constraints
Articulate high level functional priorities, dates to the team andstakeholders
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Sprint Planning
Agenda• Review meeting agenda & guidelines• Part 1: Sprint goals & deliverables
– PO proposes the product backlog forreview
– Team ideally defines iteration goal– Larger stories are broken– Team selects stories that can be
completed with the sprint– Review Definition of Done for work items– PO Shares his goals & clarifies doubts
• Part 2: Task Planning– Team breaks user stories into tasks and
clearly defines estimation criteria– Estimates each task in hours– Team commits to the tasks
Attendees:PO, SM, TeamWhen: 1st day of every sprintDuration: 2-4 hoursInput:Prioritized product backlog, velocity, team capacity,backlog groomingOutput:Iteration goals, prioritized sprint backlog,acceptance tests, task breakdown, updated kanbanwallKey Obstacles:Driving into too much details & designing eachfeature instead of designing the tasksTeams not having the final sayDependencies not being sorted outStories when large needs to be broken down
Purpose is to decide on the sprint goals, deliverables and task planning
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Backlog Grooming/Refinement
Agenda• Review meeting agenda & guidelines• Goal: Identify finely groomed backlog
– PO proposes the product backlog forreview
– Discussing high priority/ new PBI (avoid)for next 2 sprints
– Splitting PBI’s– Update on spikes/dependencies for PBI– Prepare /refining acceptance criteria– Estimating PBI– PO Shares his goals & clarifies doubts– Team selects stories that can be
completed within next sprint– Look down the backlog for new
PBI’s/Spikes, dependencies etc. to betaken up next
Attendees: PO, SM, TeamWhen: Mid Sprint/Weekly (except on first and lasttwo days of sprint)Duration: 2 hrsInput: Prioritized product backlog, PBI details andinitial acceptance tests, velocity, team capacity,backlog groomingOutput:Finely groomed backlog90% of details / acceptance tests lightlydocumentedKey Obstacles:Teams not having the final sayDependencies not being sorted outStories when large needs to be broken downTeams should not breakdown stories into tasks
Helps improve sprint planning efficiency, reduce uncertainity andunknowns
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Sprint Review
Agenda• Review meeting agenda &guidelines• Team walks through completed
functionality with PO• Team identifies any incomplete
stories• The PO moves / splits incomplete
stories or backlog items back intoproduct backlog
• PO closes out iteration and acceptsappropriate functionality
• Team demonstrates working softwareto interested stakeholders
• Any open issues/impediments andaction items are noted and assigned
Attendees:PO, SM, Team, Key StakeholdersWhen: last day of every releaseDuration: 1-2 hoursInput:Incremental delivery, list of issues &impedimentsOutput:Incremental Demo, List of suggestedchanges, closure of accepted user storiesKey Obstacles:PO not being present during the meeting ornot being clear about the feedback.
Demonstrated work done and get PO/customer feedback
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Daily Standup
AgendaThe 3 questions which needs to beanswered by every team members• What have you done since we met
last time?• What you plan to do till we meet next
time?• Any impediments that affects your
work?
Attendees: PO (optional), SM, TeamWhen: Every working dayDuration: 15 min. (ideally just before lunch)Input: Individual team member updatesOutput:Team communication and understanding ofoverall progress, critical issues, impediments,Updated Kanban wallKey Obstacles:All team members not being presentNon core members consume meeting timeGeneral discussion or detailed discussionSM or PO driving the meetingNot maintaining same time, place
Peer update and coordinate development efforts
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Retrospective
Agenda• Review meeting agenda and
guidelines• Team reviews what went well during
the last sprint• Team reviews what did not go well• Identify top 3 most important issues
to fix during the next iteration• Any other issues/impediments
affecting the team are discussed
Attendees: PO (optional), SM (optional),TeamWhen: Last day of the sprintDuration: 1 to 2 hoursInput: Details of accomplishments from prioriteration, list of issues/ impedimentsOutput:Prioritized impediments, changes tostories/backlog, action plan for impromentwith dates and ownerKey Obstacles:Focusing on people instead of processChickens taking over the meeting Team notopen to raise and discuss issuesNo problem … is problem – Toyota saying
Inspect & Adapt team practices & processes that impact team progress
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum MasterResponsible for ProcessSupport the teamRemove Impediments
Product OwnerPrioritizationVoice of CustomerOwns the Product Backlog
Scrum TeamCross FunctionalDeliver Each Sprint
ProductBacklog
Daily Scrum(15 min)- 3 Questions
2-4 weeks Sprint
Refine ProductBacklog
(8-10% for nextSprint)
PotentiallyShippable Product
IncrementMinimumReleasableFeatures
(Use burndowncharts & dashboards
to track progress)
Scrum FLOW
TDD, ATDD, SimpleDesign, Coding Standards,
Pair Programming,Refactoring, CI, CD,Test Automation,
………. .
EngineeringPractices
I & A
ReleasePlanning
SprintPlanning
(2-4 hr)PrioritizationTask Breakdown & EstimateTeam CommitmentSprint Backlog
SprintRetrospective(2-3 hr)- Continuously
Improve
SprintReview(2-4 hr)Demo
SprintBacklog
AnalyzeDesignBuild
IntegrateTest
Vision + Roadmap
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum – 2 Week Team CalendarWeek 1
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum – 2 Week Team CalendarWeek 2
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Scrum MasterResponsible for ProcessSupport the teamRemove Impediments
Product OwnerPrioritizationVoice of CustomerOwns the Product Backlog
Scrum TeamCross FunctionalDeliver Each Sprint
ProductBacklog
Daily Scrum(15 min)- 3 Questions
2-4 weeks Sprint
Refine ProductBacklog
(8-10% for nextSprint)
PotentiallyShippable Product
IncrementMinimumReleasableFeatures
(Use burndowncharts & dashboards
to track progress)
Scrum FLOW
TDD, ATDD, SimpleDesign, Coding Standards,
Pair Programming,Refactoring, CI, CD,Test Automation,
………. .
EngineeringPractices
I & A
ReleasePlanning
SprintPlanning
(2-4 hr)PrioritizationTask Breakdown & EstimateTeam CommitmentSprint Backlog
SprintRetrospective(2-3 hr)- Continuously
Improve
SprintReview(2-4 hr)Demo
SprintBacklog
VisionVision
AnalyzeDesignBuild
IntegrateTest
Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.
Flow Cracker#7, 3rd Floor, Srishti Building,8th Main, Basaveshwar Nagar,Bangalore - 560079
Email :
[email protected] [email protected]
Cell: +91 984 555 8474
ThankYou
19