Analyst’s corner
Published in

Analyst’s corner

Requirements Review Challenges

A man holding a magnifying glass over an ancient book written in Latin.
Image from Pexels

If someone said you could only perform a single quality practice on a software project, what would you choose? I’d pick peer reviews of requirements. I believe this the highest-leverage software quality technique we have available today.

In a peer review, someone other than the author of a work product examines the product for quality problems and improvement opportunities. Reviewing requirements is a powerful…

--

--

--

All aspects of organisational analysis: business analysis | enterprise architecture | quality

Recommended from Medium

CI vs CD vs CD — What Are The Key Differences?

CI vs CD

Should I go to the Cloud?

10 Requirements Traps to Avoid

A gold-colored bear trap.

Docker as an Integrated Development Environment

Good Engineer/Bad Engineer

Cost-efficient Batch Computing? Tell Me More!

Let’s Do DevOps: Auto-Approve Safe Terraform Apply in Azure DevOps CI/CD

Clouds, containers & microservices: infra and architecture from ~100 DevOps/SRE surveys

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Karl Wiegers

Karl Wiegers

PhD in organic chemistry. Author of 13 books, mostly on software. Guitars, wine, and military history fill the voids. karlwiegers.com and processimpact.com

More from Medium

Keeping the Project Scope in Focus

A drawing That shows business requirements feeding into user requirements and then into functional requirements. Change requests come in at the user requirements or functional requirements level, leading to negotiating a scope increase at the business requirements level.

Scrum: The lifecycle of a Sprint

6/28 #ProductDiaries: Project Brainstorm

Avoiding Prescriptive Requirements