Defining Requirements

So, what are these requirements?

Requirements are a set of prioritized needs from all the involved stakeholders that form the base for the functionalities or features to be included as a part of the solution.

Where do these requirements come from?

Who are stakeholders?

  • Executive Sponsor — Mostly concerned about funding of the project and high-level information
  • Product Manager — Make important decisions for the project and review & approve requirements
  • Project Manager — Prepares project plan, resource allocation plan, manages the execution of the project and works very closely with the BA (Business Analyst
  • Subject Matter Experts — Assists in defining project scope, works with the BA to define business rules, processes and user interface

How stakeholders help with requirements?

How are requirements identified?

  • Identify stakeholders
  • Requirements Elicitation — capture stakeholder requirements through various techniques such as interviews, questionnaire, joint group discussions, prototypes or use cases
  • Identify requirement categories — categorize all the gathered requirements into functional, non-functional, business, technical or transitional requirements
  • Analyze requirements — analyze the requirements whether they are clear, complete, unambiguous, consistent and testable
  • Requirements documentation — requirements are documented in various forms such as Business Requirements Document (BRD) to describe business requirements, Software Requirements Specification (SRS) to describe functional and non-functional requirements, Use cases and User stories (in agile context)

Why are requirements important?

  • Success in 68% of technology projects is “improbable.” Poor requirements analysis causes many of these failures, meaning projects are doomed right from the start
  • Companies pay a premium of as much as 60% on time and budget when they use poor requirements practices on their project
  • Over 41% of the IT development budget for software, staff and external professional services will be consumed by poor requirements at the average company using average analysts versus the optimal organization
  • They are used as inputs into the design stages of product development
  • They are important input for verification process for the product developed
  • They represent what functionalities are necessary for the product

Excellent requirements leave no room for interpretation, confusion or omission of critical details and is easily understandable by everyone involved in the project.




Management Consultant. I write at, with a vision to accelerate personal growth. Follow me @theblogrelay. Love food, travel & people

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Build Named Entity Training Dataset for NER Task (Part 1)

Error Handling in Akka Actor (with Future)

My March Recommendations for Flutter Packages

SASS for CSS: Advance your frontend skills with CSS preprocessor

When Success is an Exception

Responsive Web Design — device resolution and viewport width.

Loading Assets in Phaser 3

On Code Reviews

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
Surbhi Mahnot

Surbhi Mahnot

Management Consultant. I write at, with a vision to accelerate personal growth. Follow me @theblogrelay. Love food, travel & people

More from Medium

The Usage of Scrum to Continuously Improve your Product

Time Estimation: Costing

A Brief Explanation of Scrum

Why do software specifications end up in a bad state, and how can business analysts save them?