Use a table to list out your user stories, along with description, priority, and notes. This is a great place to link to other Confluence pages to provide more detail including customer interviews, and planning pages. What exactly are they trying to achieve? How does the solution you're proposing fit into it? The team goals and business objectives section is meant to give you a chance to add some color and context to your requirement.Ī good way to think about your goals is from your customers perspective. Outline goals, business objectives, and strategic fit Keep reading to see what that summary page looks like 3. The page properties macro is a powerful macro that allows you to create a summary page that pulls in information from multiple pages. In this case, a summary page could bring in each of the fields in your table so you can see who is involved or the status of a given requirements page. When you create your first product requirement doc in Confluence you'll notice the project details are in a table located in a page properties panel. Target release: When is it projected to ship? If you use JIRA, link to your JIRA project.Status: What's the current state of the program? Use the s tatus macro to quickly show if you're on target, at risk, delayed, deferred, etc.Participants: Who is involved? Use include the product owner, and other stakeholder s.Either way, you should capture key high level details at the top of the page for easy reference. Your requirements page might be laser focused on a particular feature, or it might include requirements for a release that includes multiple features. The template will help point you in the right direction, and provide some best practices for what content to include. Get started with the special template that we've included. Here's how you can create that requirement and build a shared understanding in Confluence: 1. Start with our Product Requirements blueprint When your requirement doc is created and the details are all in one place, it makes it a lot easier for Development and Design to provide immediate feedback and input. When this happens you can iterate quickly and implement work right away. At Atlassian we find the best way to do this is to create a collaborative product requirement to hash out details for large complex epics.
#How to use confluence templates software#
The most important takeaway is: the best way to kick-off your software projects is to build a shared understanding amongst your team. We've written quite a bit about the conundrum of writing requirements in an agile environment. By Terrence Caldwell, published August 31st, 2015 Creating a collaborative product requirement