From the course: Applying Agile MoSCoW Prioritization

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Requirements cycle

Requirements cycle

From the course: Applying Agile MoSCoW Prioritization

Start my 1-month free trial

Requirements cycle

- The big question in an agile project is, when? When should I be defining and prioritizing the requirements? The good news is, there's a clear cycle to be followed and it starts in the feasibility state. In this early stage, it's unlikely that we'll know much about the project, so we're just trying to establish what the project will deliver. So, at this point, you'll probably only have a few high-level requirements. We're just trying to determine whether the project is feasible, so we don't really want to have to put too much work into requirements gathering yet. Importantly, the requirements at this level must be prioritized. We'll need to check that not everything is a must-have, as we'll need to have some flexibility once work begins. Once we've received the go-ahead, the project moves into the definition stage and the high-level requirements are broken down a little further. These broken down requirements will be prioritized even further. As you can see, just because a high-level…

Contents