Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
DevOps Culture and Practice with OpenShift

You're reading from   DevOps Culture and Practice with OpenShift Deliver continuous business value through people, processes, and technology

Arrow left icon
Product type Paperback
Published in Aug 2021
Publisher Packt
ISBN-13 9781800202368
Length 812 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (5):
Arrow left icon
Noel O’Connor Noel O’Connor
Author Profile Icon Noel O’Connor
Noel O’Connor
Mike Hepburn Mike Hepburn
Author Profile Icon Mike Hepburn
Mike Hepburn
Ilaria Doria Ilaria Doria
Author Profile Icon Ilaria Doria
Ilaria Doria
Donal Spring Donal Spring
Author Profile Icon Donal Spring
Donal Spring
Tim Beattie Tim Beattie
Author Profile Icon Tim Beattie
Tim Beattie
+1 more Show less
Arrow right icon
View More author details
Toc

Table of Contents (30) Chapters Close

Preface Acknowledgements Section 1: Practices Make Perfect FREE CHAPTER
1. Introduction — Start with Why 2. Introducing DevOps and Some Tools 3. The Journey Ahead Section 2: Establishing the Foundation
4. Open Culture 5. Open Environment and Open Leadership 6. Open Technical Practices – Beginnings, Starting Right 7. Open Technical Practices — The Midpoint Section 3: Discover It
8. Discovering the Why and Who 9. Discovering the How 10. Setting Outcomes Section 4: Prioritize It
11. The Options Pivot Section 5: Deliver It
12. Doing Delivery 13. Measure and Learn Section 6: Build It, Run It, Own It
14. Build It 15. Run It 16. Own It Section 7: Improve It, Sustain It
17. Improve It 18. Sustain It Index
Appendix A – OpenShift Sizing Requirements for Exercises 1. Appendix B – Additional Learning Resources

The Definition of Ready

Jeff Sutherland, co-creator of the Scrum framework, called out that one of the main reasons that many Scrum projects fail is due to teams working on items that are simply not ready to be worked on. They are either too ambiguous, not understood by business and technical stakeholders, too big, or they lack ambiguity as to the scope of the item in question.

Many teams have chosen to adopt the practice of having a Definition of Ready to mitigate this risk. The Definition of Done practice has been popular with Agile teams for many years—we will explore that later in this chapter. The Definition of Ready has been less utilized. A good way to look at this, like every practice in the Open Practice Library, is as a tool that can be taken out of the toolbox to address a problem. If a team is struggling to get work done because of ambiguity and a lack of shared understanding before even starting it, adding a Definition of Ready may improve the team's success...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime