When Agile goes bad'''

1
When Agile goes bad...

• How to stay calm and move forward

2
Sebastien Lambla
Founder of
Helping people achieve greatness
seb_at_serialseb.com - _at_serialseb
http//serialseb.blogspot.com
3
(No Transcript)
4
The organization

• A company becomes agile as a whole

5
Watch out for...

• High turnover
• High documentation environment

6
Managers ctos

• Dealing with the sceptics

7
Engineers are not agile! And they build planes!
And they fly!

• Boeing and Airbus are Lean companies.

8
We have a culture of working hard

• Measure and show what happens with long hours

9
Agile proponents are socialists. We want
superstars!

• Heroes ! Talent

10
In waterfall, I have a full one-year ahead plan.
I need that for my budget

• The budgets have always been estimates. Thats
  not changing...

11
Agile is just an excuse for cowboys development

• Business-focus and releases, and a structured
  approach to development

12
Choosing a project
13
You cant do agile for fixed price projects

• Usually followed by...

14
Scope, resources and release dates are fixed!

• Are they?

15
Building your project team
16
Accountability
17
The Developers
18
Dont impose a methodology. Build a trust
relationship.
19
Heroes

• Detect and address early

20
The customer

• The business, the stakeholders, the sponsors,
  their proxies, etc.

21
The proxy I cant make that call, need to
discuss it

• Proxy without authority is an impediment

22
The Scrum Master

• Manager managing something

23
Im your boss

• Dont manage people, manage issues. Leadership
  over control.

24
We need to take what will work for our
organization and blend it with its current
practices

• You should, but you cant. Not at the beginning
  anyway.

25
Agile is like cooking

• Learn the recipeThe Checklist step
• Grab other peoples recipes
• Blend The final stageif you ever get thereis
  a level of fluency and intuitiveness where you
  can't say what you're doing, but you kind of
  borrow and blend - Cockburn

26
Workshop Iteration 0
27
The workshop
28
(No Transcript)
29
The Planning

• Time, estimates, cards, points, poker game etc.

30
just write it
31
The Scrum Master writes and distribute tasks

• Iterative waterfall ! agile

32
The iteration

• Development

33
Were stopping the SCRUM temporarily because we
know exactly what needs to be done

• Except when you dont.

34
We cant do CI, it doesnt work with our
source-control repository

• Change the tools, not the practices

35
Its done, except for a bit of data integration

• Done ! Done Done

36
The Daily standup
37
People sit down
38
People have conversations
39
Can I talk now?
40
The Retrospective

• Building from experience

41
Its Johns fault.

• The team succeeds or fails as a unit.

42
What do you mean we write less than perfect
code?

• Charge interest to your technical debt!

43
The release party
44
The stakeholders are not coming...

• Ask the hard questions