Are BRD and FRD documents required for non-systems/non-IT projects? We are involved in services migration project moving managed website hosting services from a fully-managed external vendor to in-house so we can manage these ourselves. Because this is a transition project which does not require the development or building of any IT systems or infrastructure (we already have the servers to support the website), it can be compared to a construction or engineering project where BRD and FRD documents don’t usually exist.
Usually, the requirements are based on Business Objectives and then functional and non-functional requirements are based on requirements. If this is a transition project which is moving a service from Provider A (external) to Provider B (in-house), is a BRD really required?
The primary business objective is to transition the managed services externally to in-house. If we look at the actual tasks and the work pieces involved in the project to successfully achieve the business objective, a few of these at a very high-level include:
- Documentation: Identifying and transferring support documentation.
- HR: Employing new staff or employing existing vendor staff to manage the hosting serviced internally.
- Processes: Obtaining from the vendor and introducing new processes to provide the same managed service.
The primary constraints, or non-functional requirements if this were a systems/IT project, would be:
- No loss in service delivery during transition.
- Adhering to company processes and SLAs.
Are BRD and FRD documents required, or would a series of plans (implementation plan, transition plan, continuity plan, SLA, etc.) be sufficient?
Update: thank you so much for the replies and comments so far. I am calling for more viewpoints and comments that can contribute, as such projects are not uncommon but there is scarce information online to refer to.