Lesson 13

A Change Request

Responding to a change in requirements


Lesson Outline

A Change Request

We haven't even started on our first sprint yet, but we already have a change request from the client! This is something the processes we have set up are designed to handle, so a change request is nothing to fret.

At this stage, the client has supplied me with three new requirements in the form of user stories:

  • As a massage therapist, I would like any new/changed responses in a users questionnaire highlighted, so that I can quickly view and analyse any relevant information
  • As a massage therapist, I would like to be able to view a history of previous versions of the questionnaire, so that I can understand how a clients needs have changed over time
  • As a massage therapist, I would like to be able to view my upcoming appointments by week/month, so that I can view future time slots and make it easier to book in current clients.

We haven't got into much of the development yet so this is still a rather easy time to incorporate a change, however, given that we have received this request so early it is a good chance to review it a little to see if it is going to impact the way we handle our data modelling with Firebase/Firestore.

First, we will add these new requirements to our backlog:


Thanks for checking out the preview of this lesson!

You do not have the appropriate membership to view the full lesson. If you would like full access to this module you can view membership options (or log in if you are already have an appropriate membership).