User Story Templates

A couple of people emailed me and asked me what the story cards looked like on our information radiator.

It is important to note that these story cards are only drafted after extensive modeling and feedback sessions during our modeling week.  We don’t use them in the traditional XP fashion and caution should be taken when implementing as this may deter from fluid communication if used improperly.

These templates are word documents that have been formatted to fit on a 4×6 index card.


As you can see the story card has several sections:

  • Story Name:  This is the story name but it also contains the [Story Points] estimate in brackets.
  • Business Analyst: This is the business analyst that has been assigned to the story.
  • Systems Analyst: This is the systems analyst that has been assigned to the story.
  • Developer:  This is the developer who has elected to make themselves responsible for the teams delivery of this story.
  • Architect: This is the Architect who is responsible for insuring that the story stays within the Architectural Guidelines of the framework.
  • Estimate SIT:  This is the date that team estimates when the story should be completed by.

If you notice the only stake holders that are listed are Pigs!  If you have other Pig roles you may want to include them as well.  Don’t include the chickens!

The templates can be downloaded from here.


Note: Some of you may be wondering where the Acceptance Test are.  Well the stories are sent to Mercury Quality Center and the acceptance test plans are written against the stories there.

About Joe Ocampo

My personal philosophy is simple: "Have a good strategy that sets the environment for success through the enablement of the whole. Be agile but with a mind towards pragmatism. Delegate to the best qualified individuals, but don’t be afraid to involve yourself in all parts of a job. Treat everyone with respect, humility, and with a genuine pursuit towards excellence." Respected business and technical leader with expertise in directing organization towards effective results driven outcomes. Proven ability to perform and communicate from both technical and business perspectives. Strong technical and business acumen developed through experience, education and training. Provides the ability to utilize technology, harness business intelligence and execute strategically by optimizing systems, tools and process. Passionate about building people, companies and software by containing cost, maximizing operational throughput and capitalize on revenue. Looks to leverage the strengths of individuals and grow the organization to their maximum potential by harnessing the power of their collective whole and deliver results. Co-Founder of
This entry was posted in Agile Project Coaching & Management, Agile Teams, Tools. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

3 Responses to User Story Templates

  1. Nice… thanks Joe.

    Best Regards.

  2. Baz says:

    just looking at the stakeholders and i’m noticing that there is no mention of Quality assurance or tester

    Is this an ommision?:

  3. Joe Ocampo says:

    Our SA’s function as our QA analyst as well. But you should be able to add any additional stakeholder as you see fit.