the product owner in scrum a powerful agile business analyst · the product owner in scrum a...

The Product Owner in Scrum, a powerful Agile Business Analyst

BBC 2016, Las Vegas

Michele Maritato MBA, PMP, PMI-RMP, CBAP, CSM, PSM I, PSPO I, PMI-ACP

2 www.pm-progetti.it | michele.maritato@pm-progetti.it Michele Maritato, MBA, PMP, PMI-RMP, CBAP, CSM, PSM I, PSPO I, PMI-ACP

About me

RIBERA

1.  CONSIDERATIONS ON

AGILE BUSINESS ANALYSIS

2.  THE SCRUM TEAM & BA

3.  THE BABOK GUIDE AND

SCRUM FOR THE PO

The Agile Manifesto and the Babok Guide (1)

Process and Tools

Individuals and Interactions ov

Following a Plan

Responding to Change ov

Comprehensive Documentation

Working Systems ov

Contract Negotiation

Customer Collaboration ov

http://agilemanifesto.org/

BABOK Guide V3

The Agile Manifesto and the Babok Guide (2)

•  Change driven approach •  Focus on stakeholder

analysis •  Plan for governance

through interactions with people, over processes and rules

•  Organize to work together with people in co-located environments

•  Plan for exchanging information deeply and directly

•  Focus on continuous improvement

•  Plan for change in scope

•  Deep, continuous, informal interaction with people

•  Understand value •  Communicate value

•  “Agile” modelling techniques, focus more on engaging people

•  Understand motivation triggers

•  Understand risks in change driven approaches

•  Incremental solutions, focus on simplicity

•  Share continuously with people

•  Evaluate the solution on the field

•  Manage for continuous change of requirements and scope

•  Robust traceability •  Prioritization based on value •  Manage through engaging people

BABOK Guide V3

The Underlying Competencies

• Creative Thinking • Decision Making • Learning • Problem Solving • Systems Thinking • Conceptual Thinking • Visual Thinking

Analytical Thinking and

Problem Solving

Behavioral Characteris

Business Knowledge

Communication Skills

Interaction Skills

Tools and Technology

• Creative Think.

• Decision Mak.

• Learning

• Problem Solv.

• Systems Think.

• Conceptual Thinking

• Visual Think.

• Ethics

• Personal Accountability

• Trustworthiness

• Organization & Time Management

• Adaptability

• Business Acumen

• Industry Knowledge

• Organization Knowledge

• Solution Knowledge

• Methodology Knowledge

• Verbal Communicat.

• Non-Verbal Communicat.

• Written Communicat.

• Listening

• Facilitation

• Leadership & Influencing

• Teamwork

• Negotiation & Conflict Resolution

• Teaching

• Office Productivity Tools & Technology

• Business Analysis Tools & Technology

• Communicat. Tools & Technology

BABOK Guide V3

Other discoveries

Same considerations when we analyze also the 12 agile principles

The Babok Guide model is applicable with a focus on Agile: agile as a «mind frame»

Might use specific agile BA techniques

• Team

• ScrumMaster

• Product Owner

rs •  Management

•  Customer

•  Users

The Scrum Team

The Product Owner

Ø  Is responsible for maximizing the value of the product and the work of the Team

Ø  Is the sole person responsible for managing the Product Backlog 1.  Expressing the items 2.  Ordering (prioritize) the items to

best achieve goals and missions 3.  Optimizing the value of the work

the Team performs 4.  Ensuring that the Product Backlog

is visible, transparent, and clear to all

5.  Ensuring the Team understands items to the level needed

Developm

ent Team

more, more, more…

less, less, less…

The Scrum Team Ø  The Product Owner

ü One person accountable for value: “why”, “what”, “when”, “how to change”

Ø  The Team ü One team collectively accountable

for delivery: “how”, “who”, “where”

Ø  The Scrum Master ü One person accountable for making

Scrum work and ensure the Scrum Team adheres to the agile principles

IS THE FOCUS OF BA COMPETENCIES «WITHIN

THE PROJECT»

INTERACT WITH THE PO + BA COMPETENCIES TO

SUPPORT SELF-ORGANIZATION AND

CROSS-FUNCTIONALITY

SUPPORTING THE PO AND THE TEAM + SCRUM

ENABLER IN THE ORGANIZATION (HYBRID)

The Scrum framework

Business Analysis Planning and Monitoring

•  Plan BA Approach: Initial Plan, not only for BA activities

•  Plan Stakeholder Engagement

•  Plan BA Governance

•  Plan BA Information Management

•  Review/Develop further BA Planning Outputs

•  Identify BA Performance Improvements

Initial Plan: an example

Elicitation and Collaboration

•  Prepare for elicitation

•  Conduct elicitation

•  Confirm elicitation results

•  Communicate BA Information

•  Manage Stakeholder Collaboration

•  Elicitation tasks •  Collaboration tasks

•  Business R. •  Stakeholder R. •  Other Work

•  Business R. •  Stakeholder R. •  Solution R. •  Transition R. •  Other Work

Requirements Life Cycle Management

•  Trace Requirements

•  Prioritize Requirements

•  Approve Requirements

•  Trace Requirements •  Maintain Requirements •  Prioritize Requirements •  Assess Requirements Change •  Approve Requirements

•  Business R. •  Stakeholder R. •  Other Work

Traceability: an example

I N V E S T" SIZE"BUSINESS VALUE"

USER STORY N. 12 "

AS A User"

I WANT TO cancel a reservation"

SO THAT I can change mind when I want"

ACCEPTANCE CRITERIA"

MEETS TEAM’S DEFINITION OF READY ?"

• The system should receive in input the following info <…>, search in the repository, and present the following info as output <…>: Exception: if no record found the system should show a warning message “record not found”;"• If the user is a Premium Member, the system should permit to cancel the same day without a fee;"• If the user is a Non Premium Member, the system should charge 10% for a same day cancellation;"• The system must send an email to the user <email format>"• The system must send an email to the hotel <email format>"

Strategy Analysis

•  Analyze Currents State

•  Define Future State

•  Assess Risks

•  Define Change Strategy

•  All Strategy Analysis tasks •  Business R. •  Other Work •  Business R.

•  Other Work

•  Business Need •  Capability Gaps •  Solution Approach •  Solutions Scope •  Business Case

Requirements Analysis and Design Definition

•  Specify and Model Reqs. •  Verify Reqs.; Validate Reqs. •  Define Reqs. Architecture •  Define Design Options •  Analyze Potential Value and Recommend Solution

•  Stakeholder R. •  Solution R. •  Transition R. •  Other Work

Solution Evaluation

•  Measure Solution Performance •  Analyze Performance Measures •  Assess Solution Limitations •  Assess Enterprise Limitations •  Recommend Actions to Increase Solution Value

The Agile BA Techniques

Contacts

J Michele Maritato

! +39-335-5468934 " michele.maritato@pm-progetti.it

www.pm-progetti.it

michele.maritato

michelemaritato

the product owner in scrum a powerful agile business analyst · the product owner in scrum a...

Documents

agile scrum overview

disciplined.agile.delivery, scrum, agile

agile scrum training

agile scrum

agile auckland agile 101: scrum values

exin agile scrum

scrum and agile processes - nfq.lt · scrum and agile...

agile scrum introduction

agile – scrum +

scrum fundamentals: analyst to ‘agilist’ by louis molnar...

scrum agile process

agile scrum scrum... · agile scrum foundation training...

agile - scrum

gtface: agile scrum

agile scrum agile development practices 2010

agile (scrum)

agile e scrum

agile scrum retrospective

agile@core - scrum

agile scrum roles