DevOps Books


The Phoenix Project
The Phoenix Project
Gene Kim, Kevin Behr, George Spafford
The Devops Handbook
The DevOps Handbook
Gene Kim, Jez Humble, Patrick Debois, John Willis 

Read Sample
Team Of Teams
Team of Teams: New Rules of Engagement for a Complex World
General Stanley McChrystal
The Goal
The Goal: A Process of Ongoing Improvement
Eliyahu M. Goldratt
Scrum: The Art of Doing Twice the Work in Half the Time
Jeff Sutherland
Kanban: Successful Evolutionary Change for Your Technology Business
David J. Anderson
Accelerate: Building Strategic Agility for a Faster-Moving World
John P. Kotter
Switch: How to Change Things When Change Is Hard
Chip Heath, Dan Heath
Drive: The Surprising Truth About What Motivates Us
Daniel H. Pink
Lean Software Development
Lean Software Development: An Agile Toolkit
Mary Poppendieck, Tom Poppendieck
Scrum And Xp 
Scrum and Xp from the Trenches
Henrik Kniberg

The Five Dysfunctions 
The Five Dysfunctions of a Team: A Leadership Fable
Patrick Lencioni
New Product Development Game
New Product Development Game
Hirotaka Takeuchi, Ikujiro Nonaka
Agile It Organization Design 
Agile IT Organization Design: For Digital Transformation and Continuous Delivery
Sriram Narayan
The Lean Machine 
The Lean Machine: How Harley-Davidson Drove Top-Line Growth and Profitability with Revolutionary Lean Product Development
Dantar P. Oosterwal

Gene Kim’s Email

Here is what you will get if you send an email to (As of Feb 13, 2017)

Hello all –

It was a privilege to be with you here today!

First off, I’m so happy to announce after over 5.5 years of work, The DevOps Handbook is here! Here are some stats on the book:

To get a free 130 page excerpt of The DevOps Handbook, just click here:

1 . Here’s a link to a longer version of the presentation I gave:

2 . You can find the videos and slides from the three-day DevOps Enterprise Summit below — we assembled leaders of large, complex organization who are adopting DevOps are sharing their transformation stories.

They showed that DevOps is for horses, and not just for unicorns. Speakers included leaders from GE Energy, Macy’s, Disney, Blackboard, Ticketmaster/LiveNation, Barclays Capital, US Department of Homeland Security, >, Nordstrom, Capital One, Raytheon and more…

Videos: Slides:

3 . To download the free 140 page excerpt of “The Phoenix Project,” just put your email address into this form:

4 . You can get hours of free samples of “The Phoenix Project” audiobook here:

5 . Here is a link to the DevOps Audit Defense Toolkit:

6 . If you you’d like to get announcements of early drafts of the upcoming “DevOps Handbook,” as well as other great information, just accept the Mailchimp subscription request – you’ll be getting an announcement in a couple of weeks your inbox.

We are now taking pre-orders for the DevOps Handbook at:

Thank you in advance for all your feedback!

Cheers! Gene

-– Now available in paperback: “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win”, v: +1-707-847-6771 (707-VIS-OPS1), @realgenekim

Scrum and XP from the Trenches

Scrum and XP from the Trenches - 2nd Edition Henrik Kniberg

The book can be downloaded for free from here.

Table of Content


Nokia Requirements for Iterative Development

Part One - Intro

Part Two - How we do product backlogs

Product Backlog Example

ID Name Estimate How to demo Notes
1 Deposit 5 Log in, open deposit page, deposit €10, go to my balance page and check that it has increased by €10 Need a UML sequence diagram. No need to worry about encryption for now.
2 See your own transaction history 8 Log in, click on “transactions”. Do a deposit. Go back to transactions, check that the new deposit shows up. Use paging to avoid large DB queries. Design similar to view users page.

How we keep the product backlog at a business level

Part Three - How we prepare for sprint planning

Part Four - How we do sprint planning

Why the product owner has to attend

Why quality is not negotiable

Sprint planning meetings that drag on and on…

Scrum is like any other tool – you can use a hammer to build something or to smash your thumb. Either way, don’t blame the tool.

Sprint-planning-meeting agenda

Backlog Refinement

10:30-11:30 Team time-estimates, and breaks down items as necessary. Product owner updates importance ratings as necessary. Items are clarified. “How to demo” is filled in for all high-importance items.

Sprint Planning

13:30-14:00 Product owner goes through sprint goal and summarizes product backlog. Demo place, date, and time is set.
14:00-15:00 Team selects stories to be included in sprint. Do velocity calculations as a reality check.
15:00-16:00 Select time and place for daily scrum (if different from last sprint). Further breakdown of stories into tasks.

Defining the sprint length

Short sprint Long sprint
short feedback cycle 
more frequent deliveries 
more frequent customer feedback 
less time spent running in the wrong direction 
learn and improve faster
The team gets more time to build up momentum 
they get more room to recover from problems and still make the sprint goal 
you get less overhead in terms of sprint planning meetings, demos, etc.
Product owners like Devlopers like

Defining the sprint goal

Deciding which stories to include in the sprint

This raises two questions:

1. How can product owner affect which stories make it to the sprint?

The product owner is disappointed that story D won’t be included in the sprint. What are his options during the sprint planning meeting?
Add D and remove C.
Reduce the scope of A.
Split the scope of A.

2. How does the team decide which stories to include in the sprint?

1) Gut Feel
2) Velocity calculations

Which estimating technique do we use?

Why we use index cards