Jim'sPages => StoryProcess => TeamRoles
While there are many job titles and responsibilities in a large team, we roll them up into only three roles that participate in this process:
| Customer | The people in the Customer role choose what will deliver
business value, choose what to do first and what to defer, and define the tests to show that the system does what it needs to. |
| Programmer | The people in the programmer role analyze, design, test, program and integrate the system. The programmers estimate the difficulty of all stories and track the pace at which they can deliver stories to the customer. |
| Manager | The people in the management role brings the customer and developers together and helps them meld into a smoothly operating team. You don't do the process, you make the process smoother. |
From the book eXtreme Programming Installed by luminary thinker Ron Jeffries:
You have the right to ...
an overall plan, to know what can be accomplished, when and at what cost.
get the most possible value out of every programming week.
see progress in a running system, proven to work by passing tests that you specify.
change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.
be informed of schedule changes, in time to choose how to reduce scope to restore the original date. You can cancel at any time and be left with a useful working system reflecting investment to date.
You have the right to ...
know what is needed, with clear declarations of priority.
produce quality work at all times.
ask for and receive help from peers, superiors, and customers.
make and update your own estimates.
accept your responsibilities instead of having them assigned to you.