Empirical Process                                            Control                                                      ...
Empirical vs. Definingagile42 | The Agile Coaching Company   www.agile42.com |   All rights reserved. Copyright © 2007 - 20...
“At the University of California at Irvine, ... they                                       just planted grass... they wait...
Defined Process Control                           Inspired by the assembly lineagile42 | We advise, train and coach compani...
Empirical Process Control                              Based on the the Scientific Methodagile42 | We advise, train and coa...
Scientific Method Steps:       • Ask a Question       • Do Background Research       • Construct a Hypothesis       • Test...
Software                                                           Development                                        Whic...
?                                                             Software                                                    ...
Which Metaphor?agile42 | We advise, train and coach companies building software   www.agile42.com |   All rights reserved....
Which Metaphor?agile42 | We advise, train and coach companies building software   www.agile42.com |   All rights reserved....
Process Control vs Complexity                                                                                            T...
Process Control vs Complexity                                                                                             ...
Process Control vs Complexity                                                     Empirical                               ...
Defined vs Empiricalagile42 | The Agile Coaching Company—“Coaching Good Teams to Great”   www.agile42.com |   All rights re...
Defined vs Empirical                  “How to maximize resource utilization and activity speed”agile42 | The Agile Coaching...
Defined vs Empirical                  “How to maximize resource utilization and activity speed”                            ...
Scientific Method vs Scrum         Ask a Question  • Do Background         Research  • Construct a Hypothesis  • Test Your ...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Scientific Method vs Scrum                                                                      • “They clearly need better...
Implications of Empiricalagile42 | The Agile Coaching Company—“Coaching Good Teams to Great”   www.agile42.com |   All rig...
Implications of Empirical • Learning is “hard cash”agile42 | The Agile Coaching Company—“Coaching Good Teams to Great”   w...
Implications of Empirical • Learning is “hard cash” • Speed is vital for learningagile42 | The Agile Coaching Company—“Coa...
Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environmentagile42 | Th...
Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must e...
Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must e...
Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must e...
Contact and information• geir.amsjo@agile42.com,• www.agile42.no• www.agile42.com• Blog: scrummaster.no• Twitter: @gamsjoa...
Upcoming SlideShare
Loading in …5
×

Empirical processcontrol

1,239 views

