Hello,
I am the lead for a team of SAs. We've been tasked with the development of baseline requirements for a complex system that has already been implemented. I am struggling with how to best develop these requirements. Do I guide the team to develop functional requirements or go with a more use case based requirements set? If this were a standard project where we would have planned accordingly, I would have planend to develop the functional requirements. This is just different and I'm having a hard time with it.
Any suggestions?
Hi Jason
So you've got a cart/horse project where you have to deconstruct the requirements from the system and information from the implementation.
Broadly I'd say you have two streams to document:
1. system function
2. business value
1 is what is the system capable of. You probably already have some of that from the dev team or the vendor and if you're lucky some architectural diagrams
2 is what the business wanted from the system - so you need to go back to the stakeholders/and project doco and find out:
- what were the business pain points
- what was the business value of the solution
- what was the minimum viable product (must haves)
- how many of those got implemented
At that point you can write functional requirements. But to be honest its probably better to do fit/gap analysis. If the system isn't fit for purpose - better find out early. The write requirements to bridge the gap and plan the workrounds, next release or next upgrade. Requirements are for UAT - once the system has been delivered not much point being an archeologist. My 2c worth.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: