Why are we working on this project?

Asking these nine questions when exploring business requirements helps focus all stakeholders toward a common objective.

Karl Wiegers
Analyst’s corner

--

Graphic of a tree showing various business elements: goals, ideas, sales, team, etc. that lead to success.
Image by Gerd Altmann from Pixabay

Business requirements sit at the top of several three-level models of software requirements information (Wiegers and Beatty 2013, IIBA 2015). Business requirements include the information that guides creating a solution to achieve specific business results. They answer the question, “Why are we undertaking this project?” We explore business requirements to help align all project stakeholders toward the desired outcomes. Business requirements include statements of the business opportunities being created or exploited, objectives, success metrics, vision statement, and scope definitions.

Business requirements could originate from a senior manager who understands the problem, a primary customer who recognizes a need, or a product visionary who sees a market opportunity. Such people might already have established a business case for the effort. They might find it valuable to work with a BA to craft a richer set of business requirements.

The project manager (PM) or product owner (PO) has a strong interest in determining the business requirements. Perhaps the first question the PM or PO and business analyst (BA) must assess for any proposed…

--

--

Karl Wiegers
Analyst’s corner

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