Succeeding with OKRs in Agile Extra
Succeeding with OKRs in Agile Extra
Companion to "Succeeding with OKRs in Agile" containing extra chapters and sections not included in the original.
About the Book
Extra chapters that deepend the discussion in "Succeeding with OKRs in Agile"
What is this book?
- What happens next?
- Spelling, grammar and all that
- Why read this book?
- What is this book?
1. Strategy v. change
- 1.1 Ambitious v. achievement
- 1.2 Stretch v. predicability
- 1.3 Autonomy v. authority
- 2.1 15% own project time
- 2.2 Hackathons
- 2.3 Golden ticket
- 2.4 Minimally Viable Team
- 2.5 OKRs
- 2.6 Portfolio approach
- 2.7 Dating agency
- 2.8 Summary
- 3. Deming
4. Teams TODO:Edit
- 4.1 Stable long lasting teams
- 4.2 Dependencies
- 4.3 Split for BAU?
- 5. Value in plain sight
- 6. What is value?
7. Outcome, value, benefit
- 7.1 Benefit
- 7.2 Value
- 7.3 Nature of value
- 7.4 Outcomes not to-dos
- 7.5 Summary
- 8. Incomplete information and trade-offs
- 9. Iterate doing and planning
10. Moon shot
- 10.1 Quality goals
- 11.1 Managers?
- 11.2 Managers role
- 11.3 Managers and OKRs
- 12.1 Simultaneously tight and loose
- 12.2 Day-1 mentality
- 1. Strategy v. change
II Essays and Blog posts
13. OKRs: a return to command and control?
- 13.1 What is there not to like?
- 13.2 The Connection to Today’s World
- 13.3 Thinking About Structuring OKRs
- 13.4 At the end of the day
- 14. Key Results
15. Why OKRs require a strategy rethinking
- 15.1 Is strategy a kind of planning?
- 15.2 Emergent strategy is more agile
- 16. Cascading OKRs and White Space OKRs
- 17. The difficulties of cascading OKRs
- 18. Focus is not divisible so limit you OKRs
- 19. Objective Driven Agile in 7 steps
- 20. The OKR cycle goes wide-narrow-wide
- 13. OKRs: a return to command and control?
III Organizational Structure
21. Top-down? bottom-up? or ripples in a pond?
- 21.1 Solar system
- 21.2 Autonomous
- 22. Programmer’s Rorschach test
- 23. A company is not a tree
24. Pull, don’t push: Why you should let your teams set their own OKRs
- 24.1 Cascading OKRs
- 24.2 Distributed OKRs
- 24.3 Pull don’t push
- 25. OKRs create strategy alignment but not in the way you think they do
- 21. Top-down? bottom-up? or ripples in a pond?
IV Question and Answers
- 26. Scrum or OKRs first?
27. How many OKRs should a team have?
- 27.1 Prioritise
- 27.2 Can a bigger team have more OKRs?
- 28. Topic: Can you keep Agile and OKRs separate?
- 29. How can we set an OKR if we don’t know the baseline?
30. The Backlog Q&A
- 30.1 Q: If the backlog isnt a reflection of what we need to do in order to move towards our vision what is it for?
- 30.2 Q2: Backlog needs reviewing to align with OKRs, surely?
- 30.3 Q: Isn’t OKR then a guidance to create Backlog? or prioritize it?
- 30.4 Q: How have you approached the removal of backlogs? small experiment?
- Version history
The Leanpub 60-day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.