|
|
|
|
|
by sixdimensional
3238 days ago
|
|
I use a technique where I can visualize user stories as if they were part of a regular functional specification. It involves categorizing user stories into features/functions on paper first, and then entering them into our agile tracking tool, and then keeping the paper up to date when new user stories come up. I use dot notation for functional specification grouping into features to uniquely identify user stories, which get tagged in the user stories in the tracking tool. Often they look like "Admin.UserManagement.CreateUser" or similar naming. I give meaning to each level of the hierarchy and document each, so they become like natural epic, feature and story levels. It's extra work, but you basically end up with almost the same thing as if you had written a functional specification with use cases, just lighter weight. If you have the features to do it in your agile tracking tool, you can use tags or categories and then produce a report of user stories that looks the same. I remain convinced that agile and waterfall use almost the same basic tools but just in different ways. I could go on how one can use formal project management Gantt charts to visualize sprints too. |
|