This blog will cover primarily technical aspects of Microsoft Dynamics AX.
I have posted previously on AX and Scrum this is just a continuation of my series.
This post shall cover what a story is. A user story is a short description of what is needed. The main purpose of this is to be able to estimate the piece of work.
Below is an actual story i have worked on.
We could (should) have written this different. In scrum they teach you to write it in the perspective of the actor. For example: “As a work order user, I would like to create a work order and submit it to workflow. I would like to get alerts and notifications.”
One thing we like to do in our team is set up Acceptance criteria's (those AC1 2 AC5 that you see in the screenshot). At the end of the day we use it to tell us a story is done.
The next step for use once we have given it sized the story and accepted it into a sprint. We start putting some finer details. We break down the task.
Our comment tasks that we use and to use to indicate a story is done are:
The above tasks are pretty comprehensive and allows us to estimate how long a story takes as each task is estimated in hours. This is not set in concrete but this is what we do.
The results you see on a series of posts. The overview contains a flow diagram that was roughly documented as part of the functional design.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics