Corporate Revolutionary Library

Featuring Sidney Dekker, Steven Spear, and Richard Cook.Convergence of Safety Culture and Lean: Lessons from the LeadersDOES17 San FranciscoDevOps Enterprise...

In the Scrum framework, there are three "core roles," which are mandatory for producing the product, are committed, and ultimately responsible for each sprint & the initiative's success. These roles are Product Owner, the Agile Team, and Scrum Master.

Product vision statements are concise, evolving, inspirational descriptions of a product's long-term goals and future state. This guide will explain how to develop your product vision statement and what to look for in a good one.

Why create a team working agreement? A team working agreement provides an agreed upon set of guidelines for a Scrum Team to follow, so everyone understands what is expected as they work together in pursuit of delivering value. A team can use a working agreement to help them work toward self-management.

Become a Cucumber expert at your own pace with free online courses. Attend interactive in-person training, tailored for your needs. Learn more and get started.

Improve your CQ with the Cultural Intelligence Center. Get research-based, innovative solutions for assessing, predicting & improving cultural intelligence here!

Culture Code: Creating a Company You Love - Download as a PDF or view online for free

Technical debt is talked about quite a bit in terms of DevOps and continuous delivery, but Culture debt is something to be considered as well

Search the case studies and videos to find out how top companies and government agencies are successfully putting SAFe to work.

Read writing about Data in Trainline’s Blog. Trainline’s Blog: Meet the team behind Europe’s leading train and bus app.

A metrics-oriented mindset is key to ensuring that DevOps initiatives deliver results. This research identifies metrics that I&O leaders can use from a general perspective to track DevOps teams' progress toward business goals, identify areas for improvement and promote collaborative culture.

The adoption of IT technologies has increased exponentially over the last few decades. Nowadays, the need to create quality web applications while

What is a DEEP Backlog? Learn more about what DEEP backlog means and other agile terminology in our agile product management glossary.

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

marked by ready ability to move with quick easy grace; having a quick resourceful and adaptable character… See the full definition

Having a Definition of Ready means that stories must be immediately actionable. The Team must be able to determine what needs to be done and the amount of work required to complete the User Story or PBI.

Welcome to Defra Digital – see blog posts

You don’t have to decrease quality to deliver at speed

Deliveroo engineering blog

Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible, serving us without drawing attention to itself. Bad design, on the other hand, screams out its inadequacies, making itself very noticeable. —Don Norman, The Design of Everyday Things Design Thinking It goes beyond the traditional focus on the features and functions of a proposed product. Instead, it emphasizes understanding the problem to beRead more

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.

DevOps.com has the largest collection of original content related to DevOps on the web and one of the top result for DevOps-related search terms.

While working on the Devops Cookbook with my fellow authors Gene Kim,John Willis,Mike Orzen we are gathering a lot of “devops” practices. For some time we struggled with structuring them in the book. I figured we were missing a mental model to relate the practices/stories to. This blogpost is a first stab at providing a structure to codify devops practices. The wording, descriptions are pretty much work in progress, but I found them important enough to share to get your feedback.

DevOps at scale: what we did, what we learned at Societe Generale - Download as a PDF or view online for free

DevOps At Target: Year 3 Heather Mickman, Sr. Director Target Technology Services, Target DevOps at Target: journey to microservices and cloud native architecture DOES16 San Francisco DevOps Enterprise Summit https://events.itrevolution.com/us/