71
Practices of an Agile Team Eiwa System Management, Inc. Fumihiko Kinoshita

Practices Of An Agile Team

Embed Size (px)

DESCRIPTION

Agile2008Conference

Citation preview

Page 1: Practices Of An Agile Team

Practices ofan Agile Team

Eiwa System Management, Inc.Fumihiko Kinoshita

Page 2: Practices Of An Agile Team

About Me✓Name: Fumihiko Kinoshita✓Mail: [email protected]✓Blog: http://fkino.net✓Technical Lead ✓Practitioner of Agile Development✓XP Japan Users Group Staff✓I translated “Practices of an Agile

Developer” into Japanese.✓I like XP.

Page 3: Practices Of An Agile Team

Practices of an Agile Developer

Page 4: Practices Of An Agile Team

Japanese Edition

Page 5: Practices Of An Agile Team

The Art of Agile Development

Page 6: Practices Of An Agile Team

My Team’s Practices

Page 7: Practices Of An Agile Team

Agenda✓Agile Retrospectives✓Agile Planning✓Energized Work✓Agile Team

Page 8: Practices Of An Agile Team

WeeklyTime Box

Page 9: Practices Of An Agile Team

IterationPlanning Retrospective

Development

Page 10: Practices Of An Agile Team

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

Page 11: Practices Of An Agile Team

Agile Retrospectives

Page 12: Practices Of An Agile Team

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

Page 13: Practices Of An Agile Team

Retrospectives✓Once a week✓KPT✓Retrospective Driven✓Learning team.✓Continuous Kaizen.

Page 14: Practices Of An Agile Team

Retrospectives✓KPT (Keep/Problem/Try)

Keep

Problem

Try

Page 15: Practices Of An Agile Team

Retrospectives✓First Retrospective in the project✓“Try” area is large

Keep

Problem

Try

Page 16: Practices Of An Agile Team

Retrospectives✓Final Retrospective at the end of the project✓Timeline

Nov. Dec. Jan.

Page 17: Practices Of An Agile Team

Retrospectives✓Graduation ceremony✓Emotions

Keep

Problem

Try Happy

Sad

Page 18: Practices Of An Agile Team

Estimate Retrospectives

✓The data is gathered and analyzed

Page 19: Practices Of An Agile Team

Positive Strokes

✓Paying compliments to team member

Page 20: Practices Of An Agile Team

Feedback

Page 21: Practices Of An Agile Team

IterationPlanning Retrospective

Development

Feedback

Page 22: Practices Of An Agile Team

Lean Software Development

Page 23: Practices Of An Agile Team

Lean Principles✓Eliminate waste✓Amplify learning✓Decide as late as possible✓Deliver as fast as possible✓Empower the team✓Build integrity in✓See the whole

Page 24: Practices Of An Agile Team

Lean Principles✓Eliminate waste✓Amplify learning✓Decide as late as possible✓Deliver as fast as possible✓Empower the team✓Build integrity in✓See the whole

Page 25: Practices Of An Agile Team

Agile Retrospectives

Page 26: Practices Of An Agile Team

Post-Iteration Party

✓Drinking party✓Every 2 weeks✓You’ll need some

cash!

Page 27: Practices Of An Agile Team

Sake✓Kagetora

Page 28: Practices Of An Agile Team

Sake✓Hangover✓Serious reflection

Drank too much

Page 29: Practices Of An Agile Team

AgilePlanning

Page 30: Practices Of An Agile Team

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

Page 31: Practices Of An Agile Team

Iteration Planning

Page 32: Practices Of An Agile Team

Iteration Planning✓One week is 32 hours✓The remaining 8 hours are

“Retrospective”, “Iteration Planning” and “Slack”.✓Various Kaizen is done in

remaining time.

Page 33: Practices Of An Agile Team

Estimating

Page 34: Practices Of An Agile Team

Extreme Programming Installed

Page 35: Practices Of An Agile Team

Programmer Rights✓The programmer has the right to estimate work

and have those estimates respected by the rest of the team.

✓The programmer has the right to honestly report progress.

✓The programmer has the right to produce high-quality work at all times.

