Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Unleashing Innovation and Productivity Through Extreme Time Constraints aka "Shrink That Project!" Pascal PinckTwitter: @pascalpinck Web: Used with permission
  2. 2. How long do your projects take?Hours? Days? Weeks? Months? Years?
  3. 3. Long projects have real benefits • Time to "get things right" • Time to do foundational research • Allows us to tackle large chunks of work • Allows us to build up momentum • Provides personal/team clarity → reduces "existential overhead"
  4. 4. Long projects also have big drawbacks • Integration risks • Market risks • Compounding delay costs • Parkinsons Law*: "Work expands so as to fill the time available for its completion."*Cyril Northcote Parkinson, 1909-1993, British naval historian
  5. 5. What is a project anyway?
  6. 6. In its most abstracted form, a project is…An interlinked series of discoveries, decisions, & actionsmade in support of an explicit, unifying objectivein a context of limited resources, evolving capabilities, & changing stakeholder needs.
  7. 7. Can this be done in very short cycles?Yes. Some examples:
  8. 8. "Scrum"for SoftwareDevelopment
  9. 9. Lets revisit our definition. A project is…An interlinked series of discoveries, (= learning/understanding) decisions, (= selecting/prioritizing/negotiating) & actions (= creating/executing/delivering)made in support of an explicit, unifying objectivein a context of limited resources, evolving capabilities, & changing stakeholder needs.
  10. 10. What is a minimum viable project?
  11. 11. A minimum viable project:Includes some 1. selecting of available goals, resources, and strategic constraints 2. prioritizing, especially which tasks to OMIT 3. negotiating, especially tradeoffsAnd results in some 1. shared learning about the market, especially end users 2. shared learning about the problem/solution space 3. creation of value based on this shared learning 4. delivery of value to stakeholders 5. shared learning about ourselves and our way of working
  12. 12. What is NOT (necessarily) required • Formal planning • Explicit mitigation of all (or most) risks • Heavyweight (or even pre-defined) processes • Expectation of a particular outcome • A formal leadership structure • Documentation
  13. 13. The real magic:Its all about "less"
  14. 14. Less is good!Less work • Less work-in-progress • Less task switching • Less induced work • Less low-priority work • Less work that gets thrown away • Less procrastination (= work avoiding work)
  15. 15. Less is good!Less debt • Less social debt ("conversations not had") • Less tradespace debt ("tradeoffs not made") • Less prioritization debt ("nice-to-haves not let go of") • Less bad news debt ("nasty messes not uncovered")
  16. 16. Extreme time constraints are an engine for innovation
  17. 17. An engine for innovationHistory shows that high-pressure, time-constrainedenvironments are extremely hospitable to breakthroughinnovation.
  18. 18. An engine for innovationExtreme time constraints • Snap people out of regular routines • Call forth intense attention and engagement • Make bureaucratic processes irrelevant • Promote transparency and disclosure • Raise the bar on team performance • Force stakeholders into proximity • Encourage swarming • Encourage the simplest possible solution
  19. 19. An innovation equation Shared purpose+ laser focus+ authentic urgency+ rapid feedback+ social/organizational safety= INNOVATION MULTIPLIER EFFECT
  20. 20. "So whats the bad news?"
  21. 21. Drawbacks/downsidesThis type of project… • Is cognitively, physically, and emotionally intense • Can expose significant organizational weaknesses • Can expose a lack of shared goals/vision • Can expose poor relationships in the organization • Can cause "iteration fatigue" • Can disrupt flow in some cases • Can be hard to scale
  22. 22. What about estimating & budgeting?
  23. 23. Estimating & budgetingFor short or iterative projects…"Do as little estimating as possible."Why? • Were almost always wrong. • It tends to divert time and energy from delivering actual value. • It delays our contact with the market • It defers key discoveries, especially the most unpleasant (and expensive) ones.
  24. 24. Instead… try "Scope Flex" • Timebox is fixed. • Resources are fixed. • Team does as much as they can in the time allotted with the resources they have.
  25. 25. Instead… try "Scope Flex"Three caveats 1. Team must work on things in the order of big-picture importance (e.g., stakeholder value and/or risk). 2. Team commits to completing something of true stakeholder value by the deadline. 3. While the team gets to decide the specifics of what gets delivered, they do so in an ongoing dialog with the key stakeholders.
  26. 26. Key success factors • Frequent interaction with customer/market or proxy • Leaders who model transparency and disclosure • High-bandwidth communication • Tolerance for ambiguity • Willingness to learn iteratively • Openness to failure • Social/organizational safety • Ideally, a small team (< 20) • Shared cadence/rituals • Co-location helps
  27. 27. Suggested reading
  28. 28. Questions/DiscussionTwitter: @pascalpinck Web:
  29. 29. Image creditsImages used under creative commons licensep2 – tomato see – baker statue see – sad face see – question mark see – scrum board see – code screenshot see – warning lamps see – control room see – news set see – football see – reams of paper see – spoons see – credit cards see – stopwatch see – bees see – warning sign see
  30. 30. Image creditsImages used under creative commons license (contd)p29/30 – arching back see – running track see images – in wide releasep9 – Humble/Farley and Duvall books: Addison-Wesleyp13 – Kinect device: Microsoftp13 – 3d visualization: adafruit.comp22 – all images: NASAp32 – Poppendieck and Highsmith books: Addison-Wesleyp32 – Pascale book: Crown Businessp32 – Anderson book: Blue Hole PressOther image creditsp8 – scrum diagram: Mike Cohn / Mountain Goat Software. Used by permission.p11 – all images: BrainStore Ltd. Used by permission.