3. The Agile Manifesto
0 Individuals and interactions over processes and tools
0 Working software over comprehensive
documentation
0 Customer collaboration over contract negotiation
0 Responding to change over following a plan
4. Agile consensus
0 Works well in teams of 5 to 7
0 There is a minimum and maximum velocity
(throughput) required
0 Resources are constant
0 Timelines are constant
0 Scope is NOT constant
0 What is started is finished … sprint content is not
changed in flight, resources are not re-assigned to
other tasks
0 Is this us?
5. Reflection
0 Ideal for product teams
0 Ideal for in-house development teams
0 NOT suitable for fixed price delivery on fixed scope
7. Pros & Cons
0 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 + $
9. Pros & Cons
0 Long pre-sales
0 Can be mitigated somewhat by structuring
Requirements then delivery
0 Milestone based payment
0 Can be mitigated somewhat by % billing to milestone
0 Death by Change Reuqests
0 Is this not what we’re doing in Agile?
0 Change in scope has consequence in scope and cost
10. How do we prevent
FREEFALL!
How do we truly remain Agile?
11. Do we have to pick a
methodology?
0 No
0 What do we do then?
0 Pick the best of all – as it applies to our situation
0 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
12. 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
13. What do we measure
0 More achieved than planned is not necessarily all rosy
0 We may have spent more than planned to achieve that
0 More time spent than planned is not necessarily bad
0 We may have achieved more for that time
14. Are PMs forever going to be
number crunching?
0 PMs #1 job – plan
0 PMs #2 job – monitor and control
0 So why should we be afraid of that?
15. Are Management forever
going to read reports?
0 No
0 Use dashboards
0 If health is good, nothing
needs doing
0 If ailing, then management
applies appropriate remedy -
early
16. Will this ensure all projects
succeed?
0 Not necessarily
0 It will depend at how good we are at monitoring and
controlling
0 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
