Continuous Delivery and DevOps: A Quickstart guide

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" w...

(展开全部)

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

Paul Swartout has spent over 20 years working in IT. Starting out as a Junior Developer within a small software house, Paul has filled a number of roles over the years including Software Engineer, System Administrator, Project Manager, Program Manager, Operations Manager, and Software Development Manager. He has worked across a number of different industries and sectors—from su...

(展开全部)

Paul Swartout has spent over 20 years working in IT. Starting out as a Junior Developer within a small software house, Paul has filled a number of roles over the years including Software Engineer, System Administrator, Project Manager, Program Manager, Operations Manager, and Software Development Manager. He has worked across a number of different industries and sectors—from supply chain, through manufacturing, education, and retail to entertainment—and within organizations of various sizes from start-ups to multi-national corporates. Paul is passionate about software and how it is delivered. Since first encountering "agile" almost a decade ago he has been committed to the adoption and implementation of agile techniques and approaches to improve efficiency and output for software development teams. Until very recently Paul headed up the team responsible for delivering continuous delivery solutions into the Nokia Entertainment business. Paul and his team spent the best part of a year changing the default ways of working and driving the adoption of CD and DevOps as the de facto mode of delivery for Nokia Entertainment products. Paul lives in a seaside town in the southwest of the UK with his wife, daughters, and two small yapping things. Paul is a software development manager at Nokia and is based within the Nokia entertainment team in Bristol in the UK. The entertainment team is responsible for designing, building, and running the entertainment services and solutions for Nokia customers around the globe. These products include Nokia Music, Nokia Reading, and Nokia TV.

Preface
Chapter 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
· · · · · · (更多)

Preface
Chapter 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
Preface
Up
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
Up
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
Up
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
Up
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
Up
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
Up
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
Up
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
Up
Index
· · · · · · (收起)