Tuckman was wrong by Doc Norton at #AgileIndia2019

•

1 gostou•696 visualizações

Stable Teams have long been a known and accepted leading practice in agile. And Tuckman's stages of group development proves the need for stable teams, right? But what if that's not correct? Doc posits that Tuckman's is actually a disproven theory that none-the-less mysteriously persists. What if, by stabilizing teams, we solved a completely different problem? And what if by de-stabilizing teams we could better solve other problems? More details: https://confengine.com/agile-india-2019/proposal/8521/tuckman-was-wrong Conference link: https://2019.agileindia.org

Apresentações e oratória

@DocOnDev :: #AgileIndia2019
Tuckman Was Wrong!

@DocOnDev :: #AgileIndia2019
Stable Teams

@DocOnDev :: #AgileIndia2019
Stable Teams
– Scrum PLoP Stable Teams Pattern
“Keep teams stable and avoid shufﬂing people
around between teams. Stable teams tend to get
to know their capacity, which makes it possible for
the business to have some predictability.”

@DocOnDev :: #AgileIndia2019
Why Stable Teams?

@DocOnDev :: #AgileIndia2019
Because Tuckman’s
Forming Storming Norming Performing

@DocOnDev :: #AgileIndia2019
Performance
Time
Because Tuckman’s
Forming Storming Norming Performing

@DocOnDev :: #AgileIndia2019
Performance
Forming
Storming
Norming
Performing
Because Tuckman’s
Have you Experienced this?

@DocOnDev :: #AgileIndia2019
Performance
Forming
Storming
Norming
Performing
Because Tuckman’s
- OR -
Have you Experienced this?

@DocOnDev :: #AgileIndia2019
Performance
Time
Forming
Storming
Norming
Performing
Tuckman’s?

@DocOnDev :: #AgileIndia2019
Performance
Time
Forming
Storming
Tuckman’s?

@DocOnDev :: #AgileIndia2019
Performance
Time
Forming
Storming
Norming
Performing
Storming
Norming
Storming
Norming
Norming
Storming
Tuckman’s?

@DocOnDev :: #AgileIndia2019
ActivityOccurrence
Time
Forming
Performing
Storming
Norming
Tuckman’s (For real)

@DocOnDev :: #AgileIndia2019
The problem wasn’t
Because Tuckman’s

@DocOnDev :: #AgileIndia2019
BUT 
Stable teams did make
things better.

@DocOnDev :: #AgileIndia2019
So, if the problem wasn’t 
Because Tuckman’s?

@DocOnDev :: #AgileIndia2019
So, if the problem 
wasn’t 
Because Tuckman’s?
What Was It?

@DocOnDev :: #AgileIndia2019
What if the problem was 
Because Resources?

@DocOnDev :: #AgileIndia2019
Because Resources

@DocOnDev :: #AgileIndia2019
Tasks of 8 hours each
8 hours 16 hours 24 hours 32 hours
Start All at Once
Because Resources

@DocOnDev :: #AgileIndia2019
Start All at Once
8 hours 16 hours 24 hours 32 hours 40 hours 48 hours8 hours 16 hours 24 hours 32 hours
Because Resources

@DocOnDev :: #AgileIndia2019
8 hours 16 hours 24 hours 32 hours
Finish One at a Time
Start All at Once
8 hours 16 hours 24 hours 32 hours 40 hours 48 hours
Because Resources

@DocOnDev :: #AgileIndia2019
8Hoursofworkcompletedin…
0
3.5
7
10.5
14
Active Project Count
1 2 3 4 5
8
9.6
10.88
12.19
13.62
Because Resources
8 hours 16 hours 24 hours 32 hours 40 hours 48 hours

@DocOnDev :: #AgileIndia2019
TaskTime
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Because Resources

@DocOnDev :: #AgileIndia2019
Because Resources
8Hoursofworkcompletedin…
0
40
80
120
160
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
1
# of Projects

@DocOnDev :: #AgileIndia2019
Because Resources
8Hoursofworkcompletedin…
0
40
80
120
160
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
1
2
# of Projects

@DocOnDev :: #AgileIndia2019
8Hoursofworkcompletedin…
0
40
80
120
160
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
1
2
3
Because Resources
# of Projects

