This article discusses the clarity of requirements for Agile software development and explains how you can use a four-step process for gathering them with the four levels of agile requirements. Author: Sally Elatta, Agile Transformation Don’t you just love the word ‘Requirements’? It’s just so clear isn’t it – NOT! Have you ever heard your business customer say ‘I’ve already given you my requirements’ and the team then says ‘We haven’t received clear or detailed requirements’? The other side to this is when the team tells the customer ‘You are giving us too much details, don’t tell us where the button goes on the screen, just tell us what you want’. No wonder we have so many requirements related issues on our projects! During one of my previous PMI webinars we talked about Agile Requirements – Breaking Down EPICs and Prioritizing. I will take a stab through this blog at summarizing the levels of Agile (and frankly non Agile) requirements and how you can use a four-step process for gathering them. First, let’s start with the picture below. The picture shows four levels of requirements, and also on the left is the four-step process for gathering requirements. Agile Requirements Levels Visioning: This is the initial step of gathering requirements. The goal is to help identify all the Themes and some features desired. This exercise begins to define the scope of what is expected. Brainstorming: The goal of this step is to identify all the features and stories desired. The key [...]
The post Four Levels of Agile Requirements first appeared on Scrum Agile Project Management Expert.↧
