Adopting Agile

1,100 views

Published on

3rd Agile Gathering (Kiiv)

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

  • Be the first to like this

No Downloads
Views
Total views
1,100
On SlideShare
0
From Embeds
0
Number of Embeds
33
Actions
Shares
0
Downloads
54
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Adopting Agile

  1. 1. Pragmatic agile adoption 3-rd Agile Gathering, Ukraine 2007 Askhat Urazbaev Agile Coach
  2. 2. Askhat Urazbaev http://urazbaev.ru <ul><li>Agile Coach </li></ul><ul><li>Quality Center, Luxoft </li></ul><ul><li>Certified Scrum Master </li></ul><ul><li>Member of ScrumAlliance </li></ul><ul><li>Founder of AgileRussia </li></ul><ul><li>http://agilerussia.ru </li></ul>
  3. 3. Today… <ul><li>What do we want? </li></ul><ul><li>Adopting agile </li></ul><ul><li>Selling agile </li></ul><ul><li>Planning practices (optional) </li></ul>
  4. 4. What do we want? <ul><li>Adopt agile in the project! </li></ul><ul><li>Meet the project goal effectively </li></ul>
  5. 5. Project Analysis <ul><li>The Goal </li></ul>Problems & Risks Environment
  6. 6. The goal <ul><li>The goal must be </li></ul><ul><ul><li>Related to business </li></ul></ul><ul><ul><li>Shared and communicated </li></ul></ul><ul><ul><li>Committed by everyone </li></ul></ul><ul><li>Earn $5mln </li></ul><ul><li>Get the market share 51% by the end of year </li></ul><ul><li>Get investment $5mln </li></ul>examples
  7. 7. (btw) Manager’s goals <ul><li>Product-driven manager </li></ul><ul><li>Project-driven manager </li></ul><ul><li>Demo-driven manager </li></ul><ul><li>Project goals are not (always) manager’s goals </li></ul>
  8. 8. Problems & Risks <ul><li>Problems and risks prevents us from meeting goal </li></ul><ul><li>Customer doesn’t know what </li></ul><ul><li>she wants </li></ul><ul><li>Requirements are changing all the time </li></ul><ul><li>Employees avoid responsibility </li></ul>examples
  9. 9. Problems <ul><li>Root problems </li></ul><ul><ul><li>Not enough </li></ul></ul><ul><ul><ul><li>Collaboration </li></ul></ul></ul><ul><ul><ul><li>Communication </li></ul></ul></ul><ul><ul><ul><li>Quality </li></ul></ul></ul><ul><li>Solution </li></ul><ul><ul><li>Agile principles </li></ul></ul>
  10. 10. Adopting principles <ul><li>Slogans don’t work </li></ul><ul><li>Rituals work </li></ul><ul><li>Agile practices are rituals </li></ul><ul><ul><li>(they work even if you don’t understand them) </li></ul></ul>Commitment Reflection Feedback
  11. 11. “ Big bang” adoption Effectiveness time
  12. 12. “ Baby steps” adoption Effectiveness time
  13. 13. Environment <ul><li>All about project environment and context </li></ul><ul><ul><li>Team structure </li></ul></ul><ul><ul><li>Team qualifications </li></ul></ul><ul><ul><li>Project type </li></ul></ul><ul><ul><li>Contract type </li></ul></ul><ul><ul><li>Technology </li></ul></ul><ul><ul><li>Organizational structure </li></ul></ul><ul><ul><li>Corporate culture </li></ul></ul><ul><ul><li>…………… </li></ul></ul>
  14. 14. Environmental issues <ul><li>Some environmental issues don’t allow to adopt practices </li></ul><ul><li>Distributed development </li></ul><ul><li>Uncommitted customer </li></ul><ul><li>Legacy code </li></ul><ul><li>Fixed Price Contract </li></ul>examples
  15. 15. Uncertain and changing environment <ul><li>Some issues only LOOKS like showstoppers </li></ul><ul><li>Some issues are undiscovered yet </li></ul><ul><li>Environment changes all the time </li></ul>
  16. 16. Adopting practice. Collaboration game <ul><li>Select </li></ul><ul><li>Commit </li></ul><ul><li>Try </li></ul><ul><li>Reflect </li></ul><ul><li>Modify </li></ul><ul><li>Agile is not religion :-) </li></ul>
  17. 17. There are a few questions left <ul><li>Which order do we adopt practices? </li></ul><ul><li>How do I “sell” it to people (customers, managers, team members etc)? </li></ul>
  18. 18. Which order do we adopt practices? <ul><li>It depends </li></ul><ul><li>But basically </li></ul><ul><ul><li>We improve communication with customer </li></ul></ul><ul><ul><ul><li>(PO, backlog, planning and demo sessions) </li></ul></ul></ul><ul><ul><li>We build team </li></ul></ul><ul><ul><ul><li>(daily scrum, planning poker, taskboards etc.) </li></ul></ul></ul><ul><li>Then </li></ul><ul><ul><li>We build quality </li></ul></ul><ul><ul><ul><li>(Unit Tests & TDD, Automated testing, etc.) </li></ul></ul></ul>
  19. 19. Agile Adoption Framework <ul><li>Looking for detailed guide? </li></ul><ul><ul><li>Agile Adoption Framework (A.Sidky) </li></ul></ul>
  20. 20. Selling Agile
  21. 21. Conversation (1) <ul><li>We need pair programming (and this is cool!) </li></ul><ul><li>No, we don’t (and you are geek) </li></ul>
  22. 22. Conversation (2) <ul><li>What’s our most important problem? </li></ul><ul><li>There’s not enough communication between people </li></ul><ul><li>Then we need pair programming! </li></ul><ul><li>We don’t have time for it </li></ul>
  23. 23. Conversation (3) <ul><li>Why it is a problem? </li></ul><ul><li>We can’t develop important pieces fast enough. This is critical for business! </li></ul><ul><li>Don’t you think pairing might help? </li></ul><ul><li>I’m not sure </li></ul><ul><li>We might try for 1 iteration and reflect at the end </li></ul><ul><li>Sounds like a plan! </li></ul>
  24. 24. Summary <ul><li>Agile for the sake of agile is wrong </li></ul><ul><li>Pay attention to the goal and real problems </li></ul><ul><li>Change is hard. Baby steps </li></ul><ul><li>Adopting practices. Try and reflect </li></ul><ul><li>Selling agile is a skill :-) </li></ul>
  25. 25. <ul><li>www.agilerussia.ru </li></ul><ul><li>Agile Community Russia - независимое некоммерческое сообщество, объединяющее ИТ-профессионалов, занимающихся или интересующихся гибкими методологиями разработки ПО </li></ul>

×