Print your user stories
Let's face it, there is nothing that can replace the use of a physical sprint backlog. But, it's often easier to maintain a product backlog in some digital tool.
If your digital tool of choice cannot print to an index card sized physical version of your user story, you can use this tool.
Simply upload a CSV of the stories you want printed, and we'll take care of the rest.
Upload your CSV here
CSV format
You no longer need to use specific columns in your CSV. As long as it has column headings, you can now map your own to StoryPrinters. Below are explanations of the parts of the cards you'll see when you upload.
- Story Number
- A unique identifier for your story
- Story Title
- A short title to represent the story.
- User Story
- The story itself (As a [user], I need [some feature], so that I get [some value])
- Acceptance criterias
- The things that will tell you when your story is complete.
- Stakeholders
- The people with the money, drive and passion. Your sponsers.
- Effort
- The story points, or whatever effort metric you use.
- Scope
- Whether this was created with the backlog, or an emergent idea.
- Status
- Is it done or ready? (Add 'ready' to this column to be able to import only ready stories. Add 'done' to be able to ignore these when you import.)
- Sprint
- Which sprint did it go in?
- Release
- Which release is it going in?
If you want to see examples of product backlogs which will work with the StoryPrinter, you can use these.
Want it quick? Download here.
Want to copy? Google Doc version here.
Subscribe
Get informed of updates to the application and other news from Mike by subscribing to the newsletter.