Atlanta-based SPI Identifies Best Opportunities for Outsourcing

We know that outsourcing looks different for every company.

As businesses wonder how to implement offshore IT solutions, SPI provides answers.

Our outsourcing suitability matrix combines historical analytics with industry research to gauge your operational capabilities. Developed in-house by our IT experts, the matrix highlights opportunities for lowered costs and investigates ways to maximize efficiency.

With our state-of-the-art tool, SPI provides not just the best approach, but the best approach for your business. Companies feel our commitment to them, as we dedicate our service and attention to each and every system. 

SPI Methodology Ensures Quality IT Solutions By fusing the most heralded aspects of our business-our teams and our work-Atlanta-based SPI delivers quality IT solutions through its tested and proven methodology. We know that throughout the project life cycle, communication is key and that clearly defined steps and processes achieve results. 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 defines high level project requirements. Once the high level requirements have been set, a process of requirement definition is begun with a requirements document (RD) created for each project requirement. This document describes the requirement and the accepted 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 begin. 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 are stored. QA Assessment of Standards and Procedures The verification of the documents, programs and procedures by the QA Team is recorded in the QA Report (QAR). 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. SPI Works with Numerous Development Models At SPI, we are familiar with various software development lifecycle models and their applications. The software development models that we successfully utilize include : Waterfall Model Prototyping Model Rapid Application Development Model Spiral Model When the project can be divided into a sequence of well-defined phases, SPI chooses the Waterfall Model or the Linear Sequential Model. The actual phases - their length and content - depend on the project and are usually driven by customer needs. Typically, the phases in a development project are : Requirements analysis Design Coding Testing Deployment The Waterfall Model The Waterfall Model is the simplest model and is recommended on projects for customers new to offshore relationships. Prototyping Model When the construction of requirements is a major hurdle and the knowledge exists with a small group of customer stakeholders, the Prototyping Model may be followed. A prototype is built to quickly demonstrate to customer stakeholders what the product would look like. Only minimal functionality is provided in the prototype built in this manner. The prototype is also usually discarded after requirements have been approved by the customer. Rapid Application Development Model We sometimes combine the features of the Prototyping Model and the Waterfall Model to execute projects based on the Rapid Application Development (RAD) Model. In consultation with the customer we agree on the decomposition of the final product into manageable units that can be developed in short periods of time, for example, in 100-day cycles. The Spiral Model The Spiral Model is a popular method through which we build software products. The concept revolves around adding in different degrees of functionality with each additional spiral (level). Each level indicates the stage of evolution of the final product. The Spiral Model is a realistic way to develop software and mirrors natural thinking. However, to ensure success, levels and phases, as well as goals and objectives, have to be carefully defined when starting the project. http://www.spi.com/ourapproach_methodology.html