SPI excels at executing complex multi-stakeholder multi-location projects because of its sound, tool- supported methodology called the SPI Method. The SPI Method is flexible enough to handle any type of project, including new development projects and maintenance or support projects. The process allows customization of most aspects of a project, making it applicable to any situation. The SPI Method is robustly supported by SPI's enterprise project management tool - spiProject^® at all phases, making project progress visible to all stakeholders.

PROJECT INITIATION
The SPI Method begins with Project Initiation, where the project objectives, stakeholders, and project participants are identified. During this phase, project-specific instructions are established and project-related document templates are customized. This step is concluded by a project initiation meeting, in which all project participants are present, where these documents are discussed along with the project objectives.

REQUIREMENTS DEFINITION
In this phase, a system requirement document (SRD) is created, which describes the architecture and in which any high level project requirements are defined. Once the high level requirements have been set, an iterative process of requirement definition is begun with a requirements document (RD) created for each project requirement. This document describes the requirement and all acceptance criteria for the requirement. A change requirement document (CRD) is provided to alter requirements as necessary. As each RD or CRD is created, it is formally presented to the next participant, the designer.

DETAIL DESIGN
Using the RD and SRD as input, detail design documents (DDs) are created. These documents, at the level of pseudo code, give detailed instructions to the programmer for creating each step of the program. Along with the DD, detailed test plan documents are created. These documents are then formally presented to the RD creator or the client.

CONSTRUCTION
When the design is complete, construction and unit testing are begun. Using the DD as input, the developer codes and unit tests each module. The test results are recorded in spiProject^® for later review. As each segment of the system is completed, system tests are conducted and their results stored.

QA CHECK OF STANDARDS AND PROCEDURES
The verification of the documents, programs and procedures by the QA Team is recorded in the QA Report (QAR). Each project has its own QAR. The verification results with respect to the records (RD/DD/TD etc) are recorded in spiProject^®.

RELEASE
The final stage of the methodology is the release document where any notes pertinent to the software are stored.

SUMMARY
The SPI Method ensures robust and visible control of any project. Following the methodology assures that projects are completed on time and within budget.

KNOWLEDGE MANAGEMENT
An important factor in the success of any project or initiative is the ability of the team to learn from past experiences. SPI provides one unified channel – spiProject^® – that consolidates the knowledge the company has acquired during project execution and later facilitates search on this knowledge base... More>>

Top