Search
 Why Agiline

 


Phases
The Conceptualize Phase
The critical first step to any of Agiline´s projects is to understand the client´s business. In this phase, we facilitate meetings and workshops with our clients to clearly understand the immediate and long-term requirements and goals.
Agiline’s Conceptualize phase usually lasts for a short duration before formally starting any initiative with a client. The Conceptualize phase is usually done onsite. Consistent quality solutions delivered by using a clear understanding of our client´s goals to help them meet their long-term business objectives.
Examples of deliverables from the Conceptualize Phase:
  • High level project plan for moving forward
  • Scope Document for the project
  • Project team organization and communication/escalation procedures
The Design Phase
The design phase answers What ´s and Why´s of the project. By drilling down on the requirements, this phase will define the functional, technical and creative specifications. A well-documented design specification is taken to the next phase for execution
Agiline’s design phase may consist of parallel tracks for business design, technology design, vendor research etc depending on the size of the project.

Examples of possible deliverables from the Design Phase:
  • Scope Document for Implementation
  • Implementation Plan with Milestones and Checkpoints
  • Non Functional (or partly functional) Prototype
  • Documentation and Coding Standards
  • Logical Architecture
  • Data Flow Diagram
  • Object Model (UML)
  • Data Model (E-R diagram for backend)
  • Vendor Evaluations
  • Software Component Recommendations
  • Data Exchange Interfaces
  • Individual Module Design Documents
  • Development specifications for each module
Execute Phase
The Execute phase involves building and testing the final solution based on the design specifications.

This phase of the project is usually done offshore. If any Agiline development resources were onsite for the design phase, they typically return to our development center. For large projects, an onsite coordinator is used to maintain a constant client presence.

The solution is continuously tested through development and integration using development checkpoints and exit criteria at every step. Use case scenarios and module test scripts are created to enable various forms of testing. The application is first released in its Beta form for a select group of users before the final rollout. Agiline will monitor the application for a period of time after rollout, to ensure expected performance.

The steps, processes and deliverables used in the Execute phase are discussed in detail in Exhibit

Execution is internally broken up into granular tasks such as development, Integration Testing, Alpha/Beta/Load Testing and Live Processes.

Examples of possible deliverables from the Execute Phase:
  • Functional system as per specifications
  • Documented Source Code
  • Results from various testing stages
  • Performance Testing Benchmarks
  • Site / Project Transition Manual
  • Site / Project Troubleshooting Manual
Support Phase
In the Support phase, the product is live. Here we monitor and analyze the solution against the pre-defined success factors. We also incorporate enhancements and ongoing changes to the product during this phase.

Typically, Agiline support engineers will be on standby during the support phase to ensure that all issues are resolved promptly. Any issues that occur are prioritized according to pre-arranged guidelines with the clients. Agiline guarantees issue identification within a given time depending upon the priority of the issue.

The Support phase is used to ease the transition of the product over to the client engineers.
Agiline
Brochures download
 

 

Copyright © 2012 Agiline  •  All Rights Reserved.