Gallery Opening + Flickr Test

this is a really nice painting
DSC00212.JPG
Originally uploaded by subherwal

Tasker/Implementer Discussion

Tasker - defined at the time of task card creation; a tasker takes a story and ...

a) defines AC/DCs (customer, acceptance criteria, and deliverables) and posts them out to the Wiki

b) creates and estimates the task cards associated with the story

This is done during the 'post pre-planning' meetings, which take place the day of the pre-planning meeting.

Implementer (or 'Prime' or 'Owner') - the Implementer is established when the actual work is taken up and is typically the first person to take down a task card associated with a story. When that happens, the person's name should be attached to the story card (the blue card). The Implementer...

a) drives the story

b) assures quality (by making sure that the acceptance criteria can be met), and

c) is responsible for keeping tabs on the status of the card

The Implementer can change over time, by hingeing off with someone, so he is not married to the task forever. Note that 'responsible' does not mean 'subject to blame' if the story is not finished, but does mean that he is accountable for the status of the story and for knowing why (and why not) the tasks associated with the story have (have not) been completed.

Milestone Driven Development - raw notes

Milestone Driven Development

extremely raw notes...

fdd and gdd - drive to completion a large piece of functionality. However, mdd takes that a step further; drive to milestones that (eventually) drive to goals.

mdd -> gdd -> fdd

Milestones are:
+ smaller "goals"; rungs on a ladder (best practice: m'stones no more than a sprint long)
+ achievable; small yet demoable
+ less risky: smaller estimates, fewer unknowns
+ more manageable: verify doneness on smaller deliverables. Change milestone roadmap in an agile environment all the time. Example: 1,2,3 can become 1,2,a,3 once 1 is complete, for instance and may not change too much.

+ easier to define ACDC

+ means to an end; crawl before you walk; etc.

assists:
management - track progress sprint to sprint; if a milestone is in jeopardy, the drop goal is too unless you descope or reprioritize
developers - can modify "roadmap" at any milestone
testers - can validate smaller pieces

Example:

Feature: Add to Shopping Cart (FDD)

Release/Drop Goal: Place a single transaction in shopping cart (GDD)

Milestones (prioritized - some may be parallel efforts): (MDD)

1. Write User Stories
2. Implement User Stories
3. Complete Validation
4. Duplicate Checking
5. Security, etc...

Heading to RailsConf

My Conference Plan