Business Requirements
An Agile approach to Business Requirements.
Business requirements define of the business need that a project must meet and how we will measure successful delivery.
Agile, no less than other approaches, needs business requirements. The key differences in Agile are the level these requirements are generated at, when they are gathered in the project lifecycle and the level of customer feedback incorporated after the start of the project.
Timing of requirements
Gathering business requirements can absorb large amounts of time and analytical resources. If circumstances change while the requirements are being gathered or afterwards it can lead to significant wasted effort.
Market dynamics shift, businesses are re-structured, new systems and processes are implemented, new regulations and risk controls become relevant, key personnel leave and customers can change their minds. Because of these changes, the business requirements can move substantially.
Consequently, defining all requirements up-front will lead to either waste due to change or a project that does not deliver the expected business value.
Depth of detail within traditional business requirements.
To avoid waste caused by changing requirements and eventual acceptance by the business, many traditional approaches will extend business requirements to also define functional requirements and detailed elements of scope. The underlying rationale for this approach is that if the business agrees to all of the details up-front, it cannot object to the final delivery.
There are four issues with this approach:
- If the external business context changes the business needs can change rendering the detailed requirements useless
- Spending more time on highly detailed requirements leads to significantly more waste if business needs change
- Even detailed requirements may not create a shared understanding between the business team writing the requirements and the team delivering them. Those writing the requirements may not understand what they are ‘getting’ until they see it
- Time taken to define all requirements significantly delays the start of the project execution and therefore delays speed to market
Customer Feedback
Traditional approaches to creating business requirements restrict customer feedback to the beginning of the project. As noted previously, this is asking the business to provide feedback on a result they have not seen and may not be able conceptualise.
Feedback after delivery is usually considered “scope-creep” and/or may require change requests with additional funding. Although this controls expenditure from a project perspective it simply shifts the costs of non-delivery or additional funding back onto the business.
An Agile approach to Business Requirements.
The Agile approach is to:
This approach means:
1
Development can start sooner
2
The business can directly influence the outcome and value delivered
3
Changes to business needs are expected and can be incorporated with limited wasted effort
Locations
USA
US Headquarters
695 Town Center Dr, Suite 1100
Costa Mesa, CA 92626
+1 424 543 2623
growth_US@adaptovate.com
AUSTRALIA & NEW ZEALAND
Sydney
L12 50 Carrington Street
Sydney NSW 2000
+61 2 7200 2530
Melbourne
Suite 22-125 120 Spencer Street,
Melbourne VIC 3000
+61 2 7200 2530
Canberra
Suite 3, Ground Floor/65 Canberra Ave
Griffith ACT 2603
+61 2 7200 2530
Auckland (Tāmaki Makaurau)
Level 4, ACS House, 3 Ferncroft Street,
Grafton, Auckland 1010
New Zealand
SINGAPORE
20 Collyer Quay, Level 12,
Singapore
+65 98348486
POLAND
ul. Czackiego 15/17
00 -043 Warszawa
+48 505 626 416
CANADA
296 Richmond St. West
Toronto, ON M5V 1X2
Canada
+1 647 631 1205
UK
5th Floor, 167-169 Great Portland Street
London W1W 5PF
+44 20 3603 1662
PHILIPPINES
19th Floor, Two Neo Building
3rd Avenue corner 28th Street
Bonifacio Global City, Taguig City
+65 98348486
ADAPTOVATE is a proud sponsor of the Sydney Roosters - an Australian National Rugby League team
About us
Key Approaches
Industries
Trending Topics
©2022 ADAPTOVATE. All rights reserved