The Agile Extension to the BABOK® Guide.book

128 Pages·2011·1.28 MB·English

International Institute
IIBA®
of Business AnalysisTM
®
The Agile Extension to the BABOK Guide
November 2011 Draft for Public Review
The Agile Extension to the BABOK® Guide is a collaborative effort by the
International Institute of Business Analysis and the Agile Alliance.

Agile Extension to the
®
BABOK Guide
November 2011 Draft
for Public Review
www.iiba.org
International Institute of Business Analysis, Toronto, Ontario, Canada
© International Institute of Business Analysis. All rights reserved.
This document is provided to the business analysis community for educational
purposes. IIBA® warrants that it is suitable for any other purpose and makes no
expressed or implied warranty of any kind and assumes no responsibility for errors
or omissions. No liability is assumed for incidental or consequential damages in
connection with or arising out of the use of the information contained herein.
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are
registered trademarks owned by International Institute of Business Analysis. CBAP®
and CCBA® are registered certification marks owned by International Institute of
Business Analysis. Certified Business Analysis Professional, Certification of
Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP
logo are trademarks owned by International Institute of Business Analysis.”
The Agile Alliance® and the Agile Alliance logo are a registered trademarks owned by
The Agile Alliance.
No challenge to the status or ownership of these or any other trademarked terms
contained herein is intended by the International Institute Business Analysis.
This draft of the Agile Extension to the BABOK® Guide is provided to the community
for review and feedback and may not be used for any other purpose. In order to
provide feedback, please enter your comments at http://iiba.info/AgileFeedback.
Table of Contents
Chapter 1: Introduction to the Agile Extension 1
What is the Agile Extension to the BABOK® Guide?................................. 1
What does Agile Mean for Business Analysis?........................................... 2
What does Agile Mean for Business Analysts?........................................... 4
What makes a Business Analyst Successful on an Agile Team?............... 6
Chapter 2: Business Analysis in Agile Life-cycles 7
Scrum.............................................................................................................. 7
Backlogs........................................................................................................................... 8
Sprint Planning and Execution...................................................................................... 8
Roles and Responsibilities.............................................................................................. 9
Business Analysis in Scrum............................................................................................ 9
Techniques.................................................................................................................... 11
Extreme Programming (XP)........................................................................ 11
User Stories................................................................................................................... 11
Release Planning and Execution................................................................................ 12
Roles and Responsibilities........................................................................................... 13
Business Analysis in XP................................................................................................ 13
Techniques.................................................................................................................... 14
Kanban.......................................................................................................... 14
Queues.......................................................................................................................... 15
The Kanban Board....................................................................................................... 15
Roles & Responsibilities............................................................................................... 16
Business Analysis in Kanban....................................................................................... 16
Comparison of Agile Life-cycles................................................................. 18
Selecting an Agile Methodology or Framework......................................................... 19
Agile Levels of Planning.............................................................................. 20
Agile Levels of Planning............................................................................................... 20
Chapter 3: Knowledge Areas 25
Mapping Techniques to Knowledge Areas............................................... 25
November 2011 Draft for Public Review i
Business Analysis Planning and Monitoring............................................................. 25
Elicitation...................................................................................................................... 28
Requirements Management and Communication................................................... 30
Enterprise Analysis....................................................................................................... 32
Requirements Analysis................................................................................................ 34
Solution Assessment and Validation......................................................................... 36
Business Analysis Techniques Mapped to Agile Business Analysis Guidelines...... 39
Chapter 4: Techniques 43
A Context for Agile Business Analysis....................................................... 43
Guidelines for Agile Business Analysis..................................................... 44
A Note on Agile Extension Techniques..................................................... 44
See The Whole............................................................................................. 45
Business Capability Analysis....................................................................................... 46
Personas....................................................................................................................... 49
Value Stream Mapping................................................................................................ 51
Think as a Customer................................................................................... 55
Story Decomposition................................................................................................... 56
Story Elaboration......................................................................................................... 59
Story Mapping.............................................................................................................. 61
User Story..................................................................................................................... 64
Storyboarding............................................................................................................... 67
Analyze to Determine What is Valuable.................................................... 70
Backlog Management.................................................................................................. 70
Business Value Definition............................................................................................ 73
Kano Analysis............................................................................................................... 74
MoSCoW Prioritization................................................................................................ 77
Purpose Alignment Model........................................................................................... 79
Get Real Using Examples............................................................................ 81
Behaviour Driven Development................................................................................. 82
Understand What is Doable....................................................................... 84
Estimation..................................................................................................................... 85
Planning Workshop..................................................................................................... 87
Real Options................................................................................................................. 89
Stimulate Collaboration & Continuous Improvement............................ 93
Collaborative Games................................................................................................... 94
Retrospectives............................................................................................................... 96
Avoid Waste.................................................................................................. 98
Lightweight Documentation........................................................................................ 99
ii The Agile Extension to the BABOK® Guide
appendix A Glossary 103
appendix B Bibliography 111
appendix C Contributors 115
November 2011 Draft for Public Review iii
iv The Agile Extension to the BABOK® Guide
Introduction to the Agile Extension
chapter 1
1.1 What is the Agile Extension to the BABOK® Guide?
The Agile Extension to the BABOK® Guide describes business analysis
areas of knowledge, their associated activities and tasks, and the skills
necessary to be effective in their execution within the framework of
agile software development.
The purpose of the Agile Extension is to act as a business analysis
primer for agile software development methodologies and provide
business analysis practitioners with:
• an introduction to agile practices for business analysis,
• an overview of business analysis techniques for agile
practitioners,
• a set of definitions of typical working practices used by business
analysts working on agile projects, and
• an overview of the new and changed roles, skills, and
competencies for business analysis.
The Agile Extension is of value to business analysts new to agile, as well
as those experienced in agile methodologies. Both groups, and all
those in between, will find helpful information such as an introduction
to the practice of business analysis in an agile context, the mapping of
existing business analysis techniques to agile practices, and inclusion
of techniques that are specific to the practice of business analysis in
the agile world.
As the Agile Extension highlights, any member of an agile team may
engage in the process of business analysis. To that end, each person on
an agile team will benefit from having a set of practices and tools in
which they can select from while working in any one of the different
flavors of agile.
In the Agile Extension, we have called particular attention to the mind‐
set a business analysis practitioner must have in order to effectively
contribute to delivery of ongoing value to stakeholders. We have also
November 2011 Draft for Public Review 1
What does Agile Mean for Business Analysis? Introduction to the Agile Extension
described a number of techniques not found in the existing BABOK ®
Guide, and expanded on others that needed to be described in greater
detail. Many of the approaches described here, and the mind‐set we
describe, will prove valuable to business analysis in any methodology
and environment. Business analysts should always work to ensure
that requirements are aligned with organizational goals and objectives
and that all stakeholders have a shared understanding of those goals,
objectives, and requirements. They must also work to manage risks
and validate that the requirements, if delivered, will create real value
for stakeholders. Agile methodologies can help us find new ways to do
these things that support continuous delivery of working software, but
the responsibility to do these things is inherent to the profession of
business analysis.
1.2  What does Agile Mean for Business Analysis?
Much like other methodologies, business analysis is central to the
success of agile projects. Business analysis is necessary to enable a
diverse group of customers to speak with a single voice. This work
may be done by one of more members of an agile team.
In the agile world, software requirements are developed through
continual exploration of the business need. Requirements are gathered
and refined through an iterative process of planning, defining
acceptance criteria, prioritizing, developing, and reviewing the results.
Throughout the iterative planning and analysis of requirements,
business analysis practitioners must constantly ensure that the
features requested by the users align with the product’s business
goals, especially as the business goals evolve and change over time.
Agile business analysis is primarily about increasing the delivering of
business value to the sponsors and customers of the project/product
being developed. Agile business analysis aligns with the values and
principles of the Agile Manifesto (www.agilemanifesto.org):
• We value individuals and interactions over processes and tools.
• Our highest priority is to satisfy our customer through early
and continuous delivery of valuable software.
• Working software is the primary measure of progress.
Agile business analysis is about ensuring the right information is
available to the development team in the right level of detail at the
right time so they can build the right product.
2 The Agile Extension to the BABOK® Guide