@DocOnDev :: #AgileIndia2019
8Hoursofworkcompletedin…
0
40
80
120
160
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
1
2
3
4
Because Resources
# of Projects

@DocOnDev :: #AgileIndia2019
8Hoursofworkcompletedin…
0
40
80
120
160
Allocation
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
1
2
3
4
5
Because Resources
# of Projects

@DocOnDev :: #AgileIndia2019
Stable Teams 
Solved 
Because Resources

@DocOnDev :: #AgileIndia2019
“…different areas of code are going to need
different skill-sets at different times, and for that
reason we need [people] to go and work on
those particular areas at different times… None
of this is basically static. It’s very fluid. And if you
have the ability to reteam, then you are able to go
do this sort of thing consistently.”
– Michael Feathers

@DocOnDev :: #AgileIndia2019
“… None of this is basically static. It’s
very fluid. And if you have the ability
to reteam, then you are able to go
do this sort of thing consistently.”
– Michael Feathers

@DocOnDev :: #AgileIndia2019
reteam starters

@DocOnDev :: #AgileIndia2019
Connection
Diversity
Excellence
Autonomy
Four Factors
lead to better team
performance and
c o l l e c t i v e
satisfaction…
reteam starters

@DocOnDev :: #AgileIndia2019
reteam examples

@DocOnDev :: #AgileIndia2019
reteam
examples
Cabals at Valve

@DocOnDev :: #AgileIndia2019
reteam
examples
“Spotify Model”

@DocOnDev :: #AgileIndia2019
reteam patterns

@DocOnDev :: #AgileIndia2019
reteam
patterns
Socialization

@DocOnDev :: #AgileIndia2019
reteam
patterns
Mitosis

@DocOnDev :: #AgileIndia2019
reteam
patterns
Volunteer Fire
Department

@DocOnDev :: #AgileIndia2019
reteam
patterns
Trading Places

@DocOnDev :: #AgileIndia2019
“Reteaming is
inevitable. You
might as well
get good at
it.”
- Nayan Hajratwala

@DocOnDev :: #AgileIndia2019
Tuckman Was Wrong!
Thank You!

Mais conteúdo relacionado

Mais procurados

Failure as Success Devops Roadtrip Seattle 2016VictorOps

Chris Girolamo It's the Product not the Project 19 Mar 14LianaEliz222

Agile in Offshore developmentHiroshi KURABAYASHI

Agility ≠ SpeedKevlin Henney

Startups, Clones and MetricsHenrik Berglund

Due Date The Root Of All EvilsKamon Treetampinij

Mais procurados (6)

Failure as Success Devops Roadtrip Seattle 2016

Chris Girolamo It's the Product not the Project 19 Mar 14

Agile in Offshore development

Agility ≠ Speed

Startups, Clones and Metrics

Due Date The Root Of All Evils

Semelhante a Tuckman was wrong by Doc Norton at #AgileIndia2019

Tuckman Was WrongDoc Norton

Data driven devops as presented at QCon London 2018Baruch Sadogursky

Transform Your Approach To Talent By Leveraging Transparency and Data | Talen...LinkedIn Talent Solutions

How to Leverage Content Curation in SEO #BrightonSEOAleyda Solís

Creating a Most Loved WorkplaceQualtrics

Innovation - road to value TopConf Nov2015Alek Kozlov

Beginner's Guide to Agile Release PlanningPayton Consulting

Scaling Engineering by Hacking Conway’s Law - Geecon,2022Aviran Mordo

To Estimate or Not to Estimate, is that the Question?TechWell

[오픈소스컨설팅]Session 2 2. Future of Team CollaborationOpen Source Consulting

Data Driven DevOpsLeon Stigter

Taming a beast - Cloudnative London 2018Mike Chernev

Manage Flow - in search of flow efficiencyChris McDermott

The Technical Debt Trap - NDC Oslo 2014Doc Norton

Data driven devops as presented at Codemash 2018Baruch Sadogursky

Future Skills, Future Work: Projecting the Future, Challenge Paper Six, 16 Ap...Association for Project Management

Agile v agility_v4_mdMarc Danziger

Future is AgileOliver Szymanski

2019 AFITC Fantastic outcomes and how to measure them by Cheryl HammondCheryl M Hammond

Enacting Scrum - What it takes to maximize the chances for a successful adopt...ITCamp

