Agile Requirements by Collaboration



Similar documents
That Settles It! Techniques for Transparent and Trusted Decision-Making on Your Agile Team

Your Agile Team s Indispensible Asset

The Agile Business Analyst: Eyes for Waste By Ellen Gottesdiener Copyright EBG Consulting, Inc., 2009 EBG Consulting, Inc.:

Agile Extension to the BABOK Guide

Agile Project Management and Agile Practices Training; with a Scrum Project that you will do.

Agile Systems Engineering: What is it and What Have We Learned?

Slicing User Stories accelerate backlog refinement help sprint and release planning increase delivered value

A Guide to the Business Analysis Body of Knowledge (BABOK Guide) Version 2.0

Agile Certification: PMI-ACP

Certified Business Analysis. Professional (CBAP) version 3

Chapter 6. Iteration 0: Preparing for the First Iteration

Agile Project Management By Mark C. Layton

Agile for Product Owners

Business Analyst Work Plan. Presented by: Billie Johnson, CBAP CSM

MIS 3504 Digital Design and Innovation Studio

Course Title: Managing the Agile Product Development Life Cycle

The Agile Project Manager

WHY KANBAN? Troy Tuttle. blog.troytuttle.com. twitter.com/troytuttle. linkedin.com/in/troytuttle. Project Lead Consultant, AdventureTech

Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK

MIS 3504 Digital Design and Innovation Studio

Scaling Agile with the Lessons of Lean Product Development Flow Copyright 2012 Net Objectives, Inc. All Rights Reserved

T14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM

Executive Guide to SAFe 24 July An Executive s Guide to the Scaled Agile Framework.

Business Analyst Community. AmerisourceBergen

The Agile Manifesto is based on 12 principles:

Agile Methods. Introduction to. AAddison-Wesley. Sondra Ashmore, Ph.D. Kristin Runyan. Capetown Sydney Tokyo Singapore Mexico City

Scrum Guidelines. v W W W. S C R U M D E S K. C O M

As the use of agile approaches

44-76 mix 2. Exam Code:MB Exam Name: Managing Microsoft Dynamics Implementations Exam

How To Plan An Agile Project

Partnering for Project Success: Project Manager and Business Analyst Collaboration

I m an Alien... A Business Analyst in an Agile World Dorothy Tudor - TCC ABC 2014

Comparatif PMI-PBA VS CBAP3

How Product Management Must Change To Enable the Agile Enterprise

Software Requirements, Third Edition

AGILE - QUICK GUIDE AGILE - PRIMER

Agile & PMI Project Management Mapping MAVERIC S POINT OF VIEW Vol. 7

CHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan

AGILE & SCRUM. Revised 9/29/2015

How To Understand The Business Analysis Lifecycle

White Paper. Business Analysis meets Business Information Management

Becoming a Business Analyst

6 Oct Agile: Creating a Culture of Quality, Value and Feedback. Agile. Creating a Culture of Quality, Value and Feedback.

PMI Agile Certified Practitioner (PMI ACP) Boot Camp Course AG05; 4 Days, Instructor-led

By Peter Merholz, If you use it, please attribute it. Thanks.

ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )

When is Agile the Best Project Management Method? Lana Tylka

Agile project portfolio manageme nt

RISK MANAGMENT ON AN AGILE PROJECT

Teaching an Elephant to Dance. Patterns and Practices for Scaling Agility

Agile Product Roadmap Tutorial

Agile Testing. What Students Learn

Agile Planning & Metrics That Matter

Chapter 12. The Product Coordination Team

Agile Scrum and PMBOK Compatible or Contrary?


Agile Team Roles Product Owner & ScrumMaster. Brian Adkins Rick Smith

The Business Analyst Role in Agile Projects and How To Do It

Building a Better Backlog

Issues in Internet Design and Development

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led

BCS Certificate in Requirements Engineering Extended Syllabus

Higher National Unit specification. General information. Software Development: Analysis and Design (SCQF level 7) Unit code: HA4C 34.

