786-878-8302  evan@tiernine.com

Agile and Lean Requirements Gathering


The Product Owner is a key role to managing requirements within the Agile and Lean framework.  Defining requirements under Agile is a shared task between the Product Owner, the Designer, the Business Analyst and the Scrum team.  These roles on the Scrum team need to have a shared understand of the high-level requirement, without getting stuck in specifying all the exact details to deliver shippable software product.

When the scrum team has as shared understanding of the requirement, you don’t need all the minute details spec’d out in the beginning

When writing requirements in a toolset such as Confluence, it’s good practice to use a common template across the entire project. This makes it very easy for the team to consistently follow the requirements and provide positive feedback.

In Confluence, the Product Requirements Blueprint plug-in is a very good template to capture requirements across your project.

product-requirements-blueprintUse a Lean One Page Dashboard

Generally speaking, we should be tracking 8 different dimensions for all requirements:


  1. Define project details:
    1. Key stakeholders
    2. Status (On Schedule, At Risk, Delayed, Deferred)
    3. Target Release (Potentially Releasable Product Increment “PRPI”)
  2. Goals and business objectives
  3. Background and strategic fit to company objectives
  4. Assumptions (Technical and Business)
  5. User Stories
    1. Create links to all user stories in JIRA
    2. Include the following:
      1. User persona
      2. Pre-Conditions
      3. Actions I Can Take
      4. Things I Can See
      5. Post-Conditions
    3. Capture screen shots and other project artifacts
    4. Include success metrics. What is acceptance criteria for this user story?
  6. User interaction and Design (IE.  wireframes)
  7. Outstanding questions
  8. What is out of scope! (Call out what is NOT included in the requirement)

By managing requirements on a single page, it then becomes the center of focus for the scrum team throughout the project. The objective is to make the requirements gathering process “nimble,” so that any changes in the business model can be rapidly prioritized and scheduled for a sprint.


Leave a Reply

Your email address will not be published. Required fields are marked *