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

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 … .

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

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

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

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

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

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

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

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