Problems

Lack of knowledge

• Problems will appear
• Mistakes will be made
• Requirements will be underspecified

Presence of Change

• Systems
• Frameworks
• Requirements
• Methods

Methods

Rule of 3

Estimate the worst case scenario, and multiply it by 3.

• Inaccurate;
• Probably still not enough.

Velocity + Slack

• Estimate with story points, not time;
• Velocity: points per sprint;
• Give it some slack for problems.

Slack: Time to refactor or to compensate

A number

Implementation

A feature takes N points to implement.

Before implementation

• Analysis
• Preparation

Analysis

• Find sub-tasks;
• Decide the approach.

How long?

N / 2 (max)

Preparation

• Refactor to make implementation easier.
• Not always required.

How long?

N / 2 (max)

Test

• Before or after, there should be tests;
• May require refactoring.

How long?

N (max)

Review

• Code should be reviewed;
• Often requires refactoring.

How long?

N (max)

[considering real time, not effort]

Documentation

• Lol...

How long?

N / 2 (max)

4.5

(not considering respecs, approach changes, etc)