Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

If you need to run a project you've already failed

635 views

Published on

By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.

This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.

This presentation will introduce you to #noprojects. You will learn how to define an outcome and create an Outcome Profile. You will also learn how to manage change within the context of an outcome through the Activity Canvas.

Published in: Software
  • Be the first to comment

If you need to run a project you've already failed

  1. 1. @eleybourn @eleybourn If you need to run a project – you’ve already failed #noprojects Evan Leybourn Agile India 2016
  2. 2. @DipeshPala @eleybourn Come with an open mind This is a controversial topic
  3. 3. @eleybourn PART ONE Understanding projects
  4. 4. @DipeshPala @eleybourn What exactly is a project? A temporary structure to govern and deliver a complex change (such as a new product)
  5. 5. @DipeshPala @eleybourn Projects are expensive The three O’s of project cost; 1. Overheads, 2. Overruns and 3. Opportunity costs
  6. 6. @DipeshPala @eleybourn Projects fail The definition of insanity is to “do the same thing and expect a different result”
  7. 7. @DipeshPala @eleybourn Projects focus on the wrong thing What is measurable not what is valuable
  8. 8. @DipeshPala @eleybourn Projects are temporary (products aren’t) Products don’t end when the project does – don’t artificially constrain them & lose key skills
  9. 9. @DipeshPala @eleybourn
  10. 10. @eleybourn PART TWO introducing #noprojects
  11. 11. @DipeshPala @eleybourn Continuous change is the alternative! The approach and structure to successfully deliver continuous change without a project
  12. 12. @DipeshPala @eleybourn What is #noprojects? The alignment of activities to outcomes measured by value, constrained by guiding principles and supported by continuous delivery technologies
  13. 13. @eleybourn The continuous culture Continuous delivery, deployment, monitoring, strategy, planning, design, marketing,
  14. 14. @eleybourn PART THREE Where to begin
  15. 15. @DipeshPala @eleybourn Outcomes over outputs Outcomes are valuable, planned, slowly changing and define a common direction for all work
  16. 16. @DipeshPala @eleybourn
  17. 17. @DipeshPala @eleybourn Working principles Common, agreed, and prioritised constraints that shape all activities (e.g. quality, communication, staff engagement, security, or branding)
  18. 18. @DipeshPala @eleybourn Understanding the value of work Value degrades
  19. 19. @DipeshPala @eleybourn Understanding the value of work High value activities may come later
  20. 20. @DipeshPala @eleybourn Understanding the value of work Local Maxima
  21. 21. @DipeshPala @eleybourn Understanding the value of work The “So What” Factor
  22. 22. @DipeshPala @eleybourn Value delivery teams Dedicated cross-functional teams that contain the required skills to deliver an outcome (e.g. developers, testers, HR, accountants, sales/marketing)
  23. 23. @eleybourn PART FOUR Delivering work
  24. 24. @DipeshPala @eleybourn The activity canvas An activity is any discrete work that is undertaken as part of a change
  25. 25. @DipeshPala @eleybourn
  26. 26. @DipeshPala @eleybourn
  27. 27. @DipeshPala @eleybourn
  28. 28. @DipeshPala @eleybourn The technology of #noprojects Automated testing, continuous integration, continuous delivery, and DevOps
  29. 29. @DipeshPala @eleybourn Funding #noprojects Change the question – not “how much will this cost?”, but rather “how much is it worth?”
  30. 30. @eleybourn Evan Leybourn IBM GBS leybourn@sg.ibm.com @eleybourn slideshare.net/eleybourn sg.linkedin.com/in/evanleybourn

×