Most of our development process has been on Agile in line with customer's requirement on the adoption of Agile Methodology as part of our Project Management offerings. We believe agile development is based on values of simplicity, communication and feedback and bringing in an ‘agile’ approach to development will help bring transparency and quick “GoTo” market approach through iterative application releases
Our proposed development would be on an incremental basis and iterative approach, leading to iterative cycles with multiple releases and small teams with focus, clarity and cohesion. This would enable the project teams to assess where they are in each iterative cycle and plan the activities forward and take timely corrective actions. The use of planning and tracking tools would decide what should be done next and to predict when the project will be done. Focused on customer's business value, the teams would produce applications in a series of small fully integrated releases that pass all the tests as required by the customer.
The diagram below shows our Approach to Software Development model that would be implemented for customer's requirement
The Requirements gathering team plays a key role in knowledge acquisition and requirements definition and transmittal of the knowledge transfer and requirements documents to the AKRA TECH team.
Step 1 – Usability / Functional Review
The application release and notes received from the Requirements gathering team are reviewed interactively with the customer at identified milestones. In the initial stages of the project, Use Case Storyboards and application prototypes constitute the release from the project team. Application development is taken as the continuation of the prototypes.
Step 2 – Delta Identification
This is the documentation of the interactive process noted in Step 1. All changes and enhancements to the release are detailed in a checklist.
Step 3 –Development
The Development team plans work based on release documentation.
Step 4 – Transmittal
The application code, notes and delta documentation (work to be done) are checked into the configuration management system. The application is kept integrated at all times and clean compile of code is ensured before the code is checked in.
Step 5 – Assignment
The AKRA TECH Project Manager reviews the Transmittal from the team on a daily basis and plans the work to be done by the team.
Step 6 – Clarification
Direct communication between the customer's Project lead and the project team occurs to clarify any needed items before an estimate is sent.
Step 7 – Estimates
Estimates are compared to the original baseline to monitor the general project schedule and correct the schedule as needed. Estimates include dates for § Code completion§ Quality assurance
Step 8 – Project Schedule Update
This step allows features to be added or deleted according to current progress. Each system component is individually tracked for finer management; solutions for problems may include onsite development, additional offshore resources, or feature deletion. Alternately, better than expected progress may allow deferred work to be completed.
Step 9 – Release
The application is kept integrated at all times and clean compilation of code is ensured before the code is checked in. A release is prepared on a daily basis. Release notes with instructions to the team are also prepared and checked into the configuration management system.
AKRA TECH's experience in Agile Lifecycle Management (ALM) has helped us provide continuous improvement in process development and management of applications in the past. Through our ALM practices, we have helped provide our customers