adopting agile

25
AgileRussia.ru Pragmatic agile adoption 3-rd Agile Gathering, Ukraine 2007 Askhat Urazbaev Agile Coach

Upload: askhat-urazbaev

Post on 24-Apr-2015

1.695 views

Category:

Business


0 download

DESCRIPTION

3rd Agile Gathering (Kiiv)

TRANSCRIPT

Page 1: Adopting Agile

AgileRussia.ru

Pragmatic agile adoption

3-rd Agile Gathering, Ukraine 2007Askhat Urazbaev

Agile Coach

Page 2: Adopting Agile

AgileRussia.ru

Askhat Urazbaevhttp://urazbaev.ru

Agile Coach Quality Center, Luxoft

Certified Scrum MasterMember of ScrumAlliance

Founder of AgileRussia

http://agilerussia.ru

Page 3: Adopting Agile

AgileRussia.ru

Today…

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

Page 4: Adopting Agile

AgileRussia.ru

What do we want?

Adopt agile in the project!

Meet the project goal effectively

Page 5: Adopting Agile

AgileRussia.ru

Project Analysis

The Goal

Problems & Risks

Environment

Page 6: Adopting Agile

AgileRussia.ru

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

Page 7: Adopting Agile

AgileRussia.ru

(btw) Manager’s goals

Product-driven manager Project-driven manager Demo-driven manager

Project goals are not (always) manager’s goals

Page 8: Adopting Agile

AgileRussia.ru

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

Page 9: Adopting Agile

AgileRussia.ru

Problems

Root problems Not enough

Collaboration Communication Quality

Solution Agile principles

Page 10: Adopting Agile

AgileRussia.ru

Adopting principles Slogans don’t work Rituals work Agile practices are rituals

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

Commitment Reflection Feedback

Page 11: Adopting Agile

AgileRussia.ru

“Big bang” adoption

Effectiveness

time

Page 12: Adopting Agile

AgileRussia.ru

“Baby steps” adoption

Effectiveness

time

Page 13: Adopting Agile

AgileRussia.ru

Environment All about project environment and context

Team structure Team qualifications Project type Contract type Technology Organizational structure Corporate culture ……………

Page 14: Adopting Agile

AgileRussia.ru

Environmental issues

Some environmental issues don’t allow to adopt practices

Distributed development Uncommitted customer Legacy code Fixed Price Contract

examples

Page 15: Adopting Agile

AgileRussia.ru

Uncertain and changing environment

Some issues only LOOKS like showstoppers

Some issues are undiscovered yet Environment changes all the time

Page 16: Adopting Agile

AgileRussia.ru

Adopting practice. Collaboration game

Select Commit Try Reflect Modify

Agile is not religion :-)

Page 17: Adopting Agile

AgileRussia.ru

There are a few questions left

Which order do we adopt practices? How do I “sell” it to people

(customers, managers, team members etc)?

Page 18: Adopting Agile

AgileRussia.ru

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

Page 19: Adopting Agile

AgileRussia.ru

Agile Adoption Framework

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

Page 20: Adopting Agile

AgileRussia.ru

Selling Agile

Page 21: Adopting Agile

AgileRussia.ru

Conversation (1)

We need pair programming (and this is cool!)

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

Page 22: Adopting Agile

AgileRussia.ru

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

Page 23: Adopting Agile

AgileRussia.ru

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!

Page 24: Adopting Agile

AgileRussia.ru

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 :-)

Page 25: Adopting Agile

AgileRussia.ru

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