Agile requirements are a product owner's best friend. Product owners who don't use agile requirements get caught up with spec'ing out every detail to deliver the right software (then cross their fingers hoping they've spec'ed out the right things).

Agile requirements, on the other hand, depend on a shared understanding of the customer that is shared between the product owner, designer, and the development team. That shared understanding and empathy for the target customer unlocks hidden bandwidth for product owners. They can focus on higher-level requirements and leave implementation details to the development team, who is fully equipped to do so – again, because of that shared understanding.

Requirements
Confluence
Creating a shared understanding among teams

Creating a shared understanding among teams

When writing a requirements document, it's helpful to use a consistent template across the team so everyone can follow along and give feedback. At Atlassian, we use Confluence to create product requirements with the product requirements blueprint.

next

Define project specifics

next

Team goals and business objectives

next

Background and strategic fit

next

Assumptions

next

User Stories

next

User interaction and design

ok

Questions

Your point of contact:

 
Sarah Antrop

Agile & Scrum Consultant

Sarah Antrop
Specialization: 
Testmanagement, Bitbucket, Git, Bamboo
Platinum Solution Partner Enterpise

Atlassian Enterprise Platinum Solution Partner

Solution Partners provide the services, implementation, consulting, and unique solutions that help our users create what's next.