Practical Requirements Management
A Blog - Practical Tips & Articles on Requirements Management. No Highfalutin Theories!
As you know, writing detailed requirements is very valuable – both for traditional (waterfall) projects, and for Agile projects. Please check out my previous post for why detailed requirements are beneficial even for Agile projects.
In this blog post, I’d like to highlight one thing that many people miss when it comes to requirements management.
Wondering what it is? Read on for the answer… [Read more…]
In this quick post, I’d like to define the term “Requirements Management Plan”.
Simply put, “Requirements Management Plan” refers to:
A document (or set of documents) that define how the requirements for a software project will be managed.
Requirement management plan outlines the guidelines for creating requirements documents, types and attributes of requirements to be included in such documents, as well as the processes for change control and requirements traceability.
Here’s some more info about requirements management plans.
In my previous post I discussed different types of software requirements and how they are used. I covered five different types of requirements.
In this post, I will walk you through the different types of requirements document and what they mean.
Before I jump into it, I gotta tell you – there are numerous types of “requirements document” out there, we’re just going to cover the most popular ones in this post! Okay, let us get going… [Read more…]
Subscribe by Email: Get weekly email with fresh posts...
Get this eBook and learn the basics of use cases - plus simple & practical tips for writing effective use cases.
"The Practical Guide to Use Cases"
3) Do not read this blog one sentence per day during your lunch break, while eating a quadruple bypass burger. If you do - by the time you finish this blog, you will be a total fatty and may even die. Again, we're not responsible for it.
