Just like a car, applications need servicing and tuning every now and then to stay in top condition. They might need alterations to deal with new business problems, or just tuning to increase efficiency.
Figure: What happens after the software has been delivered and the development team moves on. The next phase is maintenance
So you’ve done 10 good Sprints and the software has been delivered (it's ready!) and the team is winding down. It will need maintenance.
Different clients need different levels of support. Offer your clients a few different support offerings.
1 day per week (or whatever quantity suits), a developer will work on enhancements and bug fixing. This is useful because the client always knows when work will next be done.
For a small monthly cost, plus a multiple of the hourly rate, you can guarantee specific response and resolution times. This way your client will be guaranteed that they can get out of a fix quickly when needed.
Learn more on Support Plan
A client can simply call for bug fixing or support as and when needed. However, unless it's a show stopper, this model can involve waiting for developer availability.
For a fixed price project, a warranty commences after the Sprint Review. The warranty length is half the length of the Sprint and, during this period, any bugs reported will be fixed for free.
Once the Sprint Review is complete, the Product Owner has half the Sprint period again to report any bugs. The conditions are: