Agile with Blueprint

1

ⓒ 2008 Blueprint Systems Inc. - Confidential & Proprietary

Requirements

• We start with a high level requirements / feature lists etc.

• Each sprint -> “just enough requirements detail”

• Initial “baseline” of requirements are done in sprint (s) prior to build sprint(s)

• We expect and plan for changes to these requirements during later sprints

• Last few sprints are “stabilization” sprints (bug fixes only)

Sprint1

requirem

ents

soft

ware

20% 5%

Sprint 2

requ

irem

ents

soft

ware

30%

10%

Sprint 3

requ

irem

ents

soft

ware

50%

15%

Sprint N

90%

75%

… Release Backlog

Sprint Plan Sprint Plan Sprint Plan Sprint Plan

How Blueprint sets up it’s project structure…

Product Backlog

• One Model File for the “product backlog”• Custom properties for (priorities, effort, release ……etc)• Use Filtering and Totals in Requirements Spreadsheet for both

Release and Sprint Planning

Detailed Requirements Models

• For each feature outlined in the Product Backlog we have a corresponding detailed requirements model

One Project Contains All Models

RELEASE Planning using a “Product Backlog” Model…

Feature & DescriptionPlanned Release

BacklogPriority

ReleasePriority

EffortEst.

Total Effort currently allocated to this

“RELEASE”

SPRINT Planning using a “Product Backlog” Model…

Feature description

Feature EffortHigh level tasks/goals

for this sprintWhich sprint

Total Effort currently allocated to this

“SPRINT”

Export from Blueprint to Scrumworks

During a Sprint

Iterative Evolution of Requirements during sprints…

Product Backlog Model

Auto Updated Test Cases

Simulation (Validate & Communicate)

Iterative Evolve Requirements

Custom Properties to

manage scope

A Requirements model for a Feature

Blueprint and Distributed Agile

• The challenges with Distributed Agile Teams….

– Distributed teams remove a key cornerstone of agile

• No longer Co-located teams

• Language, culture & distance issues

• Reduced communication efficiency and accuracy

– Studies show defect rate doubles, projects take longer

• Blueprint helping solve these challenges….

– Provides mechanism to gain back a significant portion of communication accuracy and efficiency

• Integrated Requirements

• Auto Gen (test cases, docs etc)

• Centralized & version controlled repository

– Supports iterative nature of Agile

• Elicit, Elaborate, Visualize, Accept

• Variable fidelity – “just enough spec details”

Supporting Iterative & Evolution of Requirements

• Blueprint supports Iterative and Evolutionary Requirements by…

– Version Control

– Variable & incremental fidelity of Requirements details / UI mockups / Use Cases

– Simulation to communicate (great for co-located or distributed/offshore teams)

– Simulation to validate (like a compiler for requirements)

– Typical Iterative, evolutionary process

• Start

– Start with Features list

– Create simple low-fidelity mockups

– Perhaps add a simple set of use cases

– Review via simulation - encourage discussion and creative ideas

• Continuous

– Continue with Elaboration of features, mockups and use cases and simulation review sessions until there is “enough” detail to start development.

– Continue to review requirements (Features, Mockups, Use Cases) – Review changes via simulations.