Share
Embed
A Tale of Two Teams
A look at scrum and kanban practices, and how they can be suited to fit different teams.
Dana Jones
October 13, 2018
Transcript
52 slides
-
Contingency Theory Fred Edward Fiedler Born in Austria, 1922 Leadership
approach should be based on: Leader's personality Situation -
Project Managers Communicate between stakeholders Evaluate effort and reward of
ideas Plan the product or client roadmap -
Project Managers Communicate between stakeholders Evaluate effort and reward of
ideas Plan the product or client roadmap Adjust to change -
Project Managers Communicate between stakeholders Evaluate effort and reward of
ideas Plan the product or client roadmap Adjust to change Help teams ship -
Scrum Rituals Backlog Grooming Sprint Planning Sprint Kickoff Daily Standup
/ Daily Scrum PR Review Launch Sprint Demo Sprint Review Sprint Retrospective -
"And Friends" Rituals One-on-One (1:1) Skip-Level Meeting Team Sync/ Check-in
Five Why's Decomposition Ticket Pointing Grooming -
Team Size Development Experience Composition of Team (Roles) Team Members
Personalities Project Manager Personality Length of Engagement Location Circadian Rhythms Remote Experience Purpose of Team Employment Status Time-life of Team Project Deadline Budget Company Culture -
Team Size Development Experience Composition of Team (Roles) Team Members
Personalities Project Manager Personality Length of Engagement Location Circadian Rhythms Remote Experience Purpose of Team Employment Status Time-life of Team Project Deadline Budget Company Culture Upper Management Support -
Team A All collocated Junior - Mid Long-term Maintenance Permanent
employees Team B Distributed Mid - Senior Short-term Framework upgrade Contractors -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Team A -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Technical development Team A -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Technical development Professional development Team A -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Technical development Professional development Cultural reinforcement Team A -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Technical development Professional development Cultural reinforcement Written documentation Team A -
All collocated Junior - Mid Long-term Maintenance Permanent employees More
frequent touchpoints Technical development Professional development Cultural reinforcement Written documentation Well-defined processes Team A -
Team A Sprint Planning Daily Standup / Daily Scrum Sprint
Review Sprint Retrospective -
Team A Sprint Planning Sprint Kickoff Daily Standup / Daily
Scrum Sprint Review Sprint Retrospective -
Team A Sprint Planning Sprint Kickoff Daily Standup / Daily
Scrum Sprint Review Sprint Retrospective Ticket Pointing -
Team A Sprint Planning Sprint Kickoff Daily Standup / Daily
Scrum PR Review Sprint Review Sprint Retrospective Ticket Pointing -
Team A Sprint Planning Sprint Kickoff Daily Standup / Daily
Scrum PR Review Sprint Review Sprint Retrospective One-on-One (1:1) Skip-Level Meeting Ticket Pointing -
Distributed Mid - Senior Short-term Framework upgrade Contractors Fewer touchpoints
Technical progress Team B -
Distributed Mid - Senior Short-term Framework upgrade Contractors Fewer touchpoints
Technical progress Time and budget pressure Team B -
Distributed Mid - Senior Short-term Framework upgrade Contractors Fewer touchpoints
Technical progress Time and budget pressure Cultural protection Team B -
Distributed Mid - Senior Short-term Framework upgrade Contractors Fewer touchpoints
Technical progress Time and budget pressure Cultural protection Well-curated backlog Team B -
Distributed Mid - Senior Short-term Framework upgrade Contractors Fewer touchpoints
Technical progress Time and budget pressure Cultural protection Well-curated backlog Well-defined processes Team B -
Team B PR Review Ticket Pointing Team Sync/ Check-in Five
Why's Decomposition -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
Sprint Kickoff Checklist Scope is defined (time, features, budget) Product
backlog is well groomed Team has clear understanding of sprint objectives and processes Team members are free of other work All cards in the sprint backlog are pointed Work in the sprint backlog is achievable within the course of the sprint There is a plan for removing any identified blockers -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
When Meetings Need to Die Attendees consistently decline invites They
aren't achieving their objectives There is no clear objective They are often canceled They can be replaced with an email People are nodding off, checking laptops or phones, not making eye contact -
Photo Credits http://www.ila-net.org/LeadershipLegacy/fred_fiedler.html http://scream-queens.wikia.com/wiki/File:Tumbleweed.gif http://speedendurance.com/2012/08/07/lolo-jones-justin-gatlin- jamaican-toe-drag-revisited/ https://www.her.ie/life/trouble-sleeping-this-trick-can-help-you-nod-off-in- just-60-seconds-239893 We're Hiring
https://boards.greenhouse.io/abstract