Advancing Your Business Analysis Career Intermediate and Senior Role Descriptions

Scrum, User Stories, and More! CSCI 5828: Foundations of Software Engineering Lecture 22 11/06/2014

Career Builder Course Bundle

The Agile PMO. Contents. Kevin Thompson, Ph.D., PMP, CSP Agile Practice Lead cprime, Inc E. Third Avenue, Suite 205 Foster City, CA 94404

Business Analysis Standardization & Maturity

SIX KNOWLEDGE AREAS OF BUSINESS ANALYSIS

CSPO Learning Objectives Preamble. Scrum Basics

Atern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.

Project Lifecycle Management (PLM)

Introduction. Contents. Introducing the DSDM Agile Project Framework. Introducing DSDM

A Business Analysis Perspective on Business Process Management

Overview of Scrum. Scrum Flow for one Sprint SCRUMstudy.com. All Rights Reserved. Daily Standup. Release Planning Schedule. Create.

ADVANCED BUSINESS ANALYST (ABA) STUDY GUIDE

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology

Agile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series

Rising importance of Business Analysis when performing projects

The Agile Product Manager / Product Owner Dilemma

Agile Scrum Workshop

Introduction... 2 Introducing the DSDM Agile Project Framework (AgilePF)...2 Introducing DSDM...2 Introducing Scrum...3

Object-Oriented Systems Analysis and Design

The Team... 1 The Backlog... 2 The Release... 4 The Sprint... 5 Quick Summary Stakeholders. Business Owner. Product Owner.

How to optimize offshore software development with Agile methodologies

Agile Practitioner: PMI-ACP and ScrumMaster Aligned

Increasing Development Knowledge with EPFC

A Sample Proposal. By Krish Srinivasan. A Trusted Client Partner krishsvasan@hotmail.com

Expert Reference Series of White Papers. Intersecting Project Management and Business Analysis

Answered: PMs Most Common Agile Questions

Agile Software Development

Roles: Scrum Master & Project Manager

Transcription:

Agile Requirements by Collaboration [Aarhus, DK; 5 October 2010] Ellen Gottesdiener www.ebgconsulting.com Ellen Gottesdiener Founder & Principal Consultant, EBG Consulting Facilitator, trainer, mentor, agile coach, conference advisor Years of varied project and product experience Certified Professional Facilitator, Certified Scrum Master Expert Reviewer, contributor to IIBA BABOK (Business Analysis Body of Knowledge) Author: articles, books, blog blog: www.ebgconsulting.com/blog twitter.com/ellengott enewsletter: Success with Requirements free - sign up at www.ebgconsulting.com 1

intro collaborative workshops release workshop summary agile planning roadmap workshop iteration/ WIP workshop agile planning 2

rolling wave planning agile planning reqts analysis 3

progressive requirements elaboration boulders rocks pebbles 4

product big-view release pre-view iteration/wip now-view PRODUCT Big-View RELEASE Pre-View ITERATION/ WIP Now-View PRODUCT Vision, Value Goals, Objectives Product Backlog Product Roadmap Product Backlog Release Plan Iteration/ WIP Backlog 5

collaborative workshops a structured meeting in which a carefully selected group of stakeholders work together to define, create, refine, and reach closure on deliverables. Reference: Gottesdiener, The Software Requirements Memory Jogger 6

collaborating community business case 7

10-to-1 return on investment risk of scope creep reduced from 80% to 10% project failure & cancellation rates reduced by 50% the 6 P s 8

purpose participants 9

principles products 10

place process 11

Purpose Participants Principles Products Place Process Why do we do things? Goals Needs Motivation Who is involved? People Roles Responsibilities How do we function Guidelines Working agreements Ground rules What do we create? Deliverables Decisions Plans Next steps Where is it located? Venue Logistics When do we do what? Activities Sequence big-view: roadmapping workshop 12

purpose define product s vision and scope identify features to deliver for entire product or portfolio develop product backlog 13

