Estimating With Inch-Pebbles | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Departments > Methods & Means
Every project can use inch-pebbles at some point to estimate tasks and monitor progress.
This is the third installment in a series of adapted excerpts from the author’s new book, Manage It! Your Guide to Modern Pragmatic Project Management, published by Pragmatic Bookshelf.
Inch-pebbles are the breakdown of each project task into very small pieces, no more than two days in duration, generally only one day long. If you're familiar with Extreme Programming (XP), inch-pebbles are user stories. Inch-pebbles are either done or not done; they are not some percentage complete. Collections of inch-pebbles are the multiple-day or multiple-week tasks that teams normally create when they define tasks in a schedule. In reality, inch-pebbles are a way to define tasks that fit into small timeboxes — one or two days in duration.
Every project can use inch-pebbles at some point to estimate tasks and monitor progress.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement