This basic tutorial describes in 5 steps how our Business Analysts use Leverforce SAAS during the three phases of a project engagement: Business Analysis (Steps 1, 2, and 3) Project initiation (Step 4) and Commissioning (Step 5).
Step 1 Setting up a new project and business analysis
BA sets up in Leverforce the client organization or internal business unit requesting the change in IT services.
This is done through the standard CRM modules (Organization, Contacts, Projects). The following video shows a basic project set-up:
Step 2 Modelling business processes
While conducting interviews to gather business concerns and user requirements, the analyst narrows down a list of use cases in which the business will utilize the solution.
The BA also analyses all activities associated to each use case.
The BA enters the use cases and activities that are relevant to the analysis into the Leverforce modules.To ease the entry of records, the BA is able to import the use cases and activities from excel/csv files.
Even simpler, and a more complete solution, the BA can use a UML modelling tool such as Modelio or EA Sparx to model use cases and activity diagrams. Analyst can then import all elements in the model into the Leverforce database using the import XMI feature.
Below are two screenshots and a video showing how to import models using the open source Modelio modeler:
Video showing UML modeling and XMI import from Modelio to Leverforce:
For a detailed tutorial on how to set up a Modelio model to import UML elements to leverforce, view this link..
Step 3 Defining user requirements
The BA registers all business concerns as children of a specific activity. A concern defines what the client, or the corporate sponsor, seeks to obtain for the business from the IT changes requested. It expresses what the business needs from an activity in order to mitigate a risk or to take advantage of an opportunity.
Next the BA registers all user requirements as children of concerns. A user requirement describes a behavior or condition needed from an IT service in order to satisfy a concern.
We recommend stating a short description in infinitive and a longer one detailing the behavior or condition required. It should be possible to articulate a user requirement as consequence of a business concern by following this formula:
The user needs (state user requirement here) so that the business is able to (state business concern here)
Here is a video demo showing the Leverforce interface in the activity, concern, and user requirement modules:
Step 4 Analyzing gaps and validating statement of work
Once the business has validated all user requirements the BA engages solution experts to help them define and validate a design that satisfies all gaps in the solution. A gap is the initial proposal from an IT provider. It explains what is going to be built or changed in an IT service to ensure that the behavior or condition requested by the business is available to the user.
The BA records the gaps in Leverforce. We recommend stating a short description in infinitive and a longer one detailing what will be built or changed in the IT service.
With the list of validated gaps the BA engages the business stakeholders and sponsors to finalize a Statement of work. A Statement of work is the final proposal agreed upon by the user and the IT provider. It is simply an additional iteration on the gap, explaining what is going to be built or changed in an IT service to ensure that the behavior or condition requested is available to the user.
The Statement of Work incorporates final changes and additional specifications validated as the scope of work is closed by the business and by IT providers.
Step 5 Testing user acceptance
BA decomposes requirements in the Statement of Work into Product Increments, following the priorities established by the product owner during delivery. Each product increment is then used to organize user acceptance criteria for the sprint (ready stories, rules, specifications, and UAT scripts).
The following video shows how the BA uses each product increment to organize all acceptance criteria required to satisfy an sprint: