This service allows us to collect information on “work-to-be-done”, “needs” and “opportunities” to whom, by means of our service, an answer will be given to the client, the users and the system operators. We aim to ensure that the work done will always be in the right direction with respect to the needs of those who later have to “consume” the services acquired. The contents produced during the customer profiling phase remain the strict property of the buyer. We’ll use the collected data just for ensuring the delivery of the value required, also because what is collected in this context is subject to a well-defined period that may not even cover the entire duration of the project. The activity does not fit in our marketing activities. We consider this part of our work crucial, we believe it essential to provisioning a service of adequate value; project ally profiling is offered to subscribers of one or more services as a non-billable element
User ProfilingEssential for a broad understanding of real needs of the Customers, The users and the System operators, this phase investigates on the real needs in terms of things to do, open aspects that would need to be mitigated (pains), expectations and changes that would improve their working experience (gains)
Value mapThis activity expresses, beyond the requirements, how, with respect to user profiling, the whole project will produce value for the customer. This kind of analysis doesn’t consider the detail of requirents. It rather starts with a general statement of what is required to do, what problems will be solved by the new product, and then considers the added value.
All these three aspects and subsequently a comparision to the users and customers profiles, and for each single element is found a correspondence between “problem solved”/” pains”, “added value”/” gains” and “general statement”/”activities” .
The objective is to enlight what aspects offered will determine the actual perceived value, and to clarify the real goals of the activities, beyond any technical requirement
Business ModelThis activity focuses all the information related to the operation of the “machine”. The intent is to highlight the entire life cycle of the request, in order to highlight strengths and possible attention points.
Detection of the current operating parameters (processes, time, cost)
The offer core refers to the benefit delivery, but without a adequate knowledge of the initial measurements of what has to be improved it would be difficult to talk about improvements. This document is the first to enter into the merits, and is used to collect the processes currently used to cover the requirement under consideration and to detect, for each activity, the operating parameters, in terms of cost, time, and global impacts on business productivity.
The document is important because it will allow you to define a starting point for estimating the benefits and consequent measures to achieve the objectives (“As is” analysis)
Document of the desired quality and expectations and related evaluation criteriaWith this report we deal with the customer’s and user’s quality expectation and relevant tolerance percentages.
These contents will be used to determine when the quality goal will be reached and in the face of which aspects will be evaluated the result. The content will drive the initial validation planning, and at validation phase, will help to understand when the quality management activity will be sure for an hand-off
Architectural impact ReportIf required, at this stage you will trace any architectural impacts of the project (addition or removal machines, network devices, databases), insights on management in the operation environment.
This report will help the estimates of the overall business impact and delivers an early warning about the complexity that will be managed
Requirement analysisThis activity consist of the collection of all the requirements both functional and non-functional. Requirements analysis consist by first of a requirements classification, identifying repetitions, correlations and dependencies. This document states for each requirement inclusions and exclusions from the scope of the project. The requirements analysis aims to point out the business requests, insulate all the single points and explorate dependencies and to show priority, urgency, importance and / or impact from a business point of view. The requirement analisys doesn’t propose any solution, because of the solutions are to be processed by the Business analysis phase
Validation plansThe requirements analysis feeds the Validation Planning, because every single element included in the project scope will be subject to specific verifies, to state that there is an implementation in front of it and to state the match between product and requirement. Another important correspondence processed in this phase is referred to matching the quality expectations and with the users profiling and the value map, to enable the project to deliver quality and value as much as it is possible. For each requirement, there will be one or more test case, that in this phase will be more or less a heading and a description. Complete test cases are defined on quality activities. The validation plan starts by the requirements analysis because the validation should be independent of implementation details
The “Demand management” service offers the possibility to start a project on the right foot as soon as it’s possible. Before delving into traditional requirements management, Demand Management deals with all the boundary aspects, which are usually decisive for the success of a project. In essence, it is proposed a scheme that allows you to have a clear vision in advance of what is the value provided. We don’t consider the value in absolute terms, but it is strictly determined and compared to actual activities, problems and new opportunities for the users and the structure in which they operate. The value offered is ensuring that there will be an answer to each business requirement that will provide the change
This activity proceeds on the basis of feasibility studies and the requirements analysis, which should at this point be already approved and validated. The business analysis for each requirement is intended to define how the corresponding required functionality is going to be realized. In this phase we, of course, work at the deepest detail possible in terms of functionality description. The business analysis will drive the design, so no single aspect has to be left undefined. Beyond the functional aspects get into this phase also the non-functional requirement as well as architectural aspects sensible to the business analysis phase
Requirement Documentation gathering
This activity is an essential element to take the work in charge. The activity consists in the study of the requirements in order to assess the actual workability. The result is always a document that shows the result of this analysis. This service component is to ensure the customers and stakeholders on the feasibility of the entire package of business analysis, and is not necessary when preceded by a formal analysis of the requirements conducted according to the methodology described in the “demand management” package, because in this case it is considered self-validated
The concept of “Best Practice” is a naive simplification because the concept of “best” simply does not exist in the real world.
Our proposal characterizes itself for the deepening on the objective characteristics of the client. Much more than offering of abstract “best practices”. We focus on a concrete selection of methods that will fit to the customer’s context within which they are we are going to apply; in short, more “Right Practices” rather than best practices.
The activity consists in seeking referencies in industrial practices, academic and regulations applicable to the issues addressed in the project on the following aspects:
– Ergonomics / User Experience
The purpose to select proven practices that fit in the customer’s context, to ensure that the value of what is produced on the basis of what has been provided by the activity of analysis will fully satisfy the needs. The results of the activity are shared in advance and subject to approval by the client, which in this way can have a precise idea and very advanced compared to what will be the end result of the process. Usually defining a basis of recommendations can be applied simultaneously to more than one projects under the package of Business Analysis, and it becomes at the end a customer’s asset for the topics covered
This activity is the heart of the business analysis package, the functional analysis report system offers a solution for each single requirement, according to the selected practices and gives a detailed description of systems, components, the aspects of man/machine and machine/machine interaction, in order to define the system of rules and references on the basis of which the design must be carried out.
The activity, is likely to be subect to a revision process and possible updating, any time should happen to be requested a revision. That ensures that the required and expected value is continuously aligned with the demand and business requests
The document architecture shows what are the architectural partitions planned for the system designed and defines characteristics, responsibilities, interfaces and management aspects in operation. If the project involves an impact on information infrastructures, this document is issued and is added to the project documentation on infrastructure
The design document defines the application structure of the proposed solution and the details for each element in the functional analysis, with a clear indication of both the functional analysis and requirement concerned.
If the functional analysis describes “what” is required and defines only an high-level definition, the design document deeply details the way the work is done.
The design document is the primary reference for the development team, and just like every other technical artifact may be subject to revisions, within specific case studies as:
– Change (Evolution, withdrawal or addition of requirements)
– Realign requests from the development team
– Correcting “design” problems that generated faults raised during verifications or tests
The Progress Audit ensures a double guarantee: on one hand the development team receives clarifications on the project documentation, designer intentions and objectives expressed if the design document. On the other hand, the audit oversees the execution and that ensures the customer on a correct execution about what stated in design.
The Progress Audit does not replace the Project Management audit nor any of the Team Leading functions, it instead joins these roles to facilitate the work
DESIGN & SPECIFICATION
The Design & Specification package is the drafting of the instructions for those who produce materially the software product. The design document is normally prepared in English, and uses the UML modeling language, which is a well known industry standard, shared for all levels of the software lifecycle
Validation Planning deals with defining the detailed plan for the system verification. When available, it starts from the the test plan document produced by the process of Demand Management, otherwise it proceeds, however, starting from requirements, analysis and (if necessary) by the design. It delves into the details with the description of test cases. The purpose of this service is to provide the validation team the list of the tests to perform, and for each test case a test sequence of actions to be performed to verify and ensure that the requirements are met and that, compared to what was previously analyzed and designed, there are anomalies
This service aims to warrant the correspondence of the test platforms respect to the production environment.
For a genuine test, the test platforms should be congruent to the production.
The aspects under examination by this service are:
– Hardware components
– file system structure
– network connections
– memory size
– Operating systems type and version
– run time environmet (java, .net etc. …)
This service is especially important when the test activities refer to more systems integrated, when verification processes affected across all the systems involved.
This service guarantees the team of integration testing and the customer that the test will report worthy results, moreover this service can also provide the necessary support to the preparation of the validation chains
Functional Test Plan
The Functional Test planning aims to ensure that the desired behaviors described in the requirement and analysis documents have adequate correspondence as a product. This activity explores every detail of the model of interaction and functional behavior.
The value of the functional test plans doesn’t stop whith the end of tests, because it will be used over and over to ensure the “non-regression” for each new release of the system under verification, to ensure that the functionalities not impacted by the last change will still work as desired
System integration test plan
The System Integration test plan defines how to validate the business processes that flow through realizes the validation of the system, especially from the viewpoint of processes, across all collaborating systems.
Integration testing requires that in test environment every system that will participate in the process under verification conditions, it is expected a particular service to check the availability of replicas of all systems uncooperative
User Acceptance Test Plan
Acceptance Test plan: the acceptance test is a strict verification of the requirements related to new work.
The planning of the test focuses therefore substantially the requirent artifacts that have been shared.
This document is usually defined by the users, even though they sometimes need a some support for a formal definition. This service is designed for that reason
Test Execution Support
The service offers an oveseeing for the testing activities and support for the people involved in the testing activity
Progress Reporting and Hand Off Document
Daily collection of data and reporting of progress in terms of:
– The percentage of planned tests coverage
– Identified Defects
– Fixed Defects
– Notes on critical issues and forecasts to end
– Production of the formal handoff document at the end of the activity
The project initiation service involves the collection of the requirement and its processing in order to determine whether the project (at this stage not yet active) deserves to be continued or not. In this activity, the project manager works together with a business representative, which is the person who is responsible all strategic decisions. The result of this activity is providing enough rationales to make the decision about the authorization (or denial) to proceed with the project This activity is the first stage of running a project, and that depends on the authorization obtained in the project initiation phase. In every operational phase, the products to build are split into stand-alone working packages, which will be entrusted to the leader of the team who will then produce them. This stage contains the work of custody and delegation, detection (and possibly anticipation) of potential problems and management of the related escalation process so that they can be managed at the appropriate levels. The end phase activities aim to check the execution performances and to compare whether the results are within the expected performance targets and relevant agreed deviation: on that basis the products are accepted. The subsequent activity is the preparation of the documentation to support the claim to perform the next processing step or the authorization to the conclusion of the project At the project conclusion, all operational and “management” products are reviewed and revised. Once this phase there’s the request for project closure and following the authorization there’s the decommissioning of the teams and start the final stages of product acceptance and closing the handover documents , which will then be delivered together with the product Managing a project means offering guarantees: – Ensure the customer that the project is worth for execution forward and that can deliver value in relation for the budget and the resources used Beyond these guarantees, it is required that the project can be assessed positively in terms of time, cost, scope, quality content, risks, and benefits. The project management service proposed uses an approach based on the “PRINCE2” (Projects IN Controlled Environment) methodology, which, although does not guarantee success (no project management method could ever warrant a success to the project), certainly enables a very timely detection of problems and a correct addressing of the issues.
It defines the aspects of the project in terms product definition, workflows, operational planning, setting the objectives and methods of quality assessment, definition of roles and any aspect contributing to highlight the strength necessary organizational project organization.
The result of this activity will be a document that will indicate what will produce the project, as it will produce and those who produce.
This stage concludes with a formal authorization to the execution of the next operational stage, whose planning is part of the project opening activities
Operational Phases Management
– Ensure that users be able to obtain the desired benefits, with the right level of quality
– Ensure the suppliers that their job is aligned the the actual customer needs
In the various processes that take place in an PRINCE2 project, there are approvals and authorizations authorization steps, aiming to ensure the best alignment between customer and project management. The goal of the project manager is managing the “day to day” aspects of the project, at various stages of the life cycle. The project is subdivided into “stages” performed on the basis of explicit authorization avoids planning efforts in the medium to long term, whose precision lower with the distance in the time. The setting for products and services to ensure the maintenance of concreteness
The project initiation service involves the collection of the requirement and its processing in order to determine whether the project (at this stage not yet active) deserves to be continued or not. In this activity, the project manager works together with a business representative, which is the person who is responsible all strategic decisions. The result of this activity is providing enough rationales to make the decision about the authorization (or denial) to proceed with the project
This activity is the first stage of running a project, and that depends on the authorization obtained in the project initiation phase.
In every operational phase, the products to build are split into stand-alone working packages, which will be entrusted to the leader of the team who will then produce them. This stage contains the work of custody and delegation, detection (and possibly anticipation) of potential problems and management of the related escalation process so that they can be managed at the appropriate levels. The end phase activities aim to check the execution performances and to compare whether the results are within the expected performance targets and relevant agreed deviation: on that basis the products are accepted. The subsequent activity is the preparation of the documentation to support the claim to perform the next processing step or the authorization to the conclusion of the project
At the project conclusion, all operational and “management” products are reviewed and revised. Once this phase there’s the request for project closure and following the authorization there’s the decommissioning of the teams and start the final stages of product acceptance and closing the handover documents , which will then be delivered together with the product
Managing a project means offering guarantees:
– Ensure the customer that the project is worth for execution forward and that can deliver value in relation for the budget and the resources used
Beyond these guarantees, it is required that the project can be assessed positively in terms of time, cost, scope, quality content, risks, and benefits. The project management service proposed uses an approach based on the “PRINCE2” (Projects IN Controlled Environment) methodology, which, although does not guarantee success (no project management method could ever warrant a success to the project), certainly enables a very timely detection of problems and a correct addressing of the issues.
IT STRATEGY SUPPORT
In the IT Strategy Support service we support the customer in organizing processes and practices necessary to the government of its own ICT.
the covered processes are:
The budget management helps to track the total budgets in charge and to subdivide then into initiative budgets.
The portfolio management enables a tracking for the business requests, and to enrich them with relevant information like associated total budgets, reasons, priority, budget estimation, requirer.
The Portfolio Management, records the the business requests and the associated parameters, and allows an objective evaluation and above all comparison with the other requests, from which can arise the decision on which requests are worth to be brought forward.
The promoted request pass to the demand management process and become “initiatives”, which assesses and detailed aspects of economic impact in terms of capital costs and operating costs, and it defines a multi-year cash flow. Moreover, the demand process deepens the detail of the projects to be opened, and feeds the program management
The detail reached at this point allows you to decide what to start on a priority to the operational phase, then open the appropriate projects.
The various projects feed the accounting system related to governance, allow to track their progress and promptly to take exit opportunities for projects that are closing or intervention needs for projects that are having difficulty.
The government ICT company allows you to have a clear view continuously updated on the costs incurred and the value of the product, and can become an important tool for management