17. Lean classifies 8 Wastes
“Tim Woods”
Transportation moving parts, people, informa7on
Inventory storing parts, documen7ng
Motion bending, turning, reaching, li=ing
Waiting for parts, info, equipment, tools
Over production making more than is immediately required
Over processing 7ghter tolerances and more efforts than necessary
Defects rework, scrap, incorrect documenta7on
Skills under u7lizing capabili7es, inadequate trainings
18. WHAT ARE THE TOP WASTES
IN SOFTWARE DEVELOPMENT?
20. scrum is a
product development framework
scrum connects product people with
development teams.
Scrum helps learn fast by inspecting and
adapting product and process.
Scrum exposes your process inefficiencies
– it is like a mirror.
21. Which Terms from the List
Are Not Part of Scrum?
User Stories
Velocity Metric
Grooming Meetings
Continuous Integration
Automated Testing
Monthly Releases
Visual Task Boards
Story Points
34. How Many Product Owners do you need?
A company develops a web-shop with services
like: a catalog, user profiles, email subscrip7ons,
persistent shopping cart, payments and B2B-
integra7on for partner shops.
How many products do you iden7fy?
How many Product Backlogs will you have?
How many Product Owners will you need?
40. types of hypothesis
1. Problem hypothesis
We assume there a problem.
2. User hypothesis
We assume these people have this problem.
3. Solu6on hypothesis
We assume our solu7on will solve it.
4. Growth hypothesis
We assume there are enough users.
41. Pivot examples
1. Odeo began as a network where people could find and
subscribe to podcasts.
2. This company actually began as an online role-playing game
called Game Neverending, where users would travel around
a digital map, interact with other users and buy, sell and
build items.
3. It was developed by a company called Confinity in 1999 to
allow people to “beam” payments from their PDA.
4. In 2007 a website called The Point was created which was a
“social good” fundraising site that ran on a “7pping point”
system, where a cause would only receive funding once the
pledged dona7ons reached a certain number.
42. What will you do when you learn your
hypothesis were wrong?
Agile makes Changing your mind legal.
45. Knowing your users
1. Demographics
who are they?
2. Values, Goals, Behaviors
what do they want to achieve?
how do they do their work now?
3. Needs, Frustra6ons, Problems
what is their pain?
55. how fast can you learn?
Do you need to build all product to see if it is valuable and
usable?
Can you build a part of it to validate your key
assumptions?
Can you build bare minimum to learn?
Can you not build it and still learn?
56. Build an MVP
1. Explainer Video
2. Landing Page
3. Wizard of Oz
4. Concierge
5. Fund Raising
6. Single Featured
hDp://7nyurl.com/mvp-ideas
hDp://scalemybusiness.com/the-ul7mate-guide-to-minimum-viable-products/
62. How and where do you keep
your product ideas?
Say “yap” if you keep them in the Product
Backlog.
Say “whoopsi” if you Product Backlog has
more than 100 items.
Say “yaks” if you need to use some sort of
epics/themes/lables in your backlog tool to
group the items so that they can be found?
73. Scrum Inception
The bare minimum to start scrum
1. Common understanding of Scrum roles
2. Team arrangements
3. Initial Product Visioning
4. User personas, user/market insights
5. Story mapping
6. Initial Release Planning: MVP, next releases
7. Defining Done
8. User Story Writing Workshops
(minimum: Product Backlog for the 1st sprint)
9. Backlog refinement
10. Sprint Planning
Product
Visioning
Release
Planning
Sprinting
Process
Agreements
88. Stakeholders “Buying” Features
Features Price Tag
(complexity*10)
Stakeholder A
(50 dollars)
Stakeholder B
(50 dollars)
Stakeholder C
(70 dollars)
Feature A 100 25 25 50
Feature B 20
Feature C 50 25 25
Feature D 100
Feature E 50
Feature F 20 20
95. PRODUCT BACKLOG REFINEMENT
IS THE PBI 1/10 to 1/6
OF TEAM’S VELOCITY?
SPLIT IT
REFINE IT NEXT PBI
NO
IS THE PBI CLEAR, FEASIBLE
AND TESTABLE?
NO
YES
YES
98. How to Split Backlog?
You are adding payment capabili7es to a web-shop.
Your teams iden7fied that you’ll need a database,
valida7on logic, integra7on with several APIs, build a UI.
Your teams want to create the following product backlog
items:
1. Create database to store transac7ons
2. Integrate with APIs
3. Transac7on valida7on
4. Develop UI for payment processing
What would you say?
103. INSTEAD Split BY BUSINESS VALUE
Payment
Payment with
Visa
Payment with
MasterCard
Payment with
PayPal
User is informed if
card data is not OK
User is taken to
success page
User is taken to
retry page
User can store his
card data Too big for a sprint S7ll too big for a sprint
109. In a Head of a Product Owner
You have split all the features into stories,
es7mated them with the teams, start measuring
velocity… and the data tells that you can’t do it
by the deadline.
What do you do?
A) Ignore the data and con7nue working
B) Try to shi= the deadline
C) Add people to the project
D) Make people work harder
112. Ingredients of Self-Organization
1. High Alignment
our goal is …
2. Clear Constraints
Here are some boundaries to follow …
3. High Autonomy
go and figure out how …
115. SPRINT PLANNING 101
Commitment-based PlanningPARTONE
PARTTWO
INITIAL SPRINT GOAL
PRESENTED
PLANNED CAPACITY
DISCUSSED
TOP PRODUCT BACKLOG
ITEMS PRESENTED
PBI REVIEWED ONE BY ONE
NEEDED REFINEMENT
HAPPENS
ITEM ADDED TO SPRINT
PLAN
CONTINUE UNTIL TEAM
SAYS “ENOUGH”
SPRINT GOAL GETS ADJUSTED
116. Sprint Is Not Mini-Waterfalls
analyze
design
test
code
Sprint Sprint Sprint Sprint
117. SCRUM IS NOT A SERIES OF MINI WATERFALLS
Feature A Feature B
PLANNED:
A,B,C,D
DONE:
nothing
DESIGN
PROTO
MORE CODING
TESTING
Sprint done wrong
CODING
Feature D Feature C
(next sprint)
PLANNED:
A,B,C,D
DONE
A,B,D
Sprint done right
Discussion Point
[PO + Dev Team]
118. Done. or Done-Done-Done?
Feature A Feature B Feature D
COOL: A,B AND D ARE DONE!
CAN WE DEPLOY THEM NOW?
(poker face)
OK.. SO WHAT’S LEFT?
1.
2.
…
10.