practices of an agile team

Post on 08-May-2015

6.277 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

Agile2008Conference

TRANSCRIPT

Practices ofan Agile Team

Eiwa System Management, Inc.Fumihiko Kinoshita

About Me✓Name: Fumihiko Kinoshita✓Mail: fkinos@gmail.com✓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.

Practices of an Agile Developer

Japanese Edition

The Art of Agile Development

My Team’s Practices

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

WeeklyTime Box

IterationPlanning Retrospective

Development

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

Agile Retrospectives

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

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

Retrospectives✓KPT (Keep/Problem/Try)

Keep

Problem

Try

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

Keep

Problem

Try

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

Nov. Dec. Jan.

Retrospectives✓Graduation ceremony✓Emotions

Keep

Problem

Try Happy

Sad

Estimate Retrospectives

✓The data is gathered and analyzed

Positive Strokes

✓Paying compliments to team member

Feedback

IterationPlanning Retrospective

Development

Feedback

Lean Software Development

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

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

Agile Retrospectives

Post-Iteration Party

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

cash!

Sake✓Kagetora

Sake✓Hangover✓Serious reflection

Drank too much

AgilePlanning

Mon Tue Wed Thu Fri Sat Sun

1

Development

Retro-spectives

Development

Off2 Iteration Planning

3 Slack

Iteration Planning

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

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

remaining time.

Estimating

Extreme Programming Installed

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.

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.

Taboo Word

“We’ll Try”The saddest two words

a programmer can ever say.

Lister’s Law

People under time pressure don't think faster.

Estimate and Promise

We cannot promise the precise outcome.

Estimate and Promise

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

about what has happened.

Iteration PlanningAdjust✓the assignment of team

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

This is my job as a leader.

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

Kaiouken

Iteration Planning

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

Iteration Planning

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

Darts

Task Kanban

Task Kanban✓Football Pitch

Task Kanban✓Time.now

Task Kanban✓School Timetable

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

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

Energized Work

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

overtime, I want overtime pay!

Overtime Tickets

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

We changed office regulations without permission.

Agile Team

Frequent meeting with the customer

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

has happened.

Honesty pays— BUSHIDO

The most delightful wordsI have heard from a customer

”BecauseI trust you.”

Trust

Slack

Parent’s Rule

Always give trust slightly in advance of demonstrated trustworthiness.

Trust

Team

Trust

TrustTrust

Trust

Member

Customer

Leader

What It Feels Like

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

customer.✓I want to do the work once

again with this team.

Thank you for your attention.

Any Questions?

top related