Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

"Productivity" is Killing Us.

1 216 vues

Publié le

How busy-ness culture negatively impacts our ability to deliver value
by Adam Yuret, http://www.contextdrivenagility.com

What did you do yesterday?
What will you do today?
What’s getting in your way?
Three questions commonly asked at Daily Scrum meetings that imply that doing things is the purpose of work. Rarely have I encountered organizations where these following answers were acceptable:

Yesterday I read a book at work.
Today I intend to start no new work and make myself available to help others learn.
Being too busy is getting in my way and I need some slack.
The above may seem exaggerated but aren't; each one is an example of a behavior someone engaged in that helped deliver value to the customer. Slack, learning and play enhance our ability to deliver business and customer value.

Adam Yuret
Come join Adam Yuret to have a discussion about how a focus on resource efficiency impedes flow while creating mountains of failure demand and fracturing our organization into competing silos. Also learn some ideas about humanistic ways to mitigate these issues and bring flow back to our organizations.

Publié dans : Business
  • Login to see the comments

"Productivity" is Killing Us.

  1. 1. How Metrics and Utilization Constrict the Flow of Value. @AdamYuret Adam.Yuret@gmail.com
  2. 2. Husband, Dad, Humanistic Lean Flow-Based SystemsThinking Consultant at Context driven Agility (CDA) Consulting, Sailor @AdamYuret Adam.Yuret@gmail.com
  3. 3. @AdamYuret Adam.Yuret@gmail.com
  4. 4. @AdamYuret Adam.Yuret@gmail.com
  5. 5. @AdamYuret Adam.Yuret@gmail.com
  6. 6. @AdamYuret Adam.Yuret@gmail.com
  7. 7. Discuss how the relentless pursuit of productivity is constraining our ability to effectively deliver value to our customers and businesses. Discuss some alternatives to this approach of optimizing for busyness. @AdamYuret Adam.Yuret@gmail.com
  8. 8. @AdamYuret Adam.Yuret@gmail.com
  9. 9. @AdamYuret Waste Adam.Yuret@gmail.com
  10. 10. @AdamYuret Adam.Yuret@gmail.com
  11. 11. @AdamYuret Adam.Yuret@gmail.com
  12. 12. @AdamYuret Adam.Yuret@gmail.com
  13. 13. @AdamYuret Adam.Yuret@gmail.com
  14. 14. @AdamYuret Adam.Yuret@gmail.com
  15. 15.  Prescriptive: Follow these rules and Agile hyper- productivity will be your reward. @AdamYuret Adam.Yuret@gmail.com
  16. 16.  Castigate when the rules are not followed. @AdamYuret Adam.Yuret@gmail.com
  17. 17.  Take pride in following those rules. @AdamYuret Adam.Yuret@gmail.com
  18. 18.  Measure success based on compliance to the rules. @AdamYuret Adam.Yuret@gmail.com
  19. 19.  Blame failure on lack of strict adherence to the rules. @AdamYuret Adam.Yuret@gmail.com
  20. 20. @AdamYuret Adam.Yuret@gmail.com
  21. 21. @AdamYuret Adam.Yuret@gmail.com
  22. 22. @AdamYuret Adam.Yuret@gmail.com
  23. 23.  What did you do yesterday?  What will you do today?  Any impediments? @AdamYuret Adam.Yuret@gmail.com
  24. 24. @AdamYuret Adam.Yuret@gmail.com
  25. 25. @AdamYuret Adam.Yuret@gmail.com
  26. 26. @AdamYuret Adam.Yuret@gmail.com
  27. 27. Excessive Work in Progress (WIP) is the enemy of flow. By setting limits to work in progress we can enable greater flow. @AdamYuret Adam.Yuret@gmail.com
  28. 28. @AdamYuret Adam.Yuret@gmail.com
  29. 29. @AdamYuret Adam.Yuret@gmail.com
  30. 30. Traditional management thinking treats all demand as equal. There is work to be done and people who do the work. Failure Demand is demand that originates from a failure to have done something right in the first place. Not all productivity is desirable. @AdamYuret Adam.Yuret@gmail.com
  31. 31. @AdamYuret Adam.Yuret@gmail.com
  32. 32. Agile team produces growing velocity but, as they speed features out the door, bugs are introduced. When bugs come into the backlog they’re assigned velocity points. It is theoretically possible, therefore, to have a team producing zero value demand while increasing velocity fixing bugs. @AdamYuret Adam.Yuret@gmail.com
  33. 33. @AdamYuret Adam.Yuret@gmail.com
  34. 34. @AdamYuret Adam.Yuret@gmail.com
  35. 35.  In order to keep developers typing at maximum utilization, we create teams to absorb the failure demand caused by developers typing at maximum utilization. These teams often have unlimited WIP and must consume an unending stream of demand. This also hides the problems from the people creating them. @AdamYuret Adam.Yuret@gmail.com
  36. 36. @AdamYuret Adam.Yuret@gmail.com
  37. 37. @AdamYuret Adam.Yuret@gmail.com
  38. 38. @AdamYuret Adam.Yuret@gmail.com
  39. 39. @AdamYuret Adam.Yuret@gmail.com
  40. 40. @AdamYuret Adam.Yuret@gmail.com
  41. 41. @AdamYuret Adam.Yuret@gmail.com
  42. 42. @AdamYuret Adam.Yuret@gmail.com
  43. 43. @AdamYuret Adam.Yuret@gmail.com
  44. 44. @AdamYuret Adam.Yuret@gmail.com
  45. 45. @AdamYuret Adam.Yuret@gmail.com
  46. 46. @AdamYuret Adam.Yuret@gmail.com
  47. 47. @AdamYuret Adam.Yuret@gmail.com
  48. 48.  Variability Buffer  Learning  Innovation @AdamYuret Adam.Yuret@gmail.com
  49. 49. @AdamYuret Adam.Yuret@gmail.com
  50. 50. Flow Trumps Waste Value Trumps Flow @AdamYuret Adam.Yuret@gmail.com
  51. 51. Flow Trumps Waste @AdamYuret Adam.Yuret@gmail.com
  52. 52. Value Trumps Flow @AdamYuret Adam.Yuret@gmail.com
  53. 53. In general, reliability is the ability of a person or system to perform and maintain its functions in routine circumstances as well as in hostile or unexpected circumstances. In the case of emergency services, reliability looks at actual incident history data to measure historical performance in accordance with adopted performance measures. A unit unavailable for response provides no service to the community. The unit may be out of service for a multitude of reasons including; another emergency response, training, maintenance, etc. If a unit is not available 80% of the time, it is not reasonable to expect the unit to perform at the 80th percentile. …. Poor availability negatively influences response times. @AdamYuret Adam.Yuret@gmail.com
  54. 54. @AdamYuret Adam.Yuret@gmail.com
  55. 55. @AdamYuret Adam.Yuret@gmail.com
  56. 56. @AdamYuret Adam.Yuret@gmail.com
  57. 57. @AdamYuret Adam.Yuret@gmail.com
  58. 58. @AdamYuret Adam.Yuret@gmail.com
  59. 59. @AdamYuret Adam.Yuret@gmail.com
  60. 60.  Failure Demand  Silos:“Dumpster Teams”  Overloaded Bottlenecks  Deadline-Driven Development  Exponential Delays @AdamYuret Adam.Yuret@gmail.com
  61. 61. @AdamYuret Adam.Yuret@gmail.com
  62. 62. @AdamYuret Adam.Yuret@gmail.com
  63. 63. @AdamYuret Adam.Yuret@gmail.com
  64. 64. “Limiting our work in progress so we focused on completion was a big deal for us. It felt better to have 1 story than 5 tasks in progress.” –Lead Developer “Development was very helpful with testing, volunteering to clear impediments and helping us test during the sprint.” –Lead Tester “The team is excited and helping each other out during stand-up and working together in the War Room” –PM/SM @AdamYuret Adam.Yuret@gmail.com
  65. 65. @AdamYuret Adam.Yuret@gmail.com
  66. 66. @AdamYuret Adam.Yuret@gmail.com
  67. 67. @AdamYuret Adam.Yuret@gmail.com
  68. 68. @AdamYuret Sayat.me/ayuret Adam.Yuret@gmail.com