Lesson Outline

Sprint Two: Review

With the finishing touches that we just applied I was able to send this iteration through to the client for feedback. Depending on the clients level of familiarity with this process, you may want to give them more or less guidance and information about the process in general. For example, for some clients you might want to reiterate what specifically has been done in this sprint and what features will be implemented in future sprints.

If you are dealing with a more hands-on client - one that is involved more with the project management and organising the backlog in the Kanban board - then there will likely be less hand-holding and expectation setting required.

In this case, I am dealing with a relatively "hands-off" client so I made sure to provide plenty of explanation when delivering this iteration. With the client having had the opportunity to use the application, we can use any feedback they have to help guide the next sprint. In general, after each sprint, we would do something like this:

1. Get client feedback on current iteration
2. Review/re-sort the backlog based on our current understanding of the project
3. Add any new requirements/change requests
4. Plan the next sprint

Having used the application myself, I also prompted the client with some important features that would be good to include in the next sprint which were:

1. The ability to log out (this feature became an obvious necessity when it became difficult to show off the cool home page for the application)
2. Setting the application up as a PWA (this would provide a nicer experience when interacting with the application)