Your SlideShare is downloading. ×
War For Agile
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

War For Agile

1,243
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,243
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×