2013 10 24 VS Agile PDF

Agile
October 24, 2013

Vision and Mission
The world's leading association for
Business Analysis professionals
Develop and maintain standards for

the practice of business analysis and
for the certification of its practitioners
IIBA® is an international not-for-profit

professional association for
business analysts.
2
© I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s
Tom Karasmanis
• IIBA Product Manager
Tom K arasm anis is a S enior C onsult ant w it h 25 y ears'
experience in I nf orm at ion Technology, including roles as a
B usiness A rchit ect , B usiness/ S y st em s A naly st , P roject Leader,
Technical A rchit ect , and S of t w are E ngineer. H e has w orked in f inancial
serv ices, publishing, healt hcare, public sect or and t elecom m unicat ions.
Tom serv ed as C hief A rchit ect of t he I I B A f rom 2009 t o 2011. H e is
current ly I I B A P roduct M anager of B ei ng a B A : Techni cal E xcel l ence and
Vendor S how case. Tom is a m anagem ent consult ant in business
archit ect ure and business analy sis, assist ing organizat ions t o build or
im prov e t heir B A pract ices. H e speaks regularly at int ernat ional
conf erences.
Tom holds a B achelor of A pplied S cience in C hem ical E ngineering f rom
t he U niv ersit y of Toront o and is act iv e in t he business analy sis and
business archit ect ure com m unit ies.
3
Outline
Introductions and Housekeeping 12:00
Vendor Presentations 12:05
• TechnoSolutions 12:05
• Polarion 12:25
• Blueprint 12:40
Questions and Answers 12:55
Close 12:59
Extended Q&A 1:00
4
Question and Answer
• How to Ask Questions
Use the Question box to ask questions.
Selected questions w ill be answ er ed Ashu Potnis
at the end, but you can ask at any time.
Include the vendor ’s name if you w ant
a specif ic vendor to r espond.
Shor t, specif ic questions, please!
Jim Ferranti
IIBA Host
Tom Karasmanis
Doug Stewart
5
AGILE
6
What is AGILE?
A methodology
An approach … to software development
The BABOK classifies Agile methods as a
change-driven approach.
•
7
Characteristics of AGILE
• Agile software development projects are:
Highly dynamic environments
Changing requirements are expected
Working software is delivered in short,
iterative cycles
The focus of business analysis activities is
firmly on undertaking the analysis activities
just enough, just in time
8
• Agile software development projects:
Are light on formal requirements
documentation
• Whiteboards
• Flip charts
• User stories
Focus on creating the minimum necessary
documentation to deliver the requirements
9
• Agile software development projects:
May require that all requirements be
expressed in the form of testable
acceptance criteria
Typically no change control process
• Traceability important
• Version control important
10
AGILE Manifesto
• We are uncovering better ways of
developing software by doing it and
helping others do it.
11
AGILE Manifesto
• Through this work we have come to value:
Individuals and interactions over processes
and tools
Working software over comprehensive
documentation
Customer collaboration over contract
negotiation
Responding to change over following a plan
12
Popular AGILE Methods
Scrum
Extreme Programming (XP)
Kanban
Crystal
Dynamic Systems Development Method
(DSDM)
Agile Unified Process (AUP)
Feature Driven Development (FDD)
13
SPRINT Elements
• Artefacts • Roles
User Stories Product Owner
Backlog Scrum Master
Sprint The Team
• Ceremonies Customer
Sprint Planning
Daily Scrum
Sprint Reviews
Sprint Retrospectives
14
SPRINT Cycle
15
Agile
Requirements & Processes
User Stories
Standup
Backlog
Meetings
Releases Sprints
Burndown
Charts
Agile
Rapid iterative development to deliver business
value in short cycles
Scrum Framework
User Stories
Releases Backlog
Burndown
Sprints
Charts
Standup
Meetings
Sprints and Releases
Release 1 Release 2
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5