✓The programmer has the right to know what is most important to work on next.

✓The programmer has the right to ask business-oriented questions whenever they arise.

Page 36: Practices Of An Agile Team

Programmer Rights✓The programmer has the right to estimate work

and have those estimates respected by the rest of the team.

✓The programmer has the right to honestly report progress.

✓The programmer has the right to produce high-quality work at all times.

✓The programmer has the right to know what is most important to work on next.

✓The programmer has the right to ask business-oriented questions whenever they arise.

Page 37: Practices Of An Agile Team

Taboo Word

Page 38: Practices Of An Agile Team

“We’ll Try”The saddest two words

a programmer can ever say.

Page 39: Practices Of An Agile Team

Lister’s Law

People under time pressure don't think faster.

Page 40: Practices Of An Agile Team

Estimate and Promise

We cannot promise the precise outcome.

Page 41: Practices Of An Agile Team

Estimate and Promise

We can✓estimate what we can do.✓promise to do our best.✓promise to tell the truth

about what has happened.

Page 42: Practices Of An Agile Team

Iteration PlanningAdjust✓the assignment of team

members.✓the scope of the work.✓the limits.

Page 43: Practices Of An Agile Team

This is my job as a leader.

Page 44: Practices Of An Agile Team

But if we don't finish the work we've committed to...

Page 45: Practices Of An Agile Team

Kaiouken

Page 46: Practices Of An Agile Team

Iteration Planning

✓Sign up for the tasks that you want to do.

Page 47: Practices Of An Agile Team

Iteration Planning

If more than one person signs up for the same task ...

Page 48: Practices Of An Agile Team

Darts

Page 49: Practices Of An Agile Team

Task Kanban

Page 50: Practices Of An Agile Team

Task Kanban✓Football Pitch

Page 51: Practices Of An Agile Team

Task Kanban✓Time.now

Page 52: Practices Of An Agile Team

Task Kanban✓School Timetable

Page 53: Practices Of An Agile Team

Toyota Kanban System

✓One-piece-At-a-Time Production✓Waiting in one line✓Standardization and multi-skill✓Start as late as possible✓Total amount management

Page 54: Practices Of An Agile Team

Toyota Kanban System

✓One-piece-At-a-Time Production✓Waiting for in line✓Standardization and multi-skill✓Start as late as possible✓Total amount management

Page 55: Practices Of An Agile Team

Energized Work

Page 56: Practices Of An Agile Team

Energized Work✓40 hours a week✓Though I do not work

overtime, I want overtime pay!

Page 57: Practices Of An Agile Team

Overtime Tickets

Page 58: Practices Of An Agile Team

Overtime Tickets✓Assume 30 hours of overtime deemed✓1 ticket = 30 minutes✓For every 30 minutes of overtime you

work, you put a ticket into the box.✓When working overtime is unavoidable, a

leader can distribute additional tickets.✓Remaining tickets = Overtime pay

Page 59: Practices Of An Agile Team

We changed office regulations without permission.

Page 60: Practices Of An Agile Team

Agile Team

Page 61: Practices Of An Agile Team

Frequent meeting with the customer

✓Every one or two weeks.✓“Problem vs. us”✓We tell the truth about what

has happened.

Page 62: Practices Of An Agile Team

Honesty pays— BUSHIDO

Page 63: Practices Of An Agile Team

The most delightful wordsI have heard from a customer

”BecauseI trust you.”

Page 64: Practices Of An Agile Team

Trust

Page 65: Practices Of An Agile Team

Slack

Page 66: Practices Of An Agile Team

Parent’s Rule

Always give trust slightly in advance of demonstrated trustworthiness.

Page 67: Practices Of An Agile Team

Trust

Team

Trust

TrustTrust

Trust

Member

Customer

Leader

Page 68: Practices Of An Agile Team

What It Feels Like

Page 69: Practices Of An Agile Team

✓You seem to take pleasure in work.✓Your team also includes the

customer.✓I want to do the work once

again with this team.

Page 70: Practices Of An Agile Team

Thank you for your attention.

Page 71: Practices Of An Agile Team

Any Questions?