I do not know nothing about agile and they call me PO !!
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
I do not know nothing
about agile…
…and they call me PO !!
Slide 1
9. September 2014
Rainer Grau, Zühlke AG
© Zühlke 2014
Rainer Grau
Executive Director & Partner
Distinguished Engineer
• Executive Director and Partner Zühlke
• Distinguished Consultant for Project &
Portfolio Mgmt, Innovation, Lean, Agile
and Change Mgmt
• Board of directors IREB
• Board member ISPMA
• Head STC Informatics Swiss Association for
Quality
• Member Swiss Agile Leaders Circle
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 2 © Zühlke 2014
Many thanks!!
…to my colleagues and friends who
shared there experience with me
Mischa Ramseyer
Daniel Tobler
Markus Flückiger
Matthew Caine
Elizabeth
Alex Bögli
Woodward
Woodward Innovation Inc
Klaus Bucka-Lassen
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 3 © Zühlke 2014
Theory is so simple
Vision
Daily
Product Owner Scrum
Scrum Master
Team
Sprint Goal
Sprint
Product Sprint Planning Sprint Sprint Review &
Backlog Meeting Backlog Retrospective
Potentially Shippable
…ordered by Product Owner Product Increment
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 5 © Zühlke 2014
Responsibility of a Product Owner
(Source: www.scrum.org/Scrum-Guide)
• The Product Owner is responsible for maximizing the value of the product
and the work of the Development Team
• The Product Owner is the sole person responsible for managing the Product
Backlog. Product Backlog management includes:
– Clearly communicating vision, goals, and Product Backlog items to the
Development Team;
– Ordering the items in the Product Backlog to best achieve goals and missions;
– Ensuring the value of the work the Development Team performs;
– Ensuring that the Product Backlog is visible, transparent, and clear to all, and
shows what the Scrum Team will work on next; and,
– Ensuring the Development Team understands items in the Product Backlog to the
level needed.
• The Product Owner may do the above work, or have the Development Team
do it. However, the Product Owner remains accountable.
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 6 © Zühlke 2014
Discovery …
• Separation of concerns
• The PO cares for the content
• The PO communicates vision and goals and prioritizes work to
best achieve those
• The Scrum Master is a servant leader
• The Scrum Master cares of the Team and the integration into
Organization
• …
• …
• …
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 9 © Zühlke 2014
What about passion !?
What about intrinsic motivation !?
This is Walter
This is Sue
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 10 © Zühlke 2014Passion
This is Walter
Passion for technique
– His bike is just perfect
Loves and thinks in features
– There is a set of features he really
would like to see in “his” product
Drives other people mad
– “…I am convinced our customer
will just love this…”
– “…better we skip this and focus
on THAT…”
Is proud of what he achieved
– “…yours product looks just fine, but mine is outstanding, remarkable. You
will love it because…”
– “…let’s celebrate the launch…we better get some beer and pizza…”
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 11 © Zühlke 2014Intrinsic Motivation
This is Sue
Sue has power, standing and born aptitude for communication
– She loves to demonstrate this and to receive perception and recognition
– She is the perfect networker and knows how to play the game
Sue loves to work with people
– Moderation, mediation, turning conflicts into chances, challenges into opportunities makes
her feel good
.
She hates stupid obstacles
– “…what about if we change…”
– “…c’mon guys, we can’t accept that
stupid proceeding eating up our
money…”
Sue gains trust
– As she acts competent, clear,
transparent, ethical, non-political
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 12 © Zühlke 2014What topic, task, responsibility will gain your interest today? I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 13 © Zühlke 2014
Avoid conflicts
The important ones typically not listed
• Intrinsic motivation conflict
– Example: I rather work on the content than organizing things with Ops
• Emotional factors conflict *
– Example: David defines success as receiving praise for the last project and
being responsible for the next (far more complex) project
– Example: Shula defines the “Wow” of the users as success
The important and listed ones
• Conflict of interests
– Example: Sitting in the election committee as mentor of the candidate
• Conflict of Responsibility
– Example: being auditor of my own project
*) See: motivating factors from Management 3.0, http://www.management30.com/
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 14 © Zühlke 2014Personal Experience when trying to
identify PO and SM
• The passion of individuals is either on the content (product, vision, goals,
features…) or on the project (team support, development process, …)
• The passion is never on both at the same time
One aspect will be uncared for if assigned to one person, therefore:
Walter, the PO Sue, the SM
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 15 © Zühlke 2014The PO is the person with passion for the
content
The term “Content” is manifold
• Vision of the business project, a physical product, a
service, an application, a concept, a change, …
The organizational level a PO acts is manifold
• The PO of a development team (classical Scrum idea)
• The PO of an organizational change
• The PO of a huge program running six years PO
• The CEO seen as PO of the company?
• …and yes – the PO has a SM as pair on the same level
PO / SM pairs drive an agile organization
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 16 © Zühlke 2014Identify PO / SM pairs
• For an area of responsibility
• On the different levels within
your organizationA PO / SM Pattern ?
Level 1 CEO (PO) COO (SM)
Product
Program Project Mgr (PO)
Mgr (SM) Mgr (SM)
BA (PO)
Guilds of Skills
Level 2, Sector A, SW Level 2, Sector B, HW Guilds for Disciplines
Subject Matter Experts
Technical Expters
SM PO SM PO SM PO SM PO
Level 3 Sector Level 3 Sector Level 3 Sector Level 3 Sector
A1 A2 B1 B2
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 18 © Zühlke 2014Personal observations
Important areas of responsibility
• Strategy, Portfolio (of projects)
– PO: Head R&D, CEO, Division Manager, Portfolio Manager,… Portfolio Mgmt
– SM: CEO, COO, Senior Program Manager, Line Manager,…
• Program or multi-team project
– PO: Product Manager, Senior Business Analyst, Subject Matter
Expert, Solution Designer, Program Manager, … Program Mgmt
– SM: Line Manager, (refactored) Project Manager, …
• Team or simple project
– PO: Subject Matter Expert, Solution Designer, Business Team
Analyst, Requirements Engineer, …
– SM: Team member, External Coach, …
ATTENTION: A role and a job-profile are orthogonal
concepts
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 19 © Zühlke 2014The normal madness and inflation of roles
…this is incomplete…
Business IT (client side)
RE IT Project
Business Solution QA
Mgr
Prj Mgr Designer
Enterprise
UAT Tester
App Architect
Owner IT (supplier side)
UAT BA
Test Mgr
Dev
Subject SW-Tester Supplier
Prj Mgr
Matter Release Solution
Expert Mgr Architect UX-Expert
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 21 © Zühlke 2014Business Roles
(obfuscated merger of some real life specifications)
Role Responsibilities
Business Project The business project manager is responsible that the project objectives are clearly
Manager defined and met. He is responsible for the overall operational management of the
project.
Solution Designer The solution designer specifies business processes and functional design of the
solution that realize the project business objectives.
App Owner The application owner is the functional and technical owner of the application. He is
responsible for its improvement, maintenance, support and operation.
UAT Test Manager The UAT (user acceptance test) test manager manages the acceptance testing
procedures required to validate operational readiness.
Business Analyst The business analyst translates the demand of subject matter experts and other
stakeholders into requirements (functional, quality, constraints).
Subject Matter The subject matter expert is a functional expert. He is a important stakeholder to
Expert elicit requirements, design the solution and functional design including usability
aspects.
Release Manager The release manager is responsible to identify, specify and confirm consistent
releases of project deliverables to optimize the values for the organization.
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 22 © Zühlke 2014IT Roles (client side)
(obfuscated merger of some real life specifications)
Role Responsibilities
IT Project Manager The IT project manager manages the development and delivery of an IT solution that
realizes IT supported objectives of a business project.
Quality Assurance The quality assurance expert is responsible for the quality assurance and control
activities related to an IT project. quality assurance reports quality KPI’s to the
business project manager.
Requirements The requirements engineer specifies the requirements of the to be developed IT
Engineer solution derived from business requirements. In collaboration with the enterprise
architect he is responsible to design an efficient and effective IT solution.
Enterprise Architect The enterprise architect is responsible for enterprise level architecture design
including modularization, usage of COTS and development of bespoke IT modules. He
defines standards, technical tools, infrastructure and operational conditions of
architectural elements. He is responsible to define the enterprise architecture
roadmaps and housekeeping activities.
UAT Tester The UAT (user acceptance test) required. The UAT tester executes and reports user
acceptance tests of the application to validate operational readiness.
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 23 © Zühlke 2014IT Roles (supplier side)
(obfuscated merger of some real life specifications)
Role Responsibilities
Supplier Project The supplier project manager is responsible for the delivery of project deliverables
Manager developed by the supplier according the defined conditions. He is first contact of the
supplier side for escalation and change management procedures.
Solution Architect The solution architect is responsible for the functional and technical design of an
application or platform within the constraints of the enterprise architecture
definitions.
Usability Expert The usability expert is responsible for the design parts of the application that
influence the usability. This includes user experience, ease of use, navigation, visual
design, multi-device support, conformity to CD
Developer The developer translates requirements into IT assets following state of the art skills
and techniques. He is as well responsible to design, implement and execute
(automated) unit tests that verify robustness, operability, functional correctness and
maintainability.
Software Tester The software tester specifies and executes system, integration, load and performance
tests of the IT deliverables that verify quality requirements for operational readiness.
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 24 © Zühlke 2014Identify the PO
Identify SM and Team Member
IT Project
Business Solution RE QA Mgr
Prj Mgr Designer
UAT Tester
App Enterprise
Owner Architect
UAT
BA
Test Mgr
Dev
Subject SW-Tester Supplier
Prj Mgr
Matter Release Solution
Expert Mgr Architect UX-Expert
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 26 © Zühlke 2014Identify the area if responsibility,
Identify the PO, SM and Team Member,
Know about stakeholder
Subject
IT Project
Matter
Mgr
Expert
Solution
Solution Architect Dev
Designer Potential Supplier
Potential
BA PO’s Prj Mgr
SM’s
Dev UAT Tester
Release
Business App SW
Prj Mgr RE
Mgr
BA Owner
Solution Tester
Enterprise UAT
QA Architect Test Mgr Architect UX-Expert
Stakeholder (if required at all) Potential Team Member
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 27 © Zühlke 2014Second Example:
A real life, non-trivial program
Program User
Mgr Subject VIP’s
Matter Partner
Sponsor Expert Supplier
SteCo Enterprise
Architect
Subject Release
BA App QA
Matter Mgr
Owner
Expert UAT
Test Mgr Supplier
RE BA
IT Prj Mgr Prj Mgr
Teams
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 29 © Zühlke 2014Second Example:
A real life, non-trivial program
SM Program User
PO
Mgr Subject VIP’s
Matter Partner
Sponsor Expert Supplier
SteCo Enterprise
Architect
Subject Release
BA App QA
Matter Mgr
Owner
Expert
Line Mgr
BA Supplier
RE
IT Prj Mgr Prj Mgr
Teams
I do not know nothing about agility - but they call me PO | Rainer Grau, Zühlke AG 9. September 2014 Slide 30 © Zühlke 2014*) Citation Peter F. Drucker: Management, Revised Edition, 2008
Experiences and observations
Passion and intrinsic
motivation matters Map Scrum
roles to
organizational
roles
PO / SM pairs are a
success factor
Portfolio Mgmt
PO / SM pairs might
Program Mgmt exists on different
organizational levels dogmatism is the
Team natural enemy of
economic thinking
© Zühlke 2014Become agile!
• Don’t fake it
• Don’t make it
• Don’t buy itYou can also read