Anatomy of a Sprint
Pre-Sprint Sprint
Allocate
Identify Refine
Backlog to Develop Test Deliver
Backlog Requirements
Sprint
User Stories
&
Constraints
Agile Requirements in TopTeam Analyst
TopTeam Analyst
Traceability
Agile Business Rules

Requirements Non-Functional Requirements
User Stories + Visualization and Application Simulation
Constraints
etc. Online Iterative Reviews & Approvals
Baselines, Versioning, Auditing

Author & Organize User Stories
Enter User Story
Organize User
Stories
in folders
Agile Requirements in TopTeam Analyst
Traceability
Business
Baselines
Rules
User
Story
Versioning,
Visualization
Auditing
Online
Approvals
Built for full Traceability TO and FROM User Stories
Define Trace
Schema/Rules for User
Stories
Trace Drill-Down using Diagram or Recursive
Multi-Level Impacts Report
Drill-Down User Stories into Use Case scenarios for
Requirements Visualization
Link “Business Rules” to

User Stories
“Derive” Scenarios from

User Stories as needed
Visualize Scenarios for Complex Interactions
Conduct Visual Application Walkthroughs with
stakeholders
Users Conduct Online Reviews & Approvals of
User Stories & Visualizations via their Web Browsers
Get rapid iterative

Requirements refinement
Versioning, “Diff” and Baselines
Precise “diff” between

User Story versions
Baseline Comparison
Project “Diff”
Prioritize User Stories
Sort on fields to
prioritize
Allocate Backlog Items to Releases
Add one or more Backlog

Items to releases
Manage Sprint Deliverables
Managing Agile Sprints via
TopTeam Integrations
Manage sprint execution using popular Agile project
execution and tracking tools
Rally
JIRA
TopTeam Rally Integration
User Story from
TopTeam Analyst
appears in Rally
repository
One-Click on link takes users to

TopTeam Web for full access to
Traceability, Business Rules and
other 360 degree information about
the User Story
TopTeam VersionOne
Integration
User Story from
TopTeam Analyst
appears in Version One
Repository
One-Click on link takes users

to TopTeam Web for full
access to Traceability,
Business Rules and other 360
degree information about the
User Story
TopTeam JIRA
Integration
User Story from

TopTeam Analyst
appears in JIRA
Repository
One-Click on link takes users

to TopTeam Web for full
access to Traceability,
Business Rules and other 360
degree information about the
User Story
When to use TopTeam Analyst for
Agile Requirements and Processes
Application Knowledge needs to persist after the end of the

Project/Product
Traceability / Compliance is important
Versioning, Differencing, Baselining is important
Enterprise Deployment / Agile needs to “fit” with other hybrid approaches

and existing legacy projects
Geographically Dispersed Team
Need to integrate with HP Quality Center/TFS & other tools

• A No-Compromise, end-to-end Solution for
Visual Requirements Definition and Requirements
Management
• Mature - launched 2005, now in seventh major

release
• Used by more than 500 organizations in 55

countries
integrations
Quality Center Rally
Team System (TFS) JIRA
Microsoft Word
Microsoft Excel
TopTeam Open API

(Integrate anything)
Learn more or try it yourself
TopTeamAnalyst.com
For more information
info@TechnoSolutions.com
"I am enjoying using TopTeam. It allows me more creative time, instead of document
formatting time, so my analysis is better and more detailed."
Carl Knowlan
Senior Analyst & Product Manager
Houston, Texas
Polarion Software®
Agile Business Analysis using Polarion
Jim Ferranti Systems Engineer Polarion Software, Inc.

Overview Our History
Polarion is the creator of the world’s fastest

enterprise scale web-based ALM solution.
The success of Polarion Software is best described

by the hundreds of Global 1000 companies and over
1 Million users who rely daily on Polarion’s
Requirements Management, Quality Assurance and
Application Lifecycle Management solutions in their
daily business processes.
Polarion Software ® www.polarion.com 43

Polarion ALM BA Principles
• Business Analysis Planning & Monitoring
• Elicitation
• Agile and Requirements Management
• Agile and Requirements Analysis
• Communication

