resumo - the art of agile planning

The Art of Agile Planning

Meu resumo do curso com James Shore

Marcela GuerraMarcela Guerramarcela.guerra@gmail.commarcela.guerra@gmail.com

James Shore

Signatário do manifesto ágil;

XP;

Co-autor de “The Art Of Agile Development” (O'Reilly, 2007)

http://www.jamesshore.com/

The Art of Agile Planning

Curso de 2 dias - 8 horas cada dia;

Práticas durante todo o curso;

Proficiencies of Planning

0: We build code;

1: We create business value;

2: We deliver business value;

3: We optimize business value;

4: We optimize our organization’s business value.

1: We Create Business Value

User stories;

Estimating;

The planning game;

2: We Deliver Business Value

Iterations;

Iteration planning;

“Done Done”;

Daily Stand-Up;

Iteration Commitments;

Velocity;

2: We Deliver Business Value

Slack;

MMF;

One at a time;

3: We Optimize Our Business Value

Purpose;

Customer Discovery;

Effect Mapping;

Adaptive Planning;

Latest Responsible Moment;

4: We Optimize Our Organization’s Business Value

Release Commitments;

User Stories

Planning tool, not requirements;

Represent customer value;

Have clear completion criteria;

3C: Card, Conversation, Confirmation;

User Stories

INVEST: Independent, Nagotiable, Valuable, Estimable, Small, Testable;

Story Template “As a ... I want .. so that ...” - create a template that works for you!

Estimating

Estimates are always wrong;

Errors average out;

The average is wrong too;

But at least it’s consistently wrong;

You need a lot of estimates;

So don’t waste time perfecting the imperfectable.

Estimating

How to estimate:

Story points / Ideal days;

New problem, break into tasks;

Familiar problem, go with your gut;

Tracking actuals can help you synchronize;

Estimating

Tricks:

First of the gate;

Planning poker;

T-shirt size;

Estimate mapping (Mute mapping);

Done Done

It’s “Done Done” when your on-site customer can use it;

Create your own “Done Done”;

Done Done

All tests coded and passed;

Installer/deployer updated;

Data migration tools updated;

Documentation updated;

All work integrated;

All bugs fixed, scheduled or accepted;

Customers reviwed and accepted;

Daily Stand-Up

1: What did you learn yesterday (that might affect others on your team)?

2: What progress did you make and what will you do today?

3: What is impeding you?

4: How confident are you (that we will meet out commitment)?

Slack

Sources of variability:

Technical debt;

Inadequate customer presence;

External disruptions;

Slack

Use slack to pay down technical debt and to learn how to be the customer;

Effect of Slack on Velocity;