Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network

Share

Agile project management

on

  • 1,931 views

Presentation done during the European Master in Project Management.

Presentation done during the European Master in Project Management.
23rd of October 2010

Statistics

Views

Total Views
1,931
Views on SlideShare
1,454
Embed Views
477

Actions

Likes
2
Downloads
33
Comments
0

3 Embeds 477

http://www.iatriple.net 469
http://www.brijj.com 5
http://www.linkedin.com 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile project management Presentation Transcript

  • 1. Agile Project Management Andoni Gonzalo Bilbao, 23, October 2010 EURO MPM European Master In Proyect Management
  • 2. Agenda I. What is Agile II. A bit of History III. Why agile is used in SW EURO MPM European Master In Proyect Management 2
  • 3. What is Agile Close Concept Speculation Iterations Revision Exploration EURO MPM European Master In Proyect Management 3
  • 4. What is Agile • Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan EURO MPM European Master In Proyect Management 4
  • 5. What is Agile Persons and V Interaction A L U E Tools and Processes EURO MPM European Master In Proyect Management 5
  • 6. What is Agile Working SW V A L U E Comprehensive documentation EURO MPM European Master In Proyect Management 6
  • 7. What is Agile Customer V collaboration A L U E Contract negotiation EURO MPM European Master In Proyect Management 7
  • 8. What is Agile Responding to V change A L U E Following a plan EURO MPM European Master In Proyect Management 8
  • 9. What is Agile • Agile = iterate • Agile = increment • Agile = collaboration with the client • Agile = team player • Agile = share responsibility • Agile = Accept/Want change EURO MPM European Master In Proyect Management 9
  • 10. History • Many years ago • Not just in SW • Japan 1986 • The New New Product Developement Game, by Hirotaka Takeuchi (Hitotsubashi University) y Ikujiro Nonaka • Jeff Sutherland, John Scumniotales y Jeff McKenna • First Scrum for SW agile development on 1993 • Use the Takeuchi y Nonaka study about teams as base. • 1995 Ken Schwaber formalized the process for the SW industry. • 2001 Agile Manifesto • 12 gurus (http://www.agilemanifesto.org) EURO MPM European Master In Proyect Management 10
  • 11. Why being Agile in SW • Traditional methods DON’T WORK!!!! the-curious-case-of-the-chaos-report-2009 EURO MPM European Master In Proyect Management 11
  • 12. Why being Agile in SW • Averages Not on time  79% EURO MPM European Master In Proyect Management 12
  • 13. Why being Agile in SW • New Agile methodologies EURO MPM European Master In Proyect Management 13
  • 14. Why being Agile in SW • Clients don’t know what they want • Changes come after every meeting • Can’t follow a real plan • “Most of the people don’t know what they want until they try it” • Selling blue elephants (Howard Moskowitz & Alex Gofman) • Agile Marketing RDE (Rule Development Experimentation) EURO MPM European Master In Proyect Management 14
  • 15. Why being Agile in SW • ROI JOHN GOODSEN EURO MPM European Master In Proyect Management 15
  • 16. Why being Agile in SW • Quality • Working output at the end of the increment • Short iterations • Easy to react to wrong decisions EURO MPM European Master In Proyect Management 16
  • 17. General problems • There isn’t a global model • Specific areas • Management not always committed • Difficult to implement in whole company • Think developers are translators • Can’t share responsibility • Clients refuse • Want clear objectives • Feels “chaos” will take over the project • Contract  Think it’s safer EURO MPM European Master In Proyect Management 17
  • 18. Methodologies Based on Processes P r a c t i c e M o d EFQM e l Specific Area Global EURO MPM European Master In Proyect Management 18
  • 19. Methodologies Based on Agile P r a c t i c e M o d e l Specific Area Global EURO MPM European Master In Proyect Management 19
  • 20. Tipos de Planificación Conclusions • Agile for SW development • Good Needed • Constant Planning • RE-planning • Other areas • Every creative work • Where change is constant • Uncertain environment EURO MPM European Master In Proyect Management 20
  • 21. Tipos de Planificación Q&A EURO MPM European Master In Proyect Management 21