It is so easy to get caught up in the “craziness” of a project. You have a tight budget, a tight timeline (some might say impossible), and not enough resources. You put your head down and focus on getting the requirements, documenting the requirements and getting them to the IT team so that you can take a breath for just a minute.
But if you take a step back and consider what the valuable requirements are, you may find that some of what you are documenting as requirements is not needed.
Tyner Blain wrote an article explaining what makes a requirement valuable. Try using this philosophy on your next project and see if it helps you focus on what’s really needed in order to meet stakeholder’s expectations.
Writing valuable requirements is important. It doesn’t matter how well your teams execute if they are off building the wrong products / capabilities / features. The right products and capabilities are the ones that have relevant value.
- Valuable requirements solve problems in your market.
- Valuable requirements support your business strategy.
- Valuable requirements solve problems for your users.
- Valuable requirements meet your buyers’ criteria.
- Valuable requirements don’t over-solve the problems.
Click here to continue reading the article…