SPAN has a wealth of experience and expertise in providing onsite/offshore services. We develop a custom-fitted strategy after meticulous evaluation of the nature of the project. This is the first step towards defining processes that ensure compliance of the deliverables within agreed norms. SPAN has proven expertise in gathering and defining user requirements, recommending technology solutions and designing system architecture. A strong tool based approach ensures productivity and quality at every stage.
SPAN follows Iterative model for development of product/applications that needs to be built in a phase wise manner. The features released to end users may get altered as well as new features would get implemented in feature releases based on feedback. Similarly the feedback from each stage would also modify the product features.
Requirement Elaboration Phase
During the Requirement Elaboration Phase, SPAN team will review the current requirements document thoroughly with Client and validate the requirements. In some cases, we may need to jointly expand on the requirements or revise them to make it clear. A face-to-face meeting is needed for this phase.
High Level Design Phase
During the High Level Design Phase, the design aspects of the application will be completed. This includes:
During the Development Phase, SPAN proposes to develop all the features as defined in the approved SRS. The development will be based on the approved requirements from the Requirement Elaboration Phase and will use the design frozen in the High Level Design Phase. This phase also includes low-level design, User Interface, coding, unit test, integration and system testing. SPAN would like to follow shorter development and testing cycles and provide working deliverables as opposed to a single long cycle and a final deliverable. The benefits of this approach are mentioned below.
Final UAT Phase
The Final UAT Phase will commence once all the tasks planned for the Development Phase are completed. During this phase the application will be released and the client will test the application to make sure all the features are working as defined in requirements document. Any issues reported are fixed and any enhancements provided are considered as 'Change Request'.
SPAN offers Agile project methodology for suitable projects wherein the Requirements are not well-defined or evolving continuously. We have extensive experience in using this methodology.
SPAN adapted Agile Scrum as a formalized process in early 2003. Since then most of the projects that are being executed for ISV's falls under either Scrum / RUP's Iterative process methodology.
Key Scrum practices included in SPAN are as follows: