what does SMART mean in the context of requirements?
User stories should be specific, measurable, achievable, relevant and timeboxed. Specific, user stories should not be vague. User stories should be measurable so they can be testable using numbers as criteria. They should also be achievable, so the user story should be finished in one implementation. User stories should have business value to one or more stakeholders using the 5 whys to find more stakeholders. Timeboxing means stopping work on a story when the time budget is up, then giving up or dividing the user story into smaller ones and then rescheduling those for the next iteration. One can also go to the customer to find the highest value story and doing that.
No comments:
Post a Comment