User stories

The format

  As a <role>
  So that/In order to <business value>
  I want to <feature>

The above user story format is the one we will be using to describe the application. It is centered around three important questions:

• Who's using the system?

• What are they doing?

• Why do they care?

Examples

These are some initial user stories that we will be working with. In a real project we would spend a couple of hours to a week defining user stories and breaking them down to features and scenarios. For the purpose of this exercise, we will add user stories along the way as we progress.

As a course administrator,
In order to be able to issue certificates,
I want to be able to create a course offering with a description and multiple delivery dates

As a course administrator,
In order to be able to issue the right certificates for a course,
I want to be able display course title, course date and the
participants name on the certificate

As a course administrator,
In order to be able to issue certificates to participants,
I want to be able import a list of participants with their final grades

As a course administrator,
In order to be able to issue certificates to participants,
I want to be able filter participants by their final grades
and generate certificates by predefined conditions.

As a course administrator,
In order to be able to issue the right certificates for a course,
I want to be able to use a predefined design template for the certificate
(I want to be able to upload and use a design template for the certificate)

As a course administrator,
In order to allow external users to verify the authenticity of a certificate I issued,
I want to include a verification url to the certificate

As a course administrator,
In order to know how often my verification system is being used
I want to track every call to a verification url