participants project sponsor executive advisors: business/product mgmt strategic product owner subset of delivery team 14

[sample] products PRODUCT Big-View Who? Stakeholders What? Relationship Map Data Domains Glossary Project Charter Product Vision When? Events MMF Dependency Graph Why? Business Policy Groups Regulations How? Features Minimum Marketable Features Process Map Nonfunctional Requirements Product Backlog Product Roadmap 15

vision minimum marketable features 16

a chunk of functionality that delivers a subset of the customer s requirements, and that is capable of returning value to the customer when released as an independent entity. Source: Denne and Cleland-Huang Also see www.softwarebynumbers.org nonfunctional requirements 17

product roadmap workshop: time horizon: once per product, revise outcomes periodically 1-3 years 18

pre-view: release planning workshop purpose 19

identify what to deliver in release elaborate and prune product backlog estimate and prioritize backlog items participants 20

strategic and tactical product owner executive advisors: business/product management [as appropriate] delivery team [sample] products 21

RELEASE Pre-View User Roles, User Role Map Personas External Interfaces MMF Context Diagram Conceptual Data Model State Diagrams Dependency Graphs Business Policies Regulations Stories, Story Map Quality Attributes Design & Implementation Constraints Product Backlog Release Plan As a <user role persona> I need to <action behavior> so that <business value> user story (canonical form) 22

delivery, development dependencies pre-view: prune the backlog 23

workshop: time horizon: once per release, revise outcomes as needed 1-4 months now-view: iteration planning workshop 24

purpose identify what to deliver in iteration or what requirements to pull elaborate and prune product backlog estimate prioritized backlog items or determine cycle time based on acceptance criteria 25

participants tactical product owner delivery team 26

[sample] products ITERATION / WIP Now-View Prototypes External Interfaces User Story Context Diagram Data Model, Data Dictionary State Diagrams User Acceptance Tests Business Rules Decision Tables, Trees Ready Stories, Scenarios Quality Attributes Design & Implementation Constraints Iteration / WIP Backlog 27

tampeddown requirements doneness 28

asking questions supplemental analysis models 29

data states rules interfaces user acceptance tests now-view: prune the backlog 30

work ahead a.k.a. make ready workshops: 2+ times before iteration planning & multiple times throughout; as analysis queue opens time horizon: 2-3 weeks 31

summary skills needed 32

facilitation requirements modeling agile (and other) methods facilitation 33

reqts modeling 34

collaboration pattern multi-model agile methods 35

PRODUCT Big-View RELEASE Pre-View ITERATION / WIP Now-View Who? Stakeholders User Roles, User Role Map Personas External Interfaces Prototypes External Interfaces What? Relationship Map Data Domains Glossary MMF Context Diagram Conceptual Data Model User Story Context Diagram Data Model, Data Dictionary Project Charter Product Vision When? Why? Events States Dependency Graphs Business Policy Groups Regulations State Diagrams Dependency Graphs Business Policies Regulations State Diagrams User Acceptance Tests Business Rules Decision Tables, Trees PRODUCT How? Features Minimal Marketable Features Process Map Nonfunctional Requirements Stories, Story Map Quality Attributes Design & Implementation Constraints Ready Stories, Scenarios Quality Attributes Design & Implementation Constraints Vision, Value Goals, Objectives Product Backlog Product Roadmap Product Backlog Release Plan Iteration / WIP Backlog successful workshops 36

sponsorship clear scope and definition of value business & technical participation workshop planning & design continual planning adjust workshop formality functional & nonfunctional requirements skilled facilitation retrospectives done 37

collaborating to agile beat email more agile ellen@ebgconsulting.com ebgconsulting.com/agile.pdf more workshops ebgconsulting.com/facres.php ebgconsulting.com/facassets.php about EBG www.ebgconsulting.com 38

www.bettersoftware.com Upcoming public offerings: London Agile Requirements: 6-7 December Collaborating for Success 8-10 December 39