Polarion ALM The Polarion Solution
Polarion ALM
Everything you need

In One Single ALM
Solution

Polarion ALM Create an Epic
Click on the type of work item you want to create
The window changes

to allow the creation of a
New Epic
Fill in the information and

Click on CREATE

Polarion ALM Building User Stories
From the newly created Epic,

Click on the blue plus ‘+’
Select New User Story
Enter appropriate
Information and
Click on ‘CREATE’

Polarion ALM End Result
My First Epic has been created
Along with the Epic, 3 supporting user stories

Polarion ALM Hybrid Agile Project
Agile Artifact
User Stories
Compliance Artifact
Requirements
Testing Cases
Defects

Polarion ALM The Polarion Solution
• Flexibility
• Agile/Project Analysis
• User Story Specifications
• Traceability

The Polarion Solution Flexibility
Your Processes
Your Methodologies

The Polarion Solution Agile/Project Analysis



The Polarion Solution User Stories

The Polarion Solution Traceability & History

The Polarion Solution Review
View Sprint Progress and Burndown Charts
Maintain Full Traceability and Auditability
Retain and Use Agile Artifact Information
Satisfy Agile Practices AND Compliance

Demands at the same time.
Use Familiar Document Views to Agile Backlogs
Define Your Own Agile and Hybrid Artifacts
Powerful Process Workflows
Create and Reuse Agile Frameworks and Templates

Achievements Polarion Customers

Polarion ALM
Next Steps
• Download 30-day FREE trial
• Try it LIVE
• Request proof of concept
• Watch demo
Stay connected with Polarion
Thank you for joining us today

www.polarion.com
Blueprint for Enterprise Agile
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved.

Business Clashing with Development
• Regulatory Compliance and Audit

• Business Case and Funding
• Portfolio Prioritization and Management
Business Need • Release Planning
• Requirements persistence (remembering ‘why’)
• Abstracting solution definition
• Change Impact and Costing
REQUIREMENTS Gap ARCHITECTURE
• Focus forward
• Just enough detail
Agile Practice • Stories are transient - answers are in the code
• Limit work in progress – maximize the work not done
• Fast pace, maximize delivery, minimize ceremony
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 62

Current Agile Practice
• User stories are discarded when done

• No organized abstraction of information
• 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 difficult
• Could be thousands of Stories
• No record of ‘why’ once the work is done
• Some people believe requirements are not needed

Plugging the Gap
Enterprise Agile supported by adding persistent

requirements
Role: Business Analyst (BA) Role: Product Owner (PO)

Application: RDM Toolset Application: Agile ALM Toolset
Requirements User Stories / Work Items

Persistent Data Transient Data
June 5, 2013 Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 64
Example Requirements Taxonomy
Provides Context or Elaboration

At any level
Bus iness Process Information Model
Feature
Theme
Non-Functional
Non-Functional constrain
Non-Functional
Requirement
Requirement
Requirement
Feature
Feature
Epic problem analysis
solution specification
Non-Functional
Non-Functional
Non-Functional
Requirement
constrain Feature
Feature
Feature
Feature UI Storyboa rd
Requirement
Requirement Feature UI
UI
Feature Us e Case
Mockups
Mockups
Mockups
Non-Functional
Non-Functional constrain
Non-Functional
Requirement
Requirement
Requirement
Feature
Feature
Feature
Epic
Feature Other
Feature
Feature
User Story Forms
Si mulation
Feature
Feature
Feature
Epic
Feature
Feature
Feature
Tasks

Completeness and Impact Analysis

Incremental Requirements Definition
Persistent
requirements
Backlog
Discovery iterations release
June 5, 2013 Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved. 67
Discovery & Scoping Iteration 0 Iteration 1 Iteration n

New New
Requirements Requirements
Ana l yze Business,

