Download - Enterprise Agile Requirements
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved.
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 2Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved.
Enterprise Agile Requirements
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 3
Enterprise-Class or Agile-at-Scale
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 4
REQUIREMENTS ARCHITECTURE
Business Clashing with Development
Business Need
• Regulatory Compliance and Audit• Business Case and Funding• Portfolio Prioritization and Management• Release Planning• Requirements persistence (remembering ‘why’)• Abstracting solution definition• Change Impact and Costing
Agile Practice
• Focus forward• Just enough detail• Stories are transient - answers are in the code• Limit work in progress – maximize the work not done• Fast pace, maximize delivery, minimize ceremony
Gap
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 5
Requirements in Agile
- Sherif Mansour, Product Guy, Atlassian Confluence
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 6
The Problem with “User Stories Only” in larger, complex, distributed IT projects
• User stories facilitate developer work and are transient (discarded when done)
• There’s little or no organized abstraction. • No auditable tracing to higher level business
objectives/needs/rules ..• No “analyzing of the business”• No good solution for portfolio/program-level needs
(prioritizing, tracking, managing releases, …)• No record of ‘why’ once the work is done• Some people believe they are not needed
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 7
Frameworks are evolving …
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 8
Requirements Taxonomy
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 9
Business Process Information Model
problem analysis
Requirements Taxonomy
FeatureTheme
Non-FunctionalRequirementNon-Functional
RequirementNon-Functional
Requirement
Non-FunctionalRequirementNon-Functional
RequirementNon-Functional
Requirement
Non-FunctionalRequirementNon-Functional
RequirementNon-Functional
Requirement
constrain
constrain
constrain
Use CaseUI
MockupsUI
MockupsUI
Mockups
Storyboard
Simulation
Other Forms
solution analysis / specification
FeatureFeatureFeatureEpicFeatureFeatureFeatureUser Story
FeatureFeatureFeatureFeatureFeatureFeature
FeatureFeatureEpic
FeatureFeatureFeatureEpicFeatureFeatureFeatureTasks
Provides Context or ElaborationAt any level
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 10
Enterprise Agile Requirements – Examples:
Tasks
User StoriesUser Stories
User Stories
TasksTasks
TasksTasks
TasksTasks
Use Case
• Used to provide high-level perspective• Scenario(s) basis for stories
• Used to elaborate on stories• Provided as additional info to team
Tasks
User StoriesUser Stories
User Stories
TasksTasks
TasksTasks
TasksTasks
Use Case
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 11
optional
Enterprise Agile Requirements – Examples:
Tasks
Epics
User StoriesUser Stories
User Stories
TasksTasks
TasksTasks
TasksTasks
UI Mockups
UI Mockups
UI Mockups
UI Mockups
SimulationStoryboard
Use Case
mandatory
Tests
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 12
Blueprint for Enterprise Agile
Product Owner; Agile ALM; Transient
Business Analyst; Blueprint; Persistent
Discovery & Scoping Iteration 0 Iteration 1
Analyze Business, Stakeholder Input,
Define Scope,Business Case,
Funding
Product Backlog
New Requirements
Update,Add,
Refine
Groom
Burn Down
Initial Product Backlog
Dem
o
Iteration n
Requirements
Product Backlog
New Requirements
Groom
Burn Down
Dem
o
Plan
/Cre
ate
Plan
/Cre
ate
Update,Add,
Refine
Update,Add,
Refine
Update,Add,
Refine
RequirementsInitial Requirements
Iteration Backlog
Iteration Backlog
Update Update
Update,Add,
Refine
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 13
Case Example …
Concept Interlock
FeasibilityInterlock
PlanInterlock
ReleaseInterlock
~9 weeks before Dev start ~6W before Dev start ~3W before Dev start ~3W before RTS
PM Lead Assigned – Each Release has a PM Lead
PM Lead Presents Base, Extended Scope items
Development/QA Lead Assigned
Leads Present Status and release recommendation
Executive TeamProduct Management Team
Chief ArchitectQuality Lead
SE LeadServices Lead
Executive TeamProduct Management Team
Chief ArchitectQuality Lead
SE LeadServices Lead
Executive Team Executive TeamChief ArchitectQuality Lead
Concept Interlock
~9W
Feasibility Interlock
~6W
Plan Interlock
~3W
Feature Freeze
RTS – 6W
Release InterlockRTS - 3W
RTS GARTS + 1W
CodeFreeze
RTS – 3W
Dev Start
18 weeks
Gated Process
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 14
BLUEPRINT
Case Example
Epics
User StoriesUser Stories
User Stories
UI Mockups
UI Mockups
UI Mockups
UI Mockups
Simulation
Storyboard
Use Case
Tests
MICROSOFT TEAM FOUNDATION SERVER
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 15
Case Example
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 16
Case Example
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 17
In Summary …
• There are ways for Agile to work NOW on large, complex, distributed IT software projects• Solutions: DAD; SAFe
• ‘Requirements’ is one of the key areas to focus on to make Enterprise Agile work• Solutions: Blueprint for Enterprise Agile (within DAD, SAFe, …)
• Layered approaches to let development teams be ‘agile’ while giving business what it needs.
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 18
Contact UsCall us and speak with a Business Development
Specialist.+1-866-979-2583 (BLUE) / [email protected]
Video Product OverviewWatch the informative video demonstration of Blueprint in action.
Watch Product Demo
Register Live DemoRequest a complimentary consultation with a Blueprint
representative.Live Demo Request