Corporate Revolutionary Library

In The Phoenix Project, we introduced the Three Ways underpinning DevOps. In my follow-up book, The Unicorn Project, I revisit Parts Unlimited and describe my learnings through the Five Ideals.

The dust-up over the term "NoOps" escalated this week, with high-profile IT executives from Netflix and Etsy issuing dueling blog posts about the evolution of IT...

It’s not often that my emails turn into full-blown conversations on DevOps. But when it happens, it’s a great time to take advantage of the insights. John

Trusted by Companies WorldwideDevOps is The Future of IT. DevOps Institute Gets You There.DevOps Institute Community MembersCertifications

In his mega bestseller, Thinking, Fast and Slow, Daniel Kahneman, world-famous psychologist and winner of the Nobel Prize in Economics, takes us on a groundbreaking tour of the mind and explains the two systems that drive the way we think.

The Effective Change Manager's Handbook helps practitioners, employers and academics define and practise change management successfully and develop change management maturity within their organization.

Great things don’t happen in a vacuum. But creating an environment for creative thinking and innovation can be a daunting challenge.

Learn how to apply agile concepts to your projects. This fully updated book covers changes to agile approaches and new information related to the methods of managing an agile project.

This is the definitive, realistic, actionable guide to starting fast with Scrum and agile–and then succeeding over the long haul

If you want to use Scrum to develop innovative products and services that delight your customers, Essential Scrum is the complete, single-source reference you’ve been searching for.

Scrum in easy steps provides an introduction to Scrum, then steps through how a team gets going on a project and how they sustain performance and continually improve.

Insights into the application of Agile across different areas of the enterprise and about Value Stream Management

The first article to mention the Scrum approach.

There is no one-size-fits-all, magic bullet for determining a sprint length that works well for every team. Originally, Scrum called for one-month sprints, but nowadays many teams have been successful with two-week or even one-week sprints. Choosing the right sprint length is about determining an appropriate stimulus-to-response cycle. In a sprint, the initial stimulus is the customer setting the priority of the stories. The response is the team building working software.

The Scrum Guide provided in HTML format on the web.

Product Discovery is the iterative process of reducing uncertainty around the problem space as a product team. Here's how to stay on course.

This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. Copyright © 1998-forever Ronald E Jeffries

Writing good user stories can be hard, however these ten tips will help you create powerful stories that direct product delivery.

XP teams have to manage stories and tasks. The INVEST and SMART acronyms can remind teams of the good characteristics of each.

In Scrum, the Prioritized Product Backlog is a single requirements document that defines the project scope by providing a prioritized list of features of t...

In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, ordering by priority is only one many techniques — and rarely the best one at that.

The Scrum Guide talks about an ordered backlog, not a prioritized one. While order and priority are related, they are not the same, and understanding the difference and why people focus on one over the other can help your team be more effective at delivering business value.

The planning fallacy leads us to underestimate how much time it will take us to complete tasks. To avoid the problem, adopt one of these estimation techniques.

Poker planning is an agile estimating and planning exercise that uses Planning Poker cards for consensus-based estimating in Scrum.

Some agile teams estimate using a fixed set of values based on the Fibonacci sequence. Learn the science behind this approach and why it works so well.