Two cases how Agile project management can be used for fixed contract projects.
Presentation for: Baltic Project Management Days 2014 conference: http://pmdays.eu
Vaidas Adomauskas
www.agilecoach.lt
18. "Managing the Development of Large Software Systems“
Royce Winston (1970), Proceedings of IEEE WESCON 26 (August): 1–9.
19. "Managing the Development of Large Software Systems“
Royce Winston (1970), Proceedings of IEEE WESCON 26 (August): 1–9.
I believe in this concept, but the implementation
described above is
risky and invites failure.
29. Agile project plan (Product Backlog)
• Project is executed feature by
feature (size):
– Feature 1 (20)
– Feature 2 (40)
– Feature 3 (20)
– Feature 4 (40)
– Feature 5 (20)
– Feature 6 (40)
• TOTAL (180)
• Early signs if we estimation was
right:
– Feature 1 (20) – finished in
30
– Feature 2 (40)
– Feature 3 (20)
– Feature 4 (40)
– Feature 5 (20)
– Feature 6 (40)
• TOTAL (180) – is it really 180?
• Feature priorities can be changed:
– Feature 1 (20)
– Feature 2 (40)
– Feature 5 (20) – important
– Feature 3 (20)
– Feature 4 (40)
– Feature 6 (40)
• TOTAL (180)
• Features can be exchanged
(with the same size):
– Feature 1 (20)
– Feature 2 (40)
– Feature 3 (20)
– Feature 7 (40) – new
– Feature 4 (20)
– Feature 5 (40)
• TOTAL (180)
30. Different assumptions
Traditional
Client knows what he
wants
Creators know how to
create
Nothing will change
Agile
Client will figure out what
he wants
Creators will find out how
to create
There will be changes
41. Agile works in projects? In outsourced ones?
Outsourcing exec urges: ‘Stop outsourcing
your software development’
Unless you absolutely have to. And
unless you do it with Agile. More
specifically, Scrum.
http://www.zdnet.com/outsourcing-exec-urges-stop-outsourcing-your-
software-development-7000004315/?s_cid=e539