War For Agile

1,471 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
1,471
On SlideShare
0
From Embeds
0
Number of Embeds
233
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

War For Agile

  1. 1. War for Agile Alimenkou Mikalai mailto:lumii.subscriber@gmail.com 28.06.2008
  2. 2. Stop and think! <ul><li>To start or not to start? </li></ul><ul><ul><li>Your team already has good enough process </li></ul></ul><ul><ul><li>You don’t have motivated team </li></ul></ul><ul><ul><li>You don’t have any practical experience in Agile </li></ul></ul><ul><ul><li>It is your temporary project </li></ul></ul><ul><ul><li>You are only one person who like and understand Agile principles </li></ul></ul>
  3. 3. Why to start? <ul><li>You don’t like </li></ul><ul><ul><li>Overtimes </li></ul></ul><ul><ul><li>Buggy code </li></ul></ul><ul><ul><li>External plan </li></ul></ul><ul><ul><li>Tons of documentation </li></ul></ul><ul><ul><li>… </li></ul></ul><ul><li>You like </li></ul><ul><ul><li>Work for fun </li></ul></ul><ul><ul><li>Team collaboration </li></ul></ul><ul><ul><li>Build useful software/product </li></ul></ul><ul><ul><li>Improving yourself </li></ul></ul><ul><ul><li>… . </li></ul></ul>
  4. 4. Fixed price projects <ul><li>Make initial estimations more Agile </li></ul><ul><li>Reduce time to first deadline </li></ul><ul><li>Use Agile internally to predict failures </li></ul><ul><li>Introduce internal releases </li></ul><ul><li>Show benefits of Agile process </li></ul><ul><li>Try to use popularity of Scrum </li></ul>
  5. 5. Hourly paid projects <ul><li>Use team as interface with Agile based implementation </li></ul><ul><li>Introduce internal process and make it company standard </li></ul><ul><li>Make proxy for external dependencies </li></ul><ul><li>Reduce overtimes </li></ul>
  6. 6. Distributed projects <ul><li>Move to separate teams approach </li></ul><ul><li>Often mix teams </li></ul><ul><li>Extend communication environment </li></ul><ul><li>Use special Agile tools </li></ul>
  7. 7. Internal projects <ul><li>Find person suitable for customer role </li></ul><ul><li>Take part in initial project planning </li></ul><ul><li>Proxy customer </li></ul><ul><li>Make internal demos and deadlines </li></ul>
  8. 8. Common best practices <ul><li>Hide team from external pressure </li></ul><ul><li>Use all engineer practices </li></ul><ul><li>Experiment and let team to make decision </li></ul><ul><li>Reuse team members for different roles </li></ul><ul><li>Build the trust </li></ul><ul><li>Be ready to any questions </li></ul><ul><li>Make management to believe in Scrum </li></ul><ul><li>Explain differences between team and management roles </li></ul>
  9. 9. Adoption issues <ul><li>No other Agile project exists </li></ul><ul><ul><li>Don’t use word Agile </li></ul></ul><ul><ul><li>Ask for a chance </li></ul></ul><ul><ul><li>Start with engineering practices </li></ul></ul><ul><ul><li>Find holes in existing process </li></ul></ul><ul><li>Low authority to make changes </li></ul><ul><ul><li>Be an example </li></ul></ul><ul><ul><li>Show benefits to team members </li></ul></ul><ul><ul><li>Find support from management </li></ul></ul><ul><ul><li>Be reliable and get the authority </li></ul></ul>
  10. 10. Adoption issues <ul><li>Unfriendly environment for Agile </li></ul><ul><ul><li>Adopt practices for yourself and share results </li></ul></ul><ul><ul><li>Make job done with highest quality </li></ul></ul><ul><ul><li>Show hidden issues </li></ul></ul><ul><li>Bad previous experience with Agile </li></ul><ul><ul><li>Don’t use word Agile </li></ul></ul><ul><ul><li>Don’t adopt all practices initially </li></ul></ul><ul><ul><li>Have an answer to each question </li></ul></ul>

×