Breaking down a complex story at project start
I'm trying to get to grips with agile project management (with Pivotal
Tracker) but keep finding myself running into walls when trying to define
the first few stories of a project. Take for example this very simple
story:
"A user should be able to tag a product"
Assuming I've already defined "product" elsewhere, this story would
possibly involve writing a polymorphic tagging system under the hood, on
completion of that system id be able to finally add the ability to tag a
product.
My problem is with the amount of work hidden in this story. I can define
tasks to get the story done but stories as a whole are supposed to be 1-2
days work? I don't feel right about the story just revealing the tip of
the iceberg but that's the only part that relates to the User.
How do you overcome this kind of thing? What are the best practices?
No comments:
Post a Comment