Analysis
WE FOCUS ON YOUR NEEDS
WHY CARRY OUT ANALYSIS?
Though the benefits may seem obvious, the reality is most companies do not fully appreciate how their businesses can be helped by analysis and the improvements that can arise as a result.
Individual projects may differ in the level of analysis required, let’s review the typical eight-step process below:
STEP 1 – ORIENTATION
Sometimes client projects are already underway, at other times there are vague notions about what the project should be or why it should exist.
Our analysts* take time to get oriented to ensure we are not only moving quickly but also able to be effective and confident contributors, the analyst undertakes the following tasks:
* At IDC the analyst and product manager roles are interchangeable and undertaken by the same assigned IDC team member.
STEP 2 – OBJECTIVES
The quickest path to a successful project is to achieve client’s agreement on high-level needs early.
The analyst undertakes the following tasks:
STEP 3 – SCOPE
A clear and complete statement of scope helps the project team to envision implementation of the client ‘needs’ in tangible ways.
Typically the scope is defined collaboratively by the assigned analyst and scrum master (aka the project manager) and consists of:
STEP 4 – ELICIT
The gathering of information necessary to understand what the client requires of specific features or process change.
This may include the following methods:
STEP 5 – ANALYSIS
The wishlist is reviewed and probed further until we have are completely clear, and is undertaken in form of:
STEP 6 – DOCUMENTATION
This is when all the gathered information is documented in the following form (as appropriate):
STEP 7 – COMMUNICATION
The requirements are presented to the client’s stakeholders and key users for a final sign-off.
STEP 8 – VALIDATE
To meet the business objectives, the analyst continues to support tasks during the entire technical implementation cycle, by ensuring: