There is an important phase in the Project recovery cycle: Requirements to a Recovery Phase. This phase allows us to validate and assess the original requirements vs. the proposed solution.
To help you understand the sub-phases, I have broken them down. This will allow you to see where the indirect requirements validation approach can be used and what the outputs of managing phases 10, and 11. It is obvious that depending on the size and scope, we need to find a time-efficient solution to complete these tasks.
Get My Scope Management Plan Template
Access the Scope Management Plan Template that I use in my projects.
It can be used for work by being adapted to your needs. It can also help you learn Scope Management.
Get the Template
What is the purpose of indirect requirement validation?
My team was asked to extract the requirements from the project requirements documentation. They then created a log of 850 requirements. This log was divided into three project areas: configuration, customizations, and reporting.
We had to find the best solution for the time and cost-effectiveness of the items. This was also due to the importance of stakeholder engagement.
The point 10.1 was successfully managed using a combination of different techniques.
Requirements review
Validation of indirect requirements using an indirect approach
Let’s look at how the indirect requirements validation could be very effective.
Both technical documentation and functional requirements documentation are available
To help you build your team, there are resources such as technical guys and business analysts
There are many requirements
What does a Requirements log structure look?
The first step in this technique was to create requirements’ logs as shown in the image below. In grey, information from previous requirements gathering. In light blue, assessment and consultancy criteria.
We decided to take the prioritizations already given and integrate them into our standards.
Processes References
The process and sub-processes were then assigned to each requirement. If any highlights had been made by the consulting company, I believe it is essential to evaluate the subprocess assignments.
Below is a table that shows the gap/fit.
Impact on business processes, original scope – see table below
Current requirements status (issues) – see the table belowGroup for questionnaire
You may regroup more than one requirement in one question on the questionnaire/survey, or you can leave each one as a single question. This is a discretionary activity. You can choose the most appropriate group based on any type of questions, priority or sub-process.
How do we select the requirements that are to be converted into questions?
This activity is discretionary and requires an independent approach.
We must exclude those who:
Have a low to medium-low impact upon the project status
Have a low impact on business processes-original scope
What techniques can be used to create questions?
Question (which combines two different requirements)
“How would you manage/improve/change a supplier invoice related to import transaction?”
It’s another powerful question type. It can provide an indirect positive or negatively confirmation of the requirements that have been identified in scope. It can also help you understand the root cause of the requirements.
Question example: This question combines two requirements from different processes.
“Why is it necessary to re-work stock materials consumption to plan and control it?”
I have used to combine different requirements to ask:
“What can you expect from an integrated approval workflow in Purchasing?”