Building the Product Backlog

 

Barclays is an adopter of agile practices. A key component of agile is the Product Backlog. I was responsible for engaging with the Business to solicit requirements, translate those requirements into user stories, then manage the backlog throughout the life of the project.

 

Use Case Model

User Interactions

When designing any new system, it is important to identify the use cases involved in a user completing a task and the interactions they have with the system. I used Enterprise Architect to produce a use case model of the domain. 

Use case model: Cloud It

Use case model: Cloud It

Requirements workshop output

Requirements workshop output

User Story

An Expression of user need

User stories are excellent for describing what the user need is and how that need will be satisfied. At Barclays, I introduced a Behaviour-Driven Development (BDD) approach to documenting scenarios that the product had to support.

User Story: View profile summary

User Story: View profile summary

 

Product Backlog

Managing the backlog

There are some great tools available to help plan and manage agile projects. I chose Rally, as it has all the functionality you need, it's easy to use and works really well for small to medium-sized project teams. 

Rally: Task View

Rally: Task View

Design Tasks

tracking design tasks

Now that the product backlog was in place, it was time for the team to create tasks against the user stories they were working on. We used the daily task board to report on progress.

Rally: Task dashboard

Rally: Task dashboard