Agile approach to Project Management

Our Proposal is based on our past experiences and our standard engagement model for delivery.

Our proposed approach.

Our approach is based on our past experiences and our standard engagement model for delivery. We will follow the industry standard Agile methodology to align at the micro level to Identify issues. manage risk and assure customer satisfaction. We will evaluate and adapt the Extreme Programming (XP) • Agile Methodology approach in our development cycle. Through this methodology of software development, we will follow an incremental, iterative process based on values of simplicity. communication. feedback and an ‘agile’ approach to development. 

Approach to Software Development with XP Methodology

Al the Beginning – Initial specifications

 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 offshore team.

Step 1 – Usability/ Functional Review

Al the Beginning – Initial specifications 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 offshore team. Step 1 – Usability/ Functional Review The application release and rates received from the Requirements gathering team are reviewed interactively with the customer al identified milestones.. In the initial stages of the pales. Use Case Storyboards and application prototypes constitute the release tram project team. Application development is taken as the continuation of Mew prototypes.

Step 2- Delta Identification

This is the documentation ca the into-active process nosed in Step 1. All changers and enhancements a 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) is checked into the configuration management system. The application is kept integrated et all limes and clean compile or code is ensured before code is checked In.

Step 5- Assignment

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 Project Lead and the team occurs to clarity any needed items balm an estimate is sent.

Step 7- Estimates

Estimates are compared to the original baseline a monitor the general project schedule and correct the schedule as needed. Estimates Include dates for:  

• Code completion

• Quality assurance (test) completion

Step 8 – Project Schedule update

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.