1. ep delivers function to the customer soon and often

   1. customer defines release through stories

   2. developers negotiate stories

2. simplicity and solving the problem at hand - don't go looking for trouble

3. things that don't relate to stories are infrastructure

   1. infrastructure is bad because it doesn't provide customer function

   2. relate infrastructure back to customer stories - if you can't, don't do it

4. example manage timesheet data and display for any one of a thousand employees

   1. needs a database - or does it

   2. the story is too complicated, split it - manage timesheet data, display employee data, follow a thousand employees

   3. now the database part has a separate story - until addressed, deal with it in other, simpler ways

   4. deliver customer function now - maybe it will be good enough to last

5. doesn't adding delayed function get harder as the system grows

   1. ep is about cheap system changes - refactoring, simplicity, no duplication, testing

   2. adding function later should be not much more expensive than adding it now

   3. and you may not need it at all

This page last modified on 19 July 2001.