Analyze requirements

- As project managers it helps a lot when we're organized. Like when we collect requirements, we also need to capture some information about each one. In other words, we need to document their attributes. That lets us build structure around the requirements that will form the basis for our project. I use a spreadsheet to track attributes and I've included an example in the course downloads which captures the attributes recommended in the business analysis body of knowledge. Here are the 10 attributes that they focus on. Absolute reference. This is the identification number for your requirement. Assigning a number makes it easier to track requirements over time even if the name or the description changes. Complexity. How difficult will it be to address the requirement? You might want to rate this on a scale like one to 10; or you can rate it easy, medium, or hard; or you might even put in an estimate for the number of hours you think it will take to address the requirement. Risk. How much uncertainty is there about the requirement? Do you feel like you really understand it? Author. Who documented or elicited the requirement? Source. Where did the information about the requirement come from? Ownership. Who's responsible for addressing the requirement? Stability. Is the requirement well-defined or does it seem like it may need to be modified or reviewed? Urgency. Does the requirement need to be addressed right away or is it something that can wait? Priority. How important is the requirement in relation to the entire project? Is it one that needs to be met in order for the project to be successful or is it a nice-to-have feature that could be left out if necessary? State. Is the requirement still being drafted or has it been fully documented and approved? You might find that you don't need all of those attributes, or you might discover others that are really important for your projects. That's fine. The key is that capturing attributes can help you organize and manage your requirements and ensure that your project meets the needs and expectations of your stakeholders.