Managing requirements in an Agile Project using Blueprint Requirements Center

1. Agile with Blueprint
1
ⓒ 2008 Blueprint Systems Inc. - Confidential & Proprietary

2. 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)
Sprint Plan Sprint Plan Sprint Plan Sprint Plan
requirements
requirements
requirements
software
software
software
Release
Backlog … 90%
75%
50%
30%
20% 10% 15%
5%
Sprint1 Sprint 2 Sprint 3 Sprint N

3. How Blueprint sets up it’s project structure…
One Project Contains All Models
Detailed Requirements Models
• For each feature outlined in the Product Backlog we have a
corresponding detailed requirements model
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

4. RELEASE Planning using a “Product Backlog” Model…
Planned Backlog Release Effort
Feature & Description
Release Priority Priority Est.
Total Effort currently
allocated to this
“RELEASE”

5. SPRINT Planning using a “Product Backlog” Model…
Which High level tasks/goals Feature
Feature Effort
sprint for this sprint description
Total Effort currently
allocated to this
“SPRINT”

6. Export from Blueprint to Scrumworks

7. Iterative Evolution of Requirements during sprints…
Product Backlog Model A Requirements model for a Feature
During a Sprint
Iterative Evolve Requirements
Auto Updated Test Cases
Simulation (Validate & Communicate)
Custom Properties to
manage scope

8. 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”

9. 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.