Thread by @bibryam

🔸tldr of 245K words / 640 pages🔸
6 Most Important #Software #Requirements Practices in 6 Tweets 🧵
medium.com/analysts-corne…

#1: Define business objectives & communicates to all stakeholders why they are working on the project.

Without business objectives, you can’t craft a clear product vision or establish the scope of either the entire project or any development increment.

medium.com/analysts-corne…

#2: Understand what users need to do with the product and the goals they want to achieve.

Rather than asking, “What do you want?” or “What do you want the system to do?” ask, “What do you need to do with the system?”

medium.com/analysts-corne…

#3: Prioritize the requirements, you can’t do it all at once.

Your goal is to deliver the maximum business value to your customers at the lowest cost & in the shortest time by guiding the team to work on the requirements in the most appropriate sequence.

medium.com/analysts-corne…

#4: Explore nonfunctional requirements as they contribute heavily to user satisfaction.

Specifying quality attributes lets you build a product that delights its users, beyond merely doing what it’s supposed to.

#5: Peer review the requirements so all the team members & stakeholders know what to do & expect

Requirements & tests are complementary: the former describe how the product should behave; the latter how to tell if it’s exhibiting the correct behaviors.

medium.com/analysts-corne…

#6: Plan for requirements change by accepting the uncertainty of what you’ll have at the end and when you’ll have it will change.

Anticipate requirement changes and establish mechanisms for dealing with them without derailing the team’s commitments.

medium.com/analysts-corne…