The three key components- Lists, Engine and Dashboard – identified in your post are great. Focus on those components will help drive out the necessary details needed for user stories. These components are mostly model builder thoughts when thinking about how to build the user story. As user stories are created with the business owner or business SME, the user story should be related to a business function or capability required in the overall business process. In the Anaplan Agile App the User Story Detail dashboard has a top portion of the user story for the business to complete – Who, What, How and Why. The business team will document the initial description of the user story as well. And the Description box is where I think the three key components you identified in your post would be entered. The evolution of the user story starts with the business team defining a portion or capability of a business process with the four initial boxes on the User Story Detail dashboard. Then as the user story is groomed the solution architect or model builder will work alongside the business team to add more and more details to the Description field. This is an iterative process that drives out all the details within the three key components identified in your post. I would like you to consider one more key component for user stories. The business team will need to define the acceptance criteria for the user story for the user story to be complete. The acceptance criteria are the final key component I would add to the three components you identified. The business team must define how they will validate the model build. The acceptance criteria will be the basis for later development of the test scripts for verification and test. Then the bottom portion of the dashboard within the Anaplan Agile App is for the model build team to track the user story from sprint planning through the build.
... View more