Continuous Delivery and DevOps: A Quickstart guide
eBook:
$14.99
Formats:
Formats:
$12.74
save 15%!
save 15%!
Print + free eBook + free PacktLib access to the book:
$39.98
Print cover: $24.99
$24.99
save 37%!
save 37%!
Free Shipping!
UK, US, Europe and selected countries in Asia.
| Also available on: |
|
- Real world and realistic examples of how to go about implementing continuous delivery and DevOps
- Learn how continuous delivery and DevOps work together with other agile tools
- An honest and open guide to consistently shipping quality software quickly
Book Details
Language : EnglishPaperback : 154 pages [ 235mm x 191mm ]
Release Date : November 2012
ISBN : 1849693684
ISBN 13 : 9781849693684
Author(s) : Paul Swartout
Topics and Technologies : All Books, Architecture & Analysis
Table of Contents
PrefaceChapter 1: Evolution of a Software House
Chapter 2: No Pain, No Gain
Chapter 3: Plan of Attack
Chapter 4: Tools and Technical Approaches
Chapter 5: Culture and Behaviors
Chapter 6: Hurdles to Look Out For
Chapter 7: Measuring Success and Remaining Successful
Index
- Chapter 1: Evolution of a Software House
- ACME systems Version 1.0
- Software delivery process flow Version 1.0
- ACME systems Version 2.0
- Software delivery process flow Version 2.0
- A few brave men and women
- ACME systems Version 3.0
- Software delivery process flow Version 3.0
- Summary
- Chapter 2: No Pain, No Gain
- Elephant in the room
- Ground rules
- Openness and honesty is the key
- Include (almost) everyone
- Some tried and tested techniques
- Value stream mapping
- Using retrospectives
- The timeline game
- StoStaKee
- Summary
- Chapter 3: Plan of Attack
- Setting and communicating goals and vision
- Standardizing vocabulary and language
- A business change project in its own right
- The benefits of a dedicated team
- The importance of evangelism
- The courage and determination required throughout the organization
- Understanding the cost
- Seeking advice from others
- Summary
- Chapter 4: Tools and Technical Approaches
- Engineering best practice
- Source control
- Small, frequent, and simple changes
- Never break your consumer
- Open and honest peer working practices
- Fail fast and often
- Automated build and testing
- Continuous integration
- Architectural approaches
- Component based architecture
- Layers of abstraction
- How many environments is enough?
- Using the same binary across all environments
- Develop against a like live environment
- CD tooling
- Automated provisioning
- No-downtime deployments
- Monitoring
- When a simple manual process is also an effective tool
- Summary
- Chapter 5: Culture and Behaviors
- Open, honest, and courageous dialogue
- Openness and honesty
- Courageous dialogue
- The physical environment
- Encouraging and embracing collaboration
- Fostering innovation and accountability at grass roots
- The blame culture
- Blame slow, learn quickly
- Building trust-based relationships across organizational boundaries
- Rewarding good behaviors and success
- The odd few
- Recognizing how different teams are incentivized can have an impact
- Embracing change and reducing risk
- Changing people's perceptions with pudding
- Being highly visible about what you are doing and how you are doing it
- Summary
- Chapter 6: Hurdles to Look Out For
- What are the potential issues you need to look out for?
- Dissenters in the ranks
- The change curve
- The outsiders
- Corporate guidelines, red tape, and standards
- Geographically diverse teams
- Failure during the evolution
- Processes that are not repeatable
- Recruitment
- Summary
- Chapter 7: Measuring Success and Remaining Successful
- Measuring effective engineering best practice
- Code versus comments
- Code complexity
- Code coverage
- Commit rates
- Unused/redundant code
- Duplicate code
- Adherence to coding rules and standards
- Where to start and why bother?
- Measuring the real world
- Measuring stability of the environments
- Incorporating automated tests
- Combining automated tests and system monitoring
- Real-time monitoring of the software itself
- Measuring effectiveness of CD
- Inspect, adapt, and drive forward
- Are we there yet?
- Streaming
- Exit stage left
- Rest on your laurels (not)
- Wider vision
- What's next?
- Summary
Paul Swartout
This book presents a very nice overview of how to introduce continuous delivery (CD) into an organization and what a DevOps team actually does. Its primary strength is its broad picture; it doesn't neglect the fact that an introduction of continuous delivery must be preceded and accompanied by lots and lots of information and marketing.
- Complete book review on this page, by Alexander Tarnowski
Submit Errata
Please let us know if you have found any errors not listed on this list by completing our errata submission form. Our editors will check them and add them to this list. Thank you.
Sorry, there are currently no downloads available for this title.
Frequently bought together
+
=
50% Off
the eBooks
the eBooks
Buy both these recommended eBooks together and get 50% off the total price
- Determine the problems and pain points within a product delivery process
- Tools and techniques to understand the root causes of the problems and pain points within a software delivery process
- Define and measure the success of implementing Devops and continuous delivery
- Understand the human elements to continuous delivery and DevOps and how important they are
- Avoid the traps, pitfalls and hurdles you’ll experience as you implement continuous delivery and DevOps
- Monitor and communicate the relative success of DevOps and continuous deliver adoption
For a while now, there has been a buzz around the IT industry regarding continuous delivery and DevOps. This book will provide you with some background information into these two new kids on the block and how they can help you to optimize, streamline and improve the way you work and ultimately how you ship quality software.
"Continuous Delivery and DevOps: A Quickstart guide" will provide you with a clear and concise insight into what continuous delivery and DevOps are all about, how to go about preparing for and implementing them and what quantifiable business value they bring. Included within are some tricks and trips based upon real world experiences which may help you reduce the time and effort needed if you were to go it alone.
In this book, you will be taken through a journey of discovery starting with real world successes, how you should prepare, plan for and implement CD and DevOps and what the pitfalls are along the way
We will start looking at the evolution of a typical software house from fledgling start-up through the growing pains that comes with global success to a best of both worlds. We’ll delve into the many aspects of what they did to complete this evolution covering topics such as how they realized there was a problem to solve, how they set about preparing for and implementing continuous delivery and DevOps and what tools, techniques and approaches they used along the way – some technical and some not so. If you work within an organization that delivers software, you will be able to plot where you are on the evolutionary scale, understand where you need to do to be more effective, cherry pick the tools, techniques and approaches that work for you and realize the best of both worlds.
"Continuous Delivery and DevOps: A Quickstart guide" will provide you with the background and information you need to realize the benefits within your own business
This book is both a practical and theoretical guide detailing how to implement continuous delivery and Devops to consistently ship quality software quickly.
Whether you are a freelance software developer, a system administrator working within a corporate business, an IT project manager or a CTO in a startup you will have a common problem; regularly shipping quality software is painful. It needn't be. This book is for anyone who wants to understand how to ship quality software regularly without the pain.