Sta keholder Input, Ini tial
Defi ne Scope, Requirements Requirements
Requirements
Bus iness Ca se,
Funding
Update Update
Business Analyst; Update, Update, Update,
Blueprint; Persistent Add, Add, Add,
Refine Refine Refine
Product Owner;
Groom Groom
Agile ALM; Transient
Ini tial Product Product Product
Ba ckl og Ba ckl og Ba ckl og
Plan/Create
Plan/Create
Update, Update,
Demo
Demo
Add, Add,
Refine Refine
Burn Burn
Down Down
Itera tion Itera tion
Ba ckl og Ba ckl og

Case Study – Blueprint Software
BLUEPRINT Simulation
Epics
UIUI
UIUI
Mockups
Mockups
Mockups
Mockups
Tests Storyboard
User Stories
User Stories
User Stories Use Case
MICROSOFT TEAM FOUNDATION SERVER

Project Implementation
Template Service
Sample Project Whitepaper

Getting Started Guide
Copyright © 2013 Blueprint Software Systems Inc. All Rights Reserved.
Questions

Question and Answer
• How to Ask Questions
Use the Question box to ask questions.
Selected questions w ill be answ er ed Ashu Potnis
at the end, but you can ask at any time.
Include the vendor ’s name if you w ant
a specif ic vendor to r espond.
Shor t, specif ic questions, please!
Jim Ferranti
IIBA Host
Tom Karasmanis
Doug Stewart
72
Contact Information
Register for m ore webinars on the Learning and
Development page of our website – under Webinars.
Ashu Potnis Jim Ferranti

Technosolutions Polarion
apotnis@technosolutions.com jim.ferranti@polarion.com
Doug Stewart
Blueprint
doug.stewart@blueprintsys.com
© International Institute of Business Analysis

73

2013 10 24 VS Agile PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2013 10 24 VS Agile PDF

Uploaded by

Copyright:

Available Formats

Agile

October 24, 2013

Develop and maintain standards for

IIBA® is an international not-for-profit

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5

Agile Business Rules

Baselines, Versioning, Auditing

Enter User Story

Link “Business Rules” to

“Derive” Scenarios from

Get rapid iterative

Precise “diff” between

Add one or more Backlog

One-Click on link takes users to

One-Click on link takes users

User Story from

One-Click on link takes users

Application Knowledge needs to persist after the end of the

Traceability / Compliance is important

Versioning, Differencing, Baselining is important

Enterprise Deployment / Agile needs to “fit” with other hybrid approaches

Geographically Dispersed Team

Need to integrate with HP Quality Center/TFS & other tools

• Mature - launched 2005, now in seventh major

• Used by more than 500 organizations in 55

Quality Center Rally

Team System (TFS) JIRA

TopTeam Open API

Agile Business Analysis using Polarion

Jim Ferranti Systems Engineer Polarion Software, Inc.

Polarion is the creator of the world’s fastest

The success of Polarion Software is best described

Polarion Software ® www.polarion.com 43

• Business Analysis Planning & Monitoring

• Agile and Requirements Management

• Agile and Requirements Analysis

Polarion Software ® www.polarion.com 44

Everything you need

Polarion Software ® www.polarion.com 45

Click on the type of work item you want to create

The window changes

Fill in the information and

Polarion Software ® www.polarion.com 46

From the newly created Epic,

Select New User Story

Polarion Software ® www.polarion.com 47

My First Epic has been created

Along with the Epic, 3 supporting user stories

Polarion Software ® www.polarion.com 48

Polarion Software ® www.polarion.com 49

• User Story Specifications

Polarion Software ® www.polarion.com 50

Polarion Software ® www.polarion.com 51

Polarion Software ® www.polarion.com 52

Polarion Software ® www.polarion.com 53

Polarion Software ® www.polarion.com 54

Polarion Software ® www.polarion.com 55

Polarion Software ® www.polarion.com 56

View Sprint Progress and Burndown Charts

Maintain Full Traceability and Auditability

Retain and Use Agile Artifact Information

Satisfy Agile Practices AND Compliance

Use Familiar Document Views to Agile Backlogs