When working in sprints, there are two common ways of demonstrating work to a client. The first is during the sprint, which eats up time for actual development.
The second is after the sprint is finished. This is an interesting choice, as your team has more time to deliver more functionality than option 1.
Here are some observations about this option:
- Two-week sprints are now fully utilized by the development team. This means they can deliver more, and there’s less pressure on the team overall, especially in the last couple of days.
- You can migrate changes from the development sandbox to the QA sandbox on the last Friday of the sprint. If something goes wrong, you have the weekend to recover.
- The demo can be held on Tuesday or Wednesday of the following week. This provides some additional time on Monday, in case some last minute updates are needed.
- Since client feedback is provided after the next sprint has started, changes will only be added to the sprint after the next. This gets tricky with the last sprint.
If your client is OK with the feedback issue, this might very well be the better option for you.
The takeaway
Instead of rushing to demo during the sprint, consider doing it after the sprint is closed. This approach has numerous benefits and only a few drawbacks.
Category:
Salesforce