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

The Definition of Done

What does Done mean in the context of writing software features? Does it mean your code builds and runs on your computer? Does it mean testing has been performed? Does it mean the code has been checked in? What about documentation? What about operational readiness? These are all good questions, and the chances are that if you ask these questions to different people, you will get very different answers.

When we use a Kanban and/or a Sprint Board in Scrum, there is a column on the right with the title DONE. So, what does Done mean here? This is why we use a Definition of Done practice. The Definition of Done is a criterion agreed across the team and shared with others that should be met before any work items are considered complete by any team member. It is collaboratively created, maintained, and enforced by the team where non-functional and functional work that should be performed for each and every work item can be managed.

Earlier in this chapter, we...

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}