5.3 Sprint One

User Story

The user should be able to navigate an online version of the User Guardian application, with a single page of the system fully operational and interacting with the backend database.

Goals

The goals are to:

• To build the site navigation and layouts as a coded online working version.
• To build a single PHP page that demonstrates updates and modifications to the underlying MySQL database.

Use Case - Business Roles

The first part of the system selected for development was the "Set Business Roles" screen (Figure 34). This section was selected as it has the most simple interaction with the underlying database. This would be more manageable than tackling some of the more complex interactions, while learning how to code the PHP and SQL elements.

Figure 34 - Diagram of Use Case - Business Roles

Preconditions

A working GUI to navigate to the Business Role page to create and delete business roles.

Timescales - Sprint Backlog

Agile Project sprint one on the original project plan was 35 days (part time hours), starting on the 29th July.

The revised date for the sprint start date is the 25th of November working full time until the 1st December for the coding section. Testing will be undertaking using spare hours during the evenings of the 1st & 2nd of December. The sprint will end on the weekend of the 4th and 5th December with the write up of the testing and project backlog ready for sprint two. This is shown in Table 23.

Table 23 - Sprint Backlog Task List

The sprint backlog tasks are scored on difficultly using the following scale. The points scoring is used for planning purposes to produce the project Burndown chart to plot development progress. The Burndown timescales are fitted within the agile sprint phases of the master project plan and Gantt chart found in sections 1.5 & 1.6.

Agile Scoring

1 point = simple task, no additional research or learning required.

3 points = Difficult to achieve, some working knowledge on how to complete the task.

5 points = Unknown how to produce or proceed without training or external advice.

Test Plan

To test this part of the system with a non-technical user to discover:

• How simple the site is to navigate?
• How clear are the screens?
• Is the user able to modify data without assistance?

The testing will be measured by interviewing the tester by asking these three questions for each task, and seeking possible comments for improvement. A successful test will be judge on the positivity of the answers graded 1 - 5.

To test the technical implementation roles will be added and removed using the GUI webpage. A successful test will be to show roles being added and deleted from the MySQL database.

Please see the testing feedback form for the non-technical user testing in the downloads section below.