We are now seeing that Software Industry has slowly started implementing AGILE process. Fast software delivery, continuous new requirements and balanced team engagement has put AGILE as a preferred process to follow.There are many benefits involved with AGILE process :
For better customer satisfaction and to be in race with the competitors, one has to deliver features/products on time, this creates pressure among team and this might reflect in
To make sure no rework(almost) is required to improve performance especially when everyone has sprint after sprint commitments, we must involve Performance Testing/Engineering Cycle after each sprint.
Failure to do this will take extra cycle of changes after final release, this might delay in next deliverables with same number of resources.
- Proper Clint Engagement and Transparency : Now customers are involved throughout the life cycle of software development, this is a very transparent approach to engage customers.
- Timely and Predictable Delivery : This Process makes sure predictable delivery time, based on sprints progress its easy to predict delivery date.
- Feature Acceptance and Feedback : Every feature getting delivered is well demonstrated among team and stakeholders which gives chance to get on time feedback and make changes if required.
- Regular Cost Analysis : Since everyone including customers are involved during the development life cycle timely cost analysis can be done.
- Improved Quality : Breaking projects into small deliverables makes sure in-depth focus on maintaining delivering Quality Product.
For better customer satisfaction and to be in race with the competitors, one has to deliver features/products on time, this creates pressure among team and this might reflect in
- Poorly coded product. Even there are code reviews which doesn't ensure better code in terms of performance especially on load conditions.
- QA may skip any Poorly Performing non functional design which can cause ripple effect during load condition or even while dealing with large set of data.
- Both developer and QA might be right on delivering stories on time, this doesn't ensure the better performing one.
To make sure no rework(almost) is required to improve performance especially when everyone has sprint after sprint commitments, we must involve Performance Testing/Engineering Cycle after each sprint.
Failure to do this will take extra cycle of changes after final release, this might delay in next deliverables with same number of resources.