Upload
dusan-kocurek
View
3.212
Download
1
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
1
Product owner…introduction of the most challenging role
Dusan KocurekNAVTEQAgile coaching, support & trainings,Collaboration with NAVTEQ Agile Workgroup
Ness KDC Focus Extended Development Center manager
ScrumDeskauthor, product owner
COOPEX Soft s r.o.Crises Management System for Slovak Republic Head of R&D department
Agile worldAgile@Slovakia FounderCertified Scrum Product OwnerScrum Alliance memberCoaching & mentoring
http://twitter.com/didierkoc
Goal
We are going to open a talk about
Agile &
Product Ownership3
What are your current concerns about the way how products are developed
and what is delivered?
4
Concerns I heard often
Features Quality
Time Cost
5
How many
features are/are not
used in products
you manage/use?6
Real life of features
Scott Ambler, IBM
Oc-ca-sionally19%
Never
45%
Al-ways7%
Often13%
Sometime
s16%
64%20%
Real life of featuresOc-ca-sionally19%
Never
45%
Al-ways7%
Often13%
Sometime
s16%
64%20%
WHY?
Scott Ambler, IBM
Customers
Changes
Competition9
Waterfall challengesCustomer
satisfaction
Change is everywhere
Timeframe todeliver a value
Feedback time
Understanding of a team
World doesn’t sleep
Waterfall challengesCustomer
satisfaction
Change is everywhere
Timeframe todeliver a value
Feedback time
Understanding of a team
World doesn’t sleep
HOW?
Typical way to solve issues
Contract
ProcessControl
Documentation
12
Agile is one possible alternative….
What Agility
in software developmentmeans?
13
Agility is the ability
to both create and respond to a change
in order to profit in turbulent business environment
Jim Highsmith, 2002
14
Agile Manifesto
Individuals and
interactionsProcesses and tools
Working softwareComprehensive documentation
Customer collaborationContract negotiation Responding to change Following plan
Agile Manifestowww.agilemanifesto.org
16
Change factor
Involve customer
in close collaboration
with development team
Simple principle
Cards
Conversation
Confirmation
CCC
18
• Feedback• Less communication channels• Pride & shame moments• Understanding of your potentialities• Planning according current needs• Doing what is necessary as late as possible• Additional sell channel
• It hurts• It take time• Meetings• Changes to be happened• Conflict with Date drive development• Contracts• Organization change
Involved customerPositive Negative (?)
versus
Adaption
Prediction
Waterfall vs. Agile
Agile approach
We are different…..
This is not possible…..
We can’t…..
If you would like to construct the building,
will you check how it looks
once is it
built?23
Check & deliver
24
A value in Agile is delivered during the development, not just at the end
Waterfall
Agile
How to develop in a different way
Incremental or iterative?
Simplified Agile product life cycle
Simplified Agile product life cycleBenefits?
Disadvantages?
Component vs. feature orientationComponent orientation
Feature orientation
Is agile product different?
Market Data
Innovation Games
Strategy, Vision,
Business Plan
Product PortfolioRoadmap
Metrics and KPI
Marketing Plan
29
Scrum overview
Roles Artifacts Ceremonies
30
Roles
Shock Therapy…
Product Owner
Father of the productVision
FeaturesPriority
Planning
Key Product Owner Attributes• A subject matter expert
• Knowledgeable about the business• Facilitates stakeholder input• Has decision making authority• Uses the system being developed
• Understands the key role of a Product Owner in Scrum• Has lots of time for the team, good communicator• Helps the team to improve© Innovel LLC
Story
35
As a <user>
I can <do something>
so that <user value received>
Acceptance Criteria
Business Value
Priority
Why?
Who is writing it?
Who is using it?
How detailed?
Agile RequirementsM
axim
ize
min
imum
YAGNI INVEST
Acceptance criteria
Scrum
Different levels of granularity
Release
Pre-planning
Iteration
Iteration planning
Feature
User Story 1 User Story 2User Story 1
Task 1 Task 2
User Story 2
Task 1 Task 2
Product planning
Parallel worlds
41
…what’s left
42
Iteration (sprint) tracking
Product BurnDown chart
44
…summary
45
Product Owner should expects
Working software on an iteration basis
Software must adds value through features that you can touch
Quality inside
It is a team work and commitment that should be honored
46
Product Owner Responsibilities
•Transparency•Help to team•Uncover ways
to continuously improve delivery
Process•Continuous
preparation•Release Early
and Often•Know team
velocity
Product
•Empower the team
•Gain commitment
•Stay tuned•Manage
uncertainty•Commit to
your plans
Iteration
47
What is different in Agile
• Customers on board• Less documentation• More collaboration• Improve product continuously daily• More meetings, but more productive• Near time planning preferred• Details are added as late as possible• Smaller development groups
48
…thank you
49
Is your customer the driver?
Add I. - Product Who?
50
Is• a leader
• Empowered to make decisions
• Necessary for product success
• Work for stakeholders• Work for the team
Must• Have a vision• Conveying vision to the
team• Gather what is required
• Leads a development effort• Outlines the work in backlog• Keep roadmap up to date• Prioritize based on business
value• Explain high-priority items
Should• Understand the market• Be available to the team
to answer questions
• Keep direction
• Respect the team’s ability to create its own plan of action
Can• Approve or decline
results• Have a visibility of
progress anytime
• Change a direction if necessary
• Expect real demonstration