XP Workflow

XP Workflow.md

Inception

• First meeting with client to tie down on stories

Daily standup (daily)

• what have you done yesterday?
• what will you do today?
• Any blockage?
• Any other updates?

Story acceptance meeting (daily or whenever a story is completed)

Purpose: To get points for velocity

Grounding:

• We love rejection (no rejection is bad as client is not committed)
• This is an important collaboration point where client can check our work and align us continuously to build client's product
• It is about giving you what you need and not what we think you know

Go through each stories in the iteration

• Restate story to client
• Make sure client has tested it properly
• Make client accept the story
• If story is rejected (rejection is good as it makes us build the product closer to your needs) -- Additional requirements to be placed in another story -- Small updates to be placed as task (please reject the story)

Stories closed will not be reopened anymore due to velocity tracking

Iteration meeting (weekly)

• do story acceptance first
• choose stories to do next week -- prioritize basic workflow initially, then later on to work on feature priorizations
• can consider to do retrospective on the first iteration meeting to ensure working impression is good
• First iteration meeting to show the inception's cards points rated so as to intro client on why and how we assign points to the stories

Release Planning (roughly every 3-4 weeks)

• Can be part of iteration meeting
• To decide on the stories in the next release

Retrospective (roughly every 3-4 weeks, can be more frequent)

• Frame participants in the retrospective first (eg. this is for the project, this is for the last company outing, etc)
• Get :), :|, :(
• Work on the :( to resolve it
• Work on the :| to resolve it
• Create action items which are to be resolved during iteration and by next retrospective