Semelhante a Tuckman was wrong by Doc Norton at #AgileIndia2019 (20)

Tuckman Was Wrong

Data driven devops as presented at QCon London 2018

Transform Your Approach To Talent By Leveraging Transparency and Data | Talen...

How to Leverage Content Curation in SEO #BrightonSEO

Creating a Most Loved Workplace

Innovation - road to value TopConf Nov2015

Beginner's Guide to Agile Release Planning

Scaling Engineering by Hacking Conway’s Law - Geecon,2022

To Estimate or Not to Estimate, is that the Question?

[오픈소스컨설팅]Session 2 2. Future of Team Collaboration

Data Driven DevOps

Taming a beast - Cloudnative London 2018

Manage Flow - in search of flow efficiency

The Technical Debt Trap - NDC Oslo 2014

Data driven devops as presented at Codemash 2018

Future Skills, Future Work: Projecting the Future, Challenge Paper Six, 16 Ap...

Agile v agility_v4_md

Future is Agile

2019 AFITC Fantastic outcomes and how to measure them by Cheryl Hammond

Enacting Scrum - What it takes to maximize the chances for a successful adopt...

Mais de Agile India

Design Teams are a Design Exercise by Phillip Joe at #AgileIndia2019Agile India

Keeping hundreds of code repositories consistent, and staying sane by Vincent...Agile India

The End is Nigh! Signs of Transformation Apocalypse by Alex Sloley at #AgileI...Agile India

Strategic Domain-Driven Design by Nick Tune at #AgileIndia2019Agile India

Acceptance Testing for Continuous Delivery by Dave Farley at #AgileIndia2019Agile India

