Anatomy of a Story Card
This article will cover all the things that can be added to a story card in AgileZen when it's created. Stories are cards that represent work items that need to be completed. To create a new story, open the add stories panel by clicking "add" in the top right.
When you open the panel, you'll see the option to add several pieces of information to a card. Many of these fields are optional and open-ended, so you can use them whatever way works best for you. Once you add in all of the information and create the card, it will look something like the example below. The numbers correspond to the information on the card and are covered in more detail below.
The text field is where you enter the description of the work item that needs to be complete.
The size of a story can be thought of as an estimate. You can either create a numeric size using hours or use t-shirt sizes like small, medium, and large.
The priority field can also be numeric or text and is a way to designate the importance of the story. For example, a story that’s priority one could be thought of as the story that needs immediate attention. Another example could be designating stories as high or low priority.
Stories also allow you to set a deadline, so everyone on your team will know when a particular story is due. You can type in the deadline or pick it from this calendar view. If the story is not complete by the date selected, the deadline field will turn red indicating the story is past due and needs the attention of the team.
You can select an owner for the story from the dropdown of collaborators on your team. This is the person that is ultimately responsible for the work related to this story. If you don’t know who the owner will be or prefer to wait to assign it, you can select unassigned.
Tags can be added to stories to group them together based on a common theme. Tags could be used to group stories associated with a feature, team, or time period (like an iteration). A tag can help differentiate a particular story from others and is a great way to use filters as a substitute for the swimlane method of organization that is sometimes used on physical kanban boards.
You may also want to pick a color for the card that is different from the default of grey. Adding color to cards is also an easy way to group story cards together.
Additional details can also be added to a story card. In this section you can add more information about a story that doesn’t necessarily belong in the text of the story. This field can be used for anything from acceptance criteria for the story to comments or questions. If a story has details, you'll see this indicator on the card.
A task can be thought of as a step that needs to be complete as part of a story. These items are meant to be short, one-line description and aren’t related to any particular phase. The task list functions more like a to-do list of items to help complete the story.