Software Development Process: AGILE Methodology
Introduction:
Agile is a type of software development methodology that anticipates the need for flexibility
and applies a level of pragmatism to the delivery of the finished product. Agile software
development focuses on the clean delivery of individual pieces or parts of the software and
not on the entire application. Agile is highly dynamic and iterative in contrast with
traditional waterfall methods.
Benefits of Agile include:
Ability to help teams in maintaining a focus on the efficient delivery of product
Continuously evolves the products through daily reviews
Improves efficiency throughout the organization as teams work together and
understand their specific roles in the process.
Provides the opportunity to make changes as needed and alert teams to any potential
issues.
Final output is a high-quality product because testing is performed throughout
development.
Agile has largely replaced waterfall as the most popular development methodology in most
companies.
Project Scope and Objectives:
Define the scope of the project that team is going to develop.
Outline the specific objectives and deliverables expected from the product.
Team Roles:
Define the roles within the Agile team (e.g., Scrum Master, Product Owner, Development
Team) and their responsibilities in ensuring project success.
Team Member Project Role
Name
R- Responsible A-Accountable S-Support C-Consult I-Inform
Implementation Strategy:
Outline the steps involved in Project development and implementation highlighting the
below:
1. Project Goals
2. Product Design
3. Project Timelines- Gantt Chart
4. Create a Prioritized Product Backlog.
5. Conduct Effective Sprint Planning.
Risk Management and Contingency Plans:
Identify potential risks associated with the product development (e.g., timeline, resource
availability, resistance to change, scope creep etc).
Detail contingency plans and mitigation strategies to address these risks and ensure project
completion on time.
Resource Training:
Assess the training requirements for the team to deliver the project on time.
Monitoring, Measurement and Evaluation:
Describe the metrics and key performance indicators (KPIs) that will be used to assess the
success of Project execution. What would be the review mechanism and the review
frequency.
1. Visual Tools for Tracking Progress.
2. Daily Stand-up Meetings.
3. Track and Monitor Sprint Velocity.
4. Continuous Feedback and Adaptation.
Progress dashboards sha
Product Testing and Approval
Define the testing process. Testing process shall include:
Test case creation and approval
Unit Testing
System testing
Integration Testing
User Acceptance Testing
Complete Traceability to be maintained for the requirements, test cases and test results.
Test results to be retailed along with the test cases in the project documentation repository.
Product Go Live
Once the testing is completed and all the issues reported in testing have been resolved, the
project shall go live for a smaller scale.
Once it runs successfully on the small scale, only then it shall be released for production.
Project Rollback Strategy:
In case the product is not as per the customer expectations, it must be positively rolled back
to previous version.
On incorporation of the issues / feed backs Pm my plan for the product relaunch.
Project Maintenance
The team shall follow the ticketing system on IT helpdesk for resolution of any issues faced
by the team/s.
Appendices:
Include any supplementary materials such as Agile process diagrams, team roles and
responsibilities, and references, if any.
1. Project Backlog
2. RASCI Matrix
3. Requirement Traceability Matrix