I came across a slightly more detailed explanation of how to write feature titles in FDD, basically:
So an example would be, Add an Item to the Shopping Cart or Calculate Total Registrations for Class. Having just gone through an exercise of planning out some features and estimating ‘story points’ on a project, this [...]
Listening again to a Polymorphic Podcast while I was out strolling around Sacramento at 5am on my morning walk, I heard commentary that struck a chord. The person being interviewed on the show was Kent Alstad, a developer with 20+ years of experience, who’s published a book or two in the .NET space. When asked [...]
It’s always important to take time off, so today I’m off to the beach in San Diego. I may post intermittently depending on wireless accessibility.
As a way of introducing a game, I’ve started to implement planning poker to estimate a Product Backlog, aka feature list, for two of my project teams. The experiments have gone fairly well so far. Basically everyone reviews the list of user stories, use cases, features, or tasks hopefully be then the poker rounds start:
To give credit, I picked up this tip from Elizabeth Hendrickson:
To check whether people are actually reading long technical requirements or design documents, liberally sprinkle the text with ridiculous quotes, like “My HoverCraft is Full of Eels.”
The basic idea is that very few people actually read long technical documentation. So why do we [...]