Published on

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,239
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
38
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • If you have to produce the same thing day in day out - an assembly line might work.\nThe different steps are highly specialized to do one thing extremely good.\nThen also the related processes might work for you.\n(In manufacturing almost nobody uses waterfall anymore)\n
  • Solving completely new problems requires exploration. A more or less strong hypothesis, then designing an experiment, then analysing the result to create an even stronger hypothesis.\n\nFinne ut så raskt som mulig om det er et problem som er verd å løse\n\n\n
  • \n
  • \n
  • Creating software is a creative exercise. It is about solving the problem ONCE. There is no production issue in IT. Like in Science we need to create good experiments to as quickly and efficient as possible learn wether our hypothesis is strong or not.\n\n
  • Simple\n Repeating patterns and consistent events\n Clear cause-and-effect\n Relationships evident to everyone;\n Right answer exists\n Fact-based management\nComplicated\n Expert diagnosis required\n Cause-and-effect relationships discoverable but not immediately apparent to everyone\n More than one right answer possible\n Known unknowns\n Fact-based management\nComplex\n Flux and unpredictability\n No right answers\n Emergent instructive patterns\n Unknown unknowns\n Many competing ideas\n A need for creative and innovative approaches\n Pattern-based leadership\nChaotic\n High turbulence\n No clear cause-and-effect relationships, so no point in looking for right answers\n Unknowables\n Many decisions to make and no time to think\n High tension\n Pattern-based leadership\nDisorder\nYou will have disorder when you don´t understand where you are.\n
  • Simple\n Repeating patterns and consistent events\n Clear cause-and-effect\n Relationships evident to everyone;\n Right answer exists\n Fact-based management\nComplicated\n Expert diagnosis required\n Cause-and-effect relationships discoverable but not immediately apparent to everyone\n More than one right answer possible\n Known unknowns\n Fact-based management\nComplex\n Flux and unpredictability\n No right answers\n Emergent instructive patterns\n Unknown unknowns\n Many competing ideas\n A need for creative and innovative approaches\n Pattern-based leadership\nChaotic\n High turbulence\n No clear cause-and-effect relationships, so no point in looking for right answers\n Unknowables\n Many decisions to make and no time to think\n High tension\n Pattern-based leadership\nDisorder\nYou will have disorder when you don´t understand where you are.\n
  • Teamet har begrenset frihet (selvsagt) slik at inkrementene fører til et helhetlig produkt.\n\n\n
  • Teamet har begrenset frihet (selvsagt) slik at inkrementene fører til et helhetlig produkt.\n\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Empirical processcontrol

    1. 1. Empirical Process Control by Geir Amsjøagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2011.
    2. 2. Empirical vs. Definingagile42 | The Agile Coaching Company www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    3. 3. “At the University of California at Irvine, ... they just planted grass... they waited a year andEmpirical vs. Defining looked at where people had made paths in the grass and built the side walks there.”agile42 | The Agile Coaching Company www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    4. 4. Defined Process Control Inspired by the assembly lineagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    5. 5. Empirical Process Control Based on the the Scientific Methodagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    6. 6. Scientific Method Steps: • Ask a Question • Do Background Research • Construct a Hypothesis • Test Your Hypothesis by Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Results Scientific Methodagile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    7. 7. Software Development Which Metaphor?agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    8. 8. ? Software Development Which Metaphor?agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    9. 9. Which Metaphor?agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    10. 10. Which Metaphor?agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2010.
    11. 11. Process Control vs Complexity The Cynefin Framework From “A Leader’s Framework for Decision Making” by D. Snowden & M. Boone in Harvard Business Review, NOV 2007.agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    12. 12. Process Control vs Complexity The Cynefin Framework Defined Process Control From “A Leader’s Framework for Decision Making” by D. Snowden & M. Boone in Harvard Business Review, NOV 2007.agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    13. 13. Process Control vs Complexity Empirical Process Control The Cynefin Framework Defined Process Control From “A Leader’s Framework for Decision Making” by D. Snowden & M. Boone in Harvard Business Review, NOV 2007.agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    14. 14. Defined vs Empiricalagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    15. 15. Defined vs Empirical “How to maximize resource utilization and activity speed”agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    16. 16. Defined vs Empirical “How to maximize resource utilization and activity speed” “How to maximize learning and innovation”agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    17. 17. Scientific Method vs Scrum Ask a Question • Do Background Research • Construct a Hypothesis • Test Your Hypothesis by Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    18. 18. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background Research • Construct a Hypothesis • Test Your Hypothesis by Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    19. 19. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background • Do some investigation in that area Research • Construct a Hypothesis • Test Your Hypothesis by Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    20. 20. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background • Do some investigation in that area Research • Define User Stories for this. Estimate • Construct a Hypothesis and prioritize (MMF, MVP). • Test Your Hypothesis by Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    21. 21. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background • Do some investigation in that area Research • Define User Stories for this. Estimate • Construct a Hypothesis and prioritize (MMF, MVP). • Test Your Hypothesis by • Run Sprint Doing an Experiment • Analyze Your Data and Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    22. 22. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background • Do some investigation in that area Research • Define User Stories for this. Estimate • Construct a Hypothesis and prioritize (MMF, MVP). • Test Your Hypothesis by • Run Sprint Doing an Experiment • Do Sprint review. Deliver the • Analyze Your Data and increment (?) Draw a Conclusion • Communicate Your Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    23. 23. Scientific Method vs Scrum • “They clearly need better browsing Ask a Question capabilities. What if we provided Geographical Browsing?” • Do Background • Do some investigation in that area Research • Define User Stories for this. Estimate • Construct a Hypothesis and prioritize (MMF, MVP). • Test Your Hypothesis by • Run Sprint Doing an Experiment • Do Sprint review. Deliver the • Analyze Your Data and increment (?) Draw a Conclusion • Have retrospective, update Product • Communicate Your Backlog (learning) Resultsagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    24. 24. Implications of Empiricalagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    25. 25. Implications of Empirical • Learning is “hard cash”agile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    26. 26. Implications of Empirical • Learning is “hard cash” • Speed is vital for learningagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    27. 27. Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environmentagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    28. 28. Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must expect to failagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    29. 29. Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must expect to fail • Team self-organize and find the best possible way to perform the workagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    30. 30. Implications of Empirical • Learning is “hard cash” • Speed is vital for learning • A safe-to-fail environment • We must expect to fail • Team self-organize and find the best possible way to perform the work • The best “experiments” lead to both valuable product increments and learningagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.
    31. 31. Contact and information• geir.amsjo@agile42.com,• www.agile42.no• www.agile42.com• Blog: scrummaster.no• Twitter: @gamsjoagile42 | The Agile Coaching Company—“Coaching Good Teams to Great” www.agile42.com | All rights reserved. Copyright © 2007 - 2012.

    ×