Agile Mëtteg - Jan. 2011

2,043 views

Published on

Agile Enterprise
27 January 2011

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,043
On SlideShare
0
From Embeds
0
Number of Embeds
81
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile Mëtteg - Jan. 2011

  1. 1. AGILE ENTERPRISE<br />Agile Mëtteg – January 27th, 2011<br />
  2. 2. ABOUT US<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />2<br />
  3. 3. AGILE PARTNER SERVICES<br />IS Methods Services<br />Custom Software Development & Maintenance & Biz Solutions<br />Our core business to answer customer needs<br />IS Dev services<br />Thanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…)<br />IS Users Services<br />We can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…)<br />IS methods services<br />We can support Methods and Methodologies owners to implement agile approach within the methodologies portfolio (Assessment, Coaching, Support, Training, Resource delegation…)<br />1<br />4<br />Software Development & SoftwareMaintenance&Biz Solutions<br />2<br />IS UsersServices<br />IS Dev Services<br />Agility<br />Agility<br />2<br />3<br />1<br />Agility<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />3<br />3<br />4<br />
  4. 4. SPEAKERS<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />4<br />Agile Practitioners<br />Scrum, Lean/Kanban<br />
  5. 5. Current paradigm of an ENTERPRISE<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />5<br />
  6. 6. THE BIG PICTURE<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />6<br />Customers<br />Business leaders<br />Product managers<br />Business Operations<br />Management<br />Support<br />IT Operations<br />Development<br />
  7. 7. BECOMING AN AGILE ENTERPRISE<br />Paradigm optimization<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />7<br />
  8. 8. THE ENTERPRISE<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />8<br />Project mgt<br />Strategic<br />Software<br />Project<br />Project<br />Process & operations<br />Process & operations<br />Strategic<br />IT<br />Method& Process<br />Biz<br />Key Users<br />Dev. team<br />Strategic<br />Project<br />Strategic<br />
  9. 9. THE BIG PICTURE<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />9<br />Customers<br />Business leaders<br />Product managers<br />Optimize the whole!<br />Business Operations<br />Management<br />Support<br />IT Operations<br />Development<br />
  10. 10. LEAN SOFTWARE DEVELOPMENT<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />10<br />Process<br />Project<br />Team<br />
  11. 11. AGILE & LEAN VALUES<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />11<br />
  12. 12. 4 VALUES<br />Extract from Manifesto for Agile Software Development<br />[…] We have come to value:<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Customer collaboration over contract negotiation<br />Responding to change over following a plan<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />12<br />Source: http://www.agilemanifesto.org/<br />
  13. 13. LEAN PRINCIPLES<br />Eliminate Waste<br />Create Knowledge<br />Build Quality In <br />Defer Commitment<br />Deliver Fast<br />Respect People <br />Improve the entire System<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />13<br /><ul><li>Partially done work
  14. 14. Extra features
  15. 15. Relearning
  16. 16. Handoffs
  17. 17. Tasks switching
  18. 18. Delays
  19. 19. Defects</li></li></ul><li>RESPONSIBILITIES<br />Focus on Value, Speed and Quality<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />14<br />
  20. 20. BENEFITS<br />Scaling agile at the entreprise level<br />Beyond local optimization and narrow focus on project / team / software<br />Create a sustainable and appropriate environment for agile development<br />« Fast – Flexible – Flow »<br />Optimized value for the Enterprise<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />15<br />
  21. 21. About you<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />16<br />
  22. 22. PARTICIPANTS<br />Who are you?<br />What is your role?<br />What do you know about agility?<br />What about your enterprise?<br />27 January 2010<br />17<br />Agile Mëtteg – Agile Enterprise<br />
  23. 23. THE CORE BELIEFS OF AGILE<br /><ul><li>You cannot know everything required to build a software product at the start of the project.
  24. 24. Customers cannot accurately tell you what they want at the start of the project; instead, they will gain clarity as the project proceeds.
  25. 25. You want feedback from the customer as often as possible and you want to give developers feedback on how they are doing as soon as possible.
  26. 26. Working code is the most accurate way of seeing the progress of the development effort.
  27. 27. Groups working together minimizes delays as well as the loss of information between people.
  28. 28. Moving test to the front of the development cycle improves the conversation between developers and customers and testers and, thus, improves the quality of the code.
  29. 29. While management can set expectations for what work is done, management must not demand how that work is done.
  30. 30. Working on one project at a time improves the productivity of a team.</li></ul>27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />18<br />From your experience, what is true?<br />
  31. 31. THE CORE BELIEFS OF LEAN<br /><ul><li>Most errors are due to the system within which people work rather than to the individuals themselves.
  32. 32. People doing the work are the best ones to understand how to improve the system.
  33. 33. Ad hoc in not an acceptable process.
  34. 34. Looking at when things are done in a process is a more useful guide than trying to make sure every step of the way is as efficient as possible.
  35. 35. Our measure for success must be related to the amount of time between when ideas come in and when they are manifested as value to our customers.
  36. 36. Management must work with the team to improve the way it works to improve its own efficiency.
  37. 37. Teams are most efficient when the amount of work is limited to their capacity.
  38. 38. Team efficiency improves by minimizing the amount of work in progress at any one time.
  39. 39. When evaluating actions, we must optimize the whole, not merely improve individual steps in the process.
  40. 40. There are principles in software development that must be followed in order to reduce waste.</li></ul>27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />19<br />From your experience, what is true?<br />
  41. 41. Wrap-up<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />20<br />
  42. 42. NEXT SESSIONS<br />The next sessions will cover all 3 areas<br />Business<br />Requirements, Portfolio Management…<br />Management<br />Kanban, Communication, Estimation…<br />Delivery<br />Clean code, modeling, TDD…<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />21<br />
  43. 43. RESSOURCES <br />Agile Partner: www.agilepartner.net<br />NEW!blog.agilepartner.net<br />Agile Interest Group Luxembourg:www.aiglu.org<br />Recommended readings<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />22<br />
  44. 44. NEXT TRAININGS & CERTIFICATIONS<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />23<br />Complete calendar on: http://www.agilepartner.net/training/focus-on/<br />
  45. 45. CONTACTS<br />Thank You<br />27 January 2010<br />Agile Mëtteg – Agile Enterprise<br />24<br />

×