Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points Tracking progress Tracking progress (But it is a nice burn-down chart) Production releases every 6 months Production release every 6 months (But we have 2 weeks sprints)
Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog Creating better burn- down charts How to sync story in Jira ?
Creating our burn- down charts Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog These are sym ptom s, not causes !
- "Business Agile": Built Upon Sand — R.Jeffries - The State of Agile Software in 2018 — M.Fowler - The Tragedy of Craftsmanship — Robert C. Martin - Developers Should Abandon Agile — R.Jeffries - The Failure of Agile — Andy Hunt - Time to Kill Agile — D.Thomas - The agile hangover — S.Mancuso
« Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, just done by brute force and thousands of slaves. » — Alan Kay We need to improve their commitment
A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 The sacred Provisional budget Management 101 The destroyer of illusions The feared balance
A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 Management 101 It’s a risk hedging strategy But, does it create value for the company ?
Scope (cost) Resources Time « Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law » Management 101
Scope (cost) Resources Time Quality You have to choose your next features carefully. The only thing you can flex Based on what has the most value for the customer
Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Collective ownership Acceptance testing Type system Planning game Short releases Feedback loops
A = What is the cost to create X ? & B = How much did it cost to produce X ? What our customers need next ? & How do we put it as quickly as possible in front of them ? From Planification to Prioritization
« Anyone building a process or framework for scaling Agile doesn’t know Agile. Period. Learn to ship software at will without any risk of defect, and you will discover you no longer need your framework. » — Arlo Belshee
lilobase
microcms
mitchan
77web
usamik26
okashoi
ohnoeight
napplecomputer
masayaaoyama
uhooi
leichteckig
tanakahisateru
coe401_
productmarketing
paulrobertlloyd
swwweet
phodgson
chriscoyier
mraible
jeffersonlam
skipperchong
jonrohan
rocio
marcduiker