Pragmatic agile adoption 3-rd Agile Gathering, Ukraine 2007 Askhat Urazbaev Agile Coach

Askhat Urazbaev http://urazbaev.ru Agile Coach Quality Center, Luxoft Certified Scrum Master Member of ScrumAlliance Founder of AgileRussia http://agilerussia.ru

Agile Coach

Quality Center, Luxoft

Certified Scrum Master

Member of ScrumAlliance

Founder of AgileRussia

http://agilerussia.ru

Today… What do we want? Adopting agile Selling agile Planning practices (optional)

What do we want?

Adopting agile

Selling agile

Planning practices (optional)

What do we want? Adopt agile in the project! Meet the project goal effectively

Adopt agile in the project!

Meet the project goal effectively

Project Analysis The Goal Problems & Risks Environment

The Goal

The goal The goal must be Related to business Shared and communicated Committed by everyone Earn $5mln Get the market share 51% by the end of year Get investment $5mln examples

The goal must be

Related to business

Shared and communicated

Committed by everyone

Earn $5mln

Get the market share 51% by the end of year

Get investment $5mln

(btw) Manager’s goals Product-driven manager Project-driven manager Demo-driven manager Project goals are not (always) manager’s goals

Product-driven manager

Project-driven manager

Demo-driven manager

Project goals are not (always) manager’s goals

Problems & Risks Problems and risks prevents us from meeting goal Customer doesn’t know what she wants Requirements are changing all the time Employees avoid responsibility examples

Problems and risks prevents us from meeting goal

Customer doesn’t know what

she wants

Requirements are changing all the time

Employees avoid responsibility

Problems Root problems Not enough Collaboration Communication Quality Solution Agile principles

Root problems

Not enough

Collaboration

Communication

Quality

Solution

Agile principles

Adopting principles Slogans don’t work Rituals work Agile practices are rituals (they work even if you don’t understand them) Commitment Reflection Feedback

Slogans don’t work

Rituals work

Agile practices are rituals

(they work even if you don’t understand them)

“ Big bang” adoption Effectiveness time

“ Baby steps” adoption Effectiveness time

Environment All about project environment and context Team structure Team qualifications Project type Contract type Technology Organizational structure Corporate culture ……………

All about project environment and context

Team structure

Team qualifications

Project type

Contract type

Technology

Organizational structure

Corporate culture

……………

Environmental issues Some environmental issues don’t allow to adopt practices Distributed development Uncommitted customer Legacy code Fixed Price Contract examples

Some environmental issues don’t allow to adopt practices

Distributed development

Uncommitted customer

Legacy code

Fixed Price Contract

Uncertain and changing environment Some issues only LOOKS like showstoppers Some issues are undiscovered yet Environment changes all the time

Some issues only LOOKS like showstoppers

Some issues are undiscovered yet

Environment changes all the time

Adopting practice. Collaboration game Select Commit Try Reflect Modify Agile is not religion :-)

Select

Commit

Try

Reflect

Modify

Agile is not religion :-)

There are a few questions left Which order do we adopt practices? How do I “sell” it to people (customers, managers, team members etc)?

Which order do we adopt practices?

How do I “sell” it to people (customers, managers, team members etc)?

Which order do we adopt practices? It depends But basically We improve communication with customer (PO, backlog, planning and demo sessions) We build team (daily scrum, planning poker, taskboards etc.) Then We build quality (Unit Tests & TDD, Automated testing, etc.)

It depends

But basically

We improve communication with customer

(PO, backlog, planning and demo sessions)

We build team

(daily scrum, planning poker, taskboards etc.)

Then

We build quality

(Unit Tests & TDD, Automated testing, etc.)

Agile Adoption Framework Looking for detailed guide? Agile Adoption Framework (A.Sidky)

Looking for detailed guide?

Agile Adoption Framework (A.Sidky)

Selling Agile

Conversation (1) We need pair programming (and this is cool!) No, we don’t (and you are geek)

We need pair programming (and this is cool!)

No, we don’t (and you are geek)

Conversation (2) What’s our most important problem? There’s not enough communication between people Then we need pair programming! We don’t have time for it

What’s our most important problem?

There’s not enough communication between people

Then we need pair programming!

We don’t have time for it

Conversation (3) Why it is a problem? We can’t develop important pieces fast enough. This is critical for business! Don’t you think pairing might help? I’m not sure We might try for 1 iteration and reflect at the end Sounds like a plan!

Why it is a problem?

We can’t develop important pieces fast enough. This is critical for business!

Don’t you think pairing might help?

I’m not sure

We might try for 1 iteration and reflect at the end

Sounds like a plan!

Summary Agile for the sake of agile is wrong Pay attention to the goal and real problems Change is hard. Baby steps Adopting practices. Try and reflect Selling agile is a skill :-)

Agile for the sake of agile is wrong

Pay attention to the goal and real problems

Change is hard. Baby steps

Adopting practices. Try and reflect

Selling agile is a skill :-)

www.agilerussia.ru Agile Community Russia - независимое некоммерческое сообщество, объединяющее ИТ-профессионалов, занимающихся или интересующихся гибкими методологиями разработки ПО

www.agilerussia.ru

Agile Community Russia - независимое некоммерческое сообщество, объединяющее ИТ-профессионалов, занимающихся или интересующихся гибкими методологиями разработки ПО