All track development - (or how we dropped the collective ego and created a p...Agile India

Open Salaries: from employees to managing partners by Alexey Voronin at #Agil...Agile India

Scaling Enterprise Agility amidst Cross Border Merger by Rocky Woestenborghs ...Agile India

InfraOps Agility - A Sysad's Perspective by Dushyanth Harinath at #AgileIndia...Agile India

Going for 10X: Building teams in a Hyper-Competitive Market by Jacob Singh at...Agile India

Principle 11 needs to go! by Ken France at #AgileIndia2019Agile India

Becoming the Catalyst - The Spark of Change that Will Move Your Team Forward ...Agile India

Branding within your UX: The secret to creating loyal customers by Bill Beard...Agile India

Build Agile Organization: Lessons Learned from Aikido by Marc Gong at #AgileI...Agile India

Security considerations while deploying Containerized Applications by Neepend...Agile India

Cloud Native in the US Federal Government by Jez Humble at #AgileIndia2019Agile India

Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India

Reactive Systems by Dave Farley at #AgileIndia2019Agile India

Collaboration Contracts by Diane Zajac & Doc Norton at #AgileIndia2019Agile India

7 Steps to Design, Build, and Scale an AI Product by Allie Miller at #AgileIn...Agile India

Mais de Agile India (20)

Design Teams are a Design Exercise by Phillip Joe at #AgileIndia2019

Keeping hundreds of code repositories consistent, and staying sane by Vincent...

The End is Nigh! Signs of Transformation Apocalypse by Alex Sloley at #AgileI...

Strategic Domain-Driven Design by Nick Tune at #AgileIndia2019

Acceptance Testing for Continuous Delivery by Dave Farley at #AgileIndia2019

All track development - (or how we dropped the collective ego and created a p...

Open Salaries: from employees to managing partners by Alexey Voronin at #Agil...

Scaling Enterprise Agility amidst Cross Border Merger by Rocky Woestenborghs ...

InfraOps Agility - A Sysad's Perspective by Dushyanth Harinath at #AgileIndia...

Going for 10X: Building teams in a Hyper-Competitive Market by Jacob Singh at...

Principle 11 needs to go! by Ken France at #AgileIndia2019

Becoming the Catalyst - The Spark of Change that Will Move Your Team Forward ...

Branding within your UX: The secret to creating loyal customers by Bill Beard...

Build Agile Organization: Lessons Learned from Aikido by Marc Gong at #AgileI...

Security considerations while deploying Containerized Applications by Neepend...

Cloud Native in the US Federal Government by Jez Humble at #AgileIndia2019

Building and Scaling High Performing Technology Organizations by Jez Humble a...

Reactive Systems by Dave Farley at #AgileIndia2019

Collaboration Contracts by Diane Zajac & Doc Norton at #AgileIndia2019

7 Steps to Design, Build, and Scale an AI Product by Allie Miller at #AgileIn...

Último

Dreaming Music Video Treatment _ Project & Portfolio IIINhPhngng3

My Presentation "In Your Hands" by Halle Baileyhlharris

Proofreading- Basics to Artificial Intelligence Integration - Presentation:Sl...David Celestin

Report Writing Webinar TrainingKylaCullinane

Uncommon Grace The Autobiography of Isaac FolorunsoKayode Fayemi

Bring back lost lover in USA, Canada ,Uk ,Australia ,London Lost Love Spell C...amilabibi1

in kuwait௹+918133066128....) @abortion pills for sale in Kuwait CityAbortion pills in Kuwait Cytotec pills in Kuwait

lONG QUESTION ANSWER PAKISTAN STUDIES10.lodhisaajjda

AWS Data Engineer Associate (DEA-C01) Exam Dumps 2024.pdfSkillCertProExams

Digital collaboration with Microsoft 365 as extension of DrupalFabian de Rijk

Dreaming Marissa Sánchez Music Video Treatmentnswingard

ICT role in 21st century education and it's challenges.pdfIslamia university of Rahim Yar khan campus

Jual obat aborsi Jakarta 085657271886 Cytote pil telat bulan penggugur kandun...ZurliaSoop

Introduction to Artificial intelligence.thamaeteboho94

Unlocking Exploration: Self-Motivated Agents Thrive on Memory-Driven CuriosityHung Le

Zone Chairperson Role and Responsibilities New updated.pptxlionnarsimharajumjf

SOLID WASTE MANAGEMENT SYSTEM OF FENI PAURASHAVA, BANGLADESH.pdfMahamudul Hasan

Tuckman was wrong by Doc Norton at #AgileIndia2019

1. @DocOnDev :: #AgileIndia2019 Tuckman Was Wrong!

2. @DocOnDev :: #AgileIndia2019 Doc Norton

3. @DocOnDev :: #AgileIndia2019 Tuckman Was Wrong!

4. @DocOnDev :: #AgileIndia2019 Stable Teams

5. @DocOnDev :: #AgileIndia2019 Stable Teams – Scrum PLoP Stable Teams Pattern “Keep teams stable and avoid shufﬂing people around between teams. Stable teams tend to get to know their capacity, which makes it possible for the business to have some predictability.”

6. @DocOnDev :: #AgileIndia2019 Why Stable Teams?

7. @DocOnDev :: #AgileIndia2019 Because Tuckman’s Forming Storming Norming Performing

8. @DocOnDev :: #AgileIndia2019 Performance Time Because Tuckman’s Forming Storming Norming Performing

9. @DocOnDev :: #AgileIndia2019 Performance Time Because Tuckman’s Forming Storming Norming Performing

10. @DocOnDev :: #AgileIndia2019 Performance Forming Storming Norming Performing Because Tuckman’s Have you Experienced this?

11. @DocOnDev :: #AgileIndia2019 Performance Forming Storming Norming Performing Because Tuckman’s - OR - Have you Experienced this?

12. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Norming Performing Tuckman’s?

13. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Norming Performing Tuckman’s?

14. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Tuckman’s?

15. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Norming Performing Tuckman’s?

16. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Norming Performing Storming Norming Storming Norming Norming Storming Tuckman’s?

17. @DocOnDev :: #AgileIndia2019 Performance Time Forming Storming Norming Performing Storming Norming Storming Norming Norming Storming ? Tuckman’s?

18. @DocOnDev :: #AgileIndia2019 ActivityOccurrence Time Forming Performing Storming Norming Tuckman’s (For real)

19. @DocOnDev :: #AgileIndia2019 The problem wasn’t Because Tuckman’s

20. @DocOnDev :: #AgileIndia2019 BUT  Stable teams did make things better.

21. @DocOnDev :: #AgileIndia2019 So, if the problem wasn’t  Because Tuckman’s?

22. @DocOnDev :: #AgileIndia2019 So, if the problem  wasn’t  Because Tuckman’s? What Was It?

23. @DocOnDev :: #AgileIndia2019 What if the problem was  Because Resources?

24. @DocOnDev :: #AgileIndia2019 Because Resources

25. @DocOnDev :: #AgileIndia2019 Because Resources

26. @DocOnDev :: #AgileIndia2019 Because Resources

27. @DocOnDev :: #AgileIndia2019 Because Resources

28. @DocOnDev :: #AgileIndia2019 Because Resources

29. @DocOnDev :: #AgileIndia2019 Because Resources

30. @DocOnDev :: #AgileIndia2019 Because Resources

31. @DocOnDev :: #AgileIndia2019 Because Resources

32. @DocOnDev :: #AgileIndia2019 Tasks of 8 hours each 8 hours 16 hours 24 hours 32 hours Start All at Once Because Resources

33. @DocOnDev :: #AgileIndia2019 Start All at Once 8 hours 16 hours 24 hours 32 hours 40 hours 48 hours8 hours 16 hours 24 hours 32 hours Because Resources

34. @DocOnDev :: #AgileIndia2019 8 hours 16 hours 24 hours 32 hours Finish One at a Time Start All at Once 8 hours 16 hours 24 hours 32 hours 40 hours 48 hours Because Resources

35. @DocOnDev :: #AgileIndia2019 8Hoursofworkcompletedin… 0 3.5 7 10.5 14 Active Project Count 1 2 3 4 5 8 9.6 10.88 12.19 13.62 Because Resources 8 hours 16 hours 24 hours 32 hours 40 hours 48 hours

36. @DocOnDev :: #AgileIndia2019 Because Resources

37. @DocOnDev :: #AgileIndia2019 TaskTime Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Because Resources

38. @DocOnDev :: #AgileIndia2019 Because Resources 8Hoursofworkcompletedin… 0 40 80 120 160 Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 1 # of Projects

39. @DocOnDev :: #AgileIndia2019 Because Resources 8Hoursofworkcompletedin… 0 40 80 120 160 Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 1 2 # of Projects

40. @DocOnDev :: #AgileIndia2019 8Hoursofworkcompletedin… 0 40 80 120 160 Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 1 2 3 Because Resources # of Projects

41. @DocOnDev :: #AgileIndia2019 8Hoursofworkcompletedin… 0 40 80 120 160 Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 1 2 3 4 Because Resources # of Projects

42. @DocOnDev :: #AgileIndia2019 8Hoursofworkcompletedin… 0 40 80 120 160 Allocation 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 1 2 3 4 5 Because Resources # of Projects

43. @DocOnDev :: #AgileIndia2019 Stable Teams  Solved  Because Resources

44. @DocOnDev :: #AgileIndia2019 But…

45. @DocOnDev :: #AgileIndia2019 But…

46. @DocOnDev :: #AgileIndia2019 And Then…

47. @DocOnDev :: #AgileIndia2019 “…different areas of code are going to need different skill-sets at different times, and for that reason we need [people] to go and work on those particular areas at different times… None of this is basically static. It’s very fluid. And if you have the ability to reteam, then you are able to go do this sort of thing consistently.” – Michael Feathers

48. @DocOnDev :: #AgileIndia2019 “… None of this is basically static. It’s very fluid. And if you have the ability to reteam, then you are able to go do this sort of thing consistently.” – Michael Feathers

49. @DocOnDev :: #AgileIndia2019 reteam starters

50. @DocOnDev :: #AgileIndia2019 Connection Diversity Excellence Autonomy Four Factors lead to better team performance and c o l l e c t i v e satisfaction… reteam starters

51. @DocOnDev :: #AgileIndia2019 reteam examples

52. @DocOnDev :: #AgileIndia2019 reteam examples Cabals at Valve

53. @DocOnDev :: #AgileIndia2019 reteam examples “Spotify Model”

54. @DocOnDev :: #AgileIndia2019 reteam patterns

55. @DocOnDev :: #AgileIndia2019 reteam patterns Socialization

56. @DocOnDev :: #AgileIndia2019 reteam patterns Mitosis

57. @DocOnDev :: #AgileIndia2019 reteam patterns Volunteer Fire Department

58. @DocOnDev :: #AgileIndia2019 reteam patterns Trading Places

59. @DocOnDev :: #AgileIndia2019 “Reteaming is inevitable. You might as well get good at it.” - Nayan Hajratwala

60. @DocOnDev :: #AgileIndia2019 Tuckman Was Wrong! Thank You!