Requirements gathering gets confusing when one starts reading about user stories, use cases, volere templates and numerous other techniques invented to capture them. Add to it, the techniques used to prioritize requirements (MoSCoW) and then estimate them (FP points, Use Case Points, User Story Points).
Key lessons I have learnt/re-learnt
1. The details captured in use cases are more useful to developers and testers.
2. User Stories are very useful in discussions priorities with the client & in planning iterations. Each user story, in fact, corresponds to a scenario within a given use case where a scenario is defined as a single path of use case execution.
Subscribe to:
Posts (Atom)
What is success?
The journey of life takes us through varied experiences like landing an admission at a prestigious college, earning a degree, getting hired,...
-
Recently after a domain password change, I got the following error in trying to run the webrole. Can not log on locally to WebRole as us...
-
I was trying my hands at creating a .NET 2.0 component that can be consumed by a COM application. One of the errors I got in the process of...
-
After editing the post-build event of my project in VS 2005, the following error came up "'Exec' task needs a command to execut...