• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
War For Agile

War For Agile






Total Views
Views on SlideShare
Embed Views



4 Embeds 225

http://www.agileukraine.org 134
http://451f.com.ua 89 1
http://webcache.googleusercontent.com 1


Upload Details

Uploaded via as Microsoft PowerPoint

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.

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

    War For Agile War For Agile Presentation Transcript

    • War for Agile Alimenkou Mikalai mailto:lumii.subscriber@gmail.com 28.06.2008
    • 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
    • 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
        • … .
    • 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
    • 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
    • Distributed projects
      • Move to separate teams approach
      • Often mix teams
      • Extend communication environment
      • Use special Agile tools
    • Internal projects
      • Find person suitable for customer role
      • Take part in initial project planning
      • Proxy customer
      • Make internal demos and deadlines
    • 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
    • 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
    • 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