5.3.4 Project Backlog and Sprint Two

The Project Backlog

The project backlog (Table 26) contains the full list of development tasks outstanding and available for inclusion within future development sprints. The items are point scored in terms of relative time/difficulty it would take to implement them.

Points can be added if new tasks are identified as required in the sprint. The points can be adjusted too for allowances where tasks are easier or harder than they first appear. Any additional points will be added to the effort remaining before the start off the next sprint.

The number of development days can be adjusted in the same way in relation to the task difficulty score.

Table 26 - Project Backlog

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.

New Items from Testing

The following table (Table 27) contains additional items discovered from the test to incorporate within the project backlog. The time and points will be added before the next sprint begins if they are to be included in on the project backlog.

Table 27 - Additional Items for Project Backlog

The Burndown Chart - Sprint Two

Table 28 contains all the tasks selected for the second development sprint. The additional days highlighted in red will be included as additional points on the Burndown chart.

The Burndown chart in Figure 43 provides progress against time. These sprints would need to be included in the main project plan to create a new project baseline and end date.

To capture the additional work 3 points and 1.5 days have been added to the remaining effort and development days for Sprint 1.

Table 28 - Second Development Sprint Tasks

Figure 43 - Burndown Chart

The points scoring and remaining development days tracking allows for detailed project management and for the project manager to approach the project sponsors on prioritising features or user stories.

In the User Guardian development the application connector and reports maybe scaled back to reduce the effort points and development days. There could then be a focus on the segregation of duties and toxic role mappings parts of the system to produce some basic working reports.