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.

Managing Projects Better


Published on

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

  • Be the first to like this

Managing Projects Better

  1. 1. AgileAre we agile or is it simply another name for chaos?
  2. 2. The Agile Manifesto0 Individuals and interactions over processes and tools0 Working software over comprehensive documentation0 Customer collaboration over contract negotiation0 Responding to change over following a plan
  3. 3. Agile consensus0 Works well in teams of 5 to 70 There is a minimum and maximum velocity (throughput) required0 Resources are constant0 Timelines are constant0 Scope is NOT constant0 What is started is finished … sprint content is not changed in flight, resources are not re-assigned to other tasks0 Is this us?
  4. 4. Reflection0 Ideal for product teams0 Ideal for in-house development teams0 NOT suitable for fixed price delivery on fixed scope
  5. 5. PRINCE2Monitor and Control to given tolerances – scope, cost, timeline, risks, quality, benefits
  6. 6. Pros & Cons0 Does not prescribe a methodology for “specialist products” – i.e. development 0 Good – nothing stopping us Agile practices 0 Bad – Higher PM effort … is it bad?0 In PRINCE2 project we’re really playing a team role … is it worth the effor + $
  7. 7. WaterfallDo we really want to go back to bad old days?
  8. 8. Pros & Cons0 Long pre-sales 0 Can be mitigated somewhat by structuring Requirements then delivery0 Milestone based payment 0 Can be mitigated somewhat by % billing to milestone0 Death by Change Reuqests 0 Is this not what we’re doing in Agile? 0 Change in scope has consequence in scope and cost
  9. 9. How do we prevent FREEFALL! How do we truly remain Agile?
  10. 10. Do we have to pick a methodology?0 No0 What do we do then? 0 Pick the best of all – as it applies to our situation0 Does that not leave us to chaos then? 0 No 0 We must apply uniform reporting mechanism 0 We must review project health as a practice
  11. 11. What do we report?0 Earned Value 0 How much did we plan to complete by now? 0 How much have we completed? 0 Difference is schedule slippage or advance 0 How much time did we plan to spend by now? 0 How much time have we spent? 0 Difference is cost slippage or advance
  12. 12. What do we measure0 More achieved than planned is not necessarily all rosy 0 We may have spent more than planned to achieve that0 More time spent than planned is not necessarily bad 0 We may have achieved more for that time
  13. 13. Are PMs forever going to be number crunching?0 PMs #1 job – plan0 PMs #2 job – monitor and control0 So why should we be afraid of that?
  14. 14. Are Management forever going to read reports?0 No0 Use dashboards0 If health is good, nothing needs doing0 If ailing, then management applies appropriate remedy - early
  15. 15. Will this ensure all projects succeed?0 Not necessarily0 It will depend at how good we are at monitoring and controlling0 This method succeeded in IRIS 0 a project that was potentially going to be the biggest loss leader of all time 0 we brought it in time and within budget