Index
A
- abstraction layers
- about / Layers of abstraction
- ACME CD project
- goal, communicating / Setting and communicating goals and vision
- ACME systems
- issues, troubleshooting / Elephant in the room
- simple manual solutions / When a simple manual process is also an effective tool
- deployment transaction model / Failure during the evolution
- ACME systems Version 1.0
- about / ACME systems Version 1.0
- deliver / ACME systems Version 1.0
- development/operations teams and management team, conversation / ACME systems Version 1.0
- software delivery process flow version 1.0 / Software delivery process flow Version 1.0
- ACME systems Version 2.0
- about / ACME systems Version 2.0
- working / ACME systems Version 2.0
- issues / ACME systems Version 2.0
- software delivery process flow Version 2.0 / Software delivery process flow Version 2.0
- R&D and Operations teams, conversation / Software delivery process flow Version 2.0
- ACME team / A few brave men and women
- ACME systems Version 3.0
- about / ACME systems Version 3.0
- software delivery process flow Version 3.0 / Software delivery process flow Version 3.0
- advice, CD and DevOps
- seeking / Seeking advice from others
- agile terminology
- product owner / Some tried and tested techniques
- Scrum master / Some tried and tested techniques
- feature / Some tried and tested techniques
- story / Some tried and tested techniques
- backlog / Some tried and tested techniques
- task / Some tried and tested techniques
- time boxed / Some tried and tested techniques
- architectural approaches, CD and DevOps
- about / Architectural approaches
- component based architecture / Component based architecture
- abstraction layers / Layers of abstraction
- automated provisioning
- about / Automated provisioning
- automation
- implementing / Automated build and testing
B
- backlog
- about / Some tried and tested techniques
- blame culture
- business change project
- implementing / A business change project in its own right
C
- CD and DevOps
- tools / Engineering best practice
- fundamentals, software engineering / Engineering best practice
- source control solution / Source control
- technical challenges / Continuous integration
- architectural approaches / Architectural approaches
- environments, using / How many environments is enough?
- monitoring / Monitoring
- open dialogue / Openness and honesty
- honest dialogue / Openness and honesty
- courageous dialogue / Courageous dialogue
- physical environment / The physical environment
- collaboration, encouraging / Encouraging and embracing collaboration
- collaboration, embracing / Encouraging and embracing collaboration
- accountability, fostering from grass roots / Fostering innovation and accountability at grass roots
- innovation, fostering from grass roots / Fostering innovation and accountability at grass roots
- blame culture / The blame culture, Blame slow, learn quickly
- trust-based relationships, building across organizational boundaries / Building trust-based relationships across organizational boundaries
- rewards / Rewarding good behaviors and success, The odd few
- people, incentivizing / Recognizing how different teams are incentivized can have an impact
- change, embracing / Embracing change and reducing risk
- risk, reducing / Embracing change and reducing risk
- proof of the pudding methodology / Changing people's perceptions with pudding
- high degree of visibility / Being highly visible about what you are doing and how you are doing it
- potential issues / What are the potential issues you need to look out for?
- streaming / Streaming
- exit stage left / Exit stage left
- wider vision / Wider vision
- CD and DevOps effectiveness , measuring
- environments stability, measuring / Measuring stability of the environments
- automated tests, incorporating / Incorporating automated tests
- automated tests and system monitoring, combining / Combining automated tests and system monitoring
- system monitoring / Real-time monitoring of the software itself
- CD effectiveness, measuring / Measuring effectiveness of CD
- CD and DevOps implementation
- goals and vision, setting / Setting and communicating goals and vision
- vocabulary and language, standardizing / Standardizing vocabulary and language
- business change project, implementing / A business change project in its own right
- dedicated team, benefits / The benefits of a dedicated team
- evangelism / The importance of evangelism
- cost, understanding / Understanding the cost
- advice, seeking / Seeking advice from others
- CD and DevOps landscape / What's next?
- CD tooling
- about / CD tooling
- automated provisioning / Automated provisioning
- no-downtime deployments / No-downtime deployments
- change/transition curve, potential issues
- about / The change curve
- diagrammatic representation / The change curve
- CI tools
- about / Continuous integration
- closed session investigations
- about / Openness and honesty is the key
- component based architecture
- about / Component based architecture
- consumer/provider relationship
- maintaining / Never break your consumer
- continuous delivery (CD)
- continuous integration
- about / Standardizing vocabulary and language, Continuous integration
- advantages / Continuous integration
- implementing / Continuous integration
- contribute
- about / Include (almost) everyone
- costs, CD and DevOps
- about / Understanding the cost
- courage
- courageous dialogue
- about / Courageous dialogue
D
- dedicated team
- benefits / The benefits of a dedicated team
- Definition of done(DOD)
- Deploy
- deployment transaction model
- about / Failure during the evolution
- diagrammatic representation / Failure during the evolution
- determination
- development/operations teams
- and management teams, conversation / ACME systems Version 1.0
- DevOps
- dissenters, potential issues
- about / Dissenters in the ranks
E
- effective engineering
- measuring / Measuring effective engineering best practice
- engaged
- about / Include (almost) everyone
- environments
- using, in CD and DevOps / How many environments is enough?
- same binary, using / Using the same binary across all environments
- developing, against / Develop against a like live environment
- evangelism
- about / The importance of evangelism
- rules / The importance of evangelism
F
- failing fast and often
- about / Fail fast and often
- feature
- about / Some tried and tested techniques
- fundamentals, software engineering
- about / Engineering best practice
- source control / Source control
- small frequent code changes / Small, frequent, and simple changes
- consumer/provider relationship, maintaining / Never break your consumer
- peer working / Open and honest peer working practices
- failing fast and often / Fail fast and often
- automated build and testing / Automated build and testing
- continuous integration / Continuous integration
G
- geographically diverse teams, potential issues
- about / Geographically diverse teams
- goal and vision
- about / Setting and communicating goals and vision
- setting / Setting and communicating goals and vision
- communicating / Setting and communicating goals and vision
H
- high degree of visibility
- honest dialogue
- about / Openness and honesty
I
- incentivizing
- issues, ACME systems
- issues, accepting/ignoring / Elephant in the room
- closed session investigation, running / Openness and honesty is the key
L
- live environment
- developing against / Develop against a like live environment
- about / Develop against a like live environment
- live environment, ACME systems 3.0
- diagrammatic representation / Develop against a like live environment
M
- monitoring
- about / Monitoring
N
- no-downtime deployments
- about / No-downtime deployments
O
- open dialogue
- about / Openness and honesty
P
- peer working practices
- potential issues, CD and DevOps
- dissenters in ranks / Dissenters in the ranks
- change curve / The change curve
- outsiders / The outsiders
- corporate guidelines / Corporate guidelines, red tape, and standards
- red tape / Corporate guidelines, red tape, and standards
- standards / Corporate guidelines, red tape, and standards
- geographically diverse teams / Geographically diverse teams
- failure during evolution / Failure during the evolution
- unrepeatable processes / Processes that are not repeatable
- recruitment / Recruitment
- product owner
- about / Some tried and tested techniques
- proof of the pudding methodology
R
- R&D
- and operations teams, conversation / Software delivery process flow Version 2.0
- Release
- retrospectives
- about / Using retrospectives
- using / Using retrospectives
- timeline game / The timeline game
- StoStaKee / StoStaKee
- rewards
S
- Scrum master
- about / Some tried and tested techniques
- simple manual solutions
- small frequent code changes
- software code metrics, measuring
- code versus comments / Code versus comments
- code complexity / Code complexity
- code coverage / Code coverage
- commit rates / Commit rates
- unused/redundant code / Unused/redundant code
- duplicate code / Duplicate code
- adherence to coding rules and standards / Adherence to coding rules and standards
- source control solution
- about / Source control
- story
- about / Some tried and tested techniques
- StoStaKee game
- about / StoStaKee
T
- task
- about / Some tried and tested techniques
- technical challenges, CD and DevOps
- about / Continuous integration
- Test driven development (TDD)
- about / Fail fast and often
- time boxed
- about / Some tried and tested techniques
- timeline game
- about / The timeline game
V
- value stream mapping
- about / Value stream mapping
- vocabulary and language
- standardizing / Standardizing vocabulary and language