Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
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

Product type Book
Published in Aug 2021
Publisher Packt
ISBN-13 9781800202368
Pages 812 pages
Edition 1st Edition
Languages
Concepts
Authors (5):
Tim Beattie Tim Beattie
Profile icon Tim Beattie
Mike Hepburn Mike Hepburn
Profile icon Mike Hepburn
Noel O'Connor Noel O'Connor
Profile icon Noel O'Connor
Donal Spring Donal Spring
Profile icon Donal Spring
Ilaria Doria Ilaria Doria
Profile icon Ilaria Doria
View More author details
Toc

Table of Contents (30) Chapters close

Preface Acknowledgements Section 1: Practices Make Perfect
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

Conclusion

In this chapter, we focused on how we are going to deliver the outcomes set in the previous section.

Figure 11.36: Adding practices to navigate us through Options

We explored the User Story Mapping and Value Slicing practices and how we take all of the information captured in Discovery practices and push it through these tools. We also showed how using some helpful practices to look at the same information with slightly different lenses –Impact versus Effort Prioritization and How/Now/Wow Prioritization – can help improve Value Slicing. Where proposed feature areas would benefit from a deeper dive to understand the value, we recommended the Design Sprint as an option.

We showed how these practices drive the initial Product Backlog prioritized by value and how this produces a living, breathing artifact that will be subject to continuous Product Backlog Refinement as we gather more learning, feedback, and metrics for our delivery...

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 €14.99/month. Cancel anytime}