DevOps for developers / Michael Hüttermann.
DevOps for Developers delivers a practical, thorough introduction to approaches, processes and tools to foster collaboration between software development and operations. Efforts of Agile software development often end at the transition phase from development to operations. This book covers the deliv...
Saved in:
| Online Access: |
Full Text (via Skillsoft) |
|---|---|
| Main Author: | |
| Format: | eBook |
| Language: | English |
| Published: |
[Berkeley, CA] :
Apress,
2012.
|
| Series: | Expert's voice in Web development.
|
| Subjects: |
Table of Contents:
- Title Page; Copyright Page; Contents at a Glance; Table of Contents; About the Author; About the Technical Reviewers; Acknowledgments; Introduction; Audience; What You Will Learn; Book Structure; Part I: Fundamentals; Chapter 1: Beginning DevOps for Developers; The Definition of DevOps; Influences and Origins; Development and Operations in Conflict; Broaden the Usage of Agile; Views of DevOps; What DevOps Is NOT; Roles and Structures; DevOps and Tool Suites; Structure of This Book; Conclusion; Chapter 2: Introducing DevOps; Traditional Project Settings; Agile Project Settings.
- Blame Game: Dev vs. OpsConflicts During Deployment; Conflicts After Deployment; Conflicts About Performance; Operations as Bottleneck; Horizontal Optimization; Operations and ITSM; DevOps to the Rescue; The Essence of DevOps; Values and Goals; Processes; Tools; Conclusion; Chapter 3: Building Blocks of DevOps; Measurement and Metrics; Traditional Use of Metrics; Agile Approach to Metrics; Definition of Done; Broken Agile Metrics; Qualify Changes; Improving Flow of Features; Cycle Time; Lead Time, Takt Time, and Throughput; Improve and Accelerate Delivery; Automatic Releasing.
- Pitfalls of AutomationLaw of Marginal Costs; Verb/Noun Mistake; Paradox of Automation; Irony of Automation; Automation Good Practices; Apply Releases Incrementally and Iteratively; Apply Monitoring, Thoroughly; Decoupled Deployment and Release; Branch by Abstraction; Feature Toggles; Dark Launching; Blue-Green Deployment; Conclusion; Part II: Metrics and Measurement View; Chapter 4: Quality and Testing; What Is Quality?; Leading and Supporting Attributes; Measurable Attributes; Reliability on Context; Key Aspects of Quality; Patterns for Improving Quality; Internal and External Quality.
- Use Scenarios to Describe QualityQuality Is an Inherent Part; QA and Making Quality Visible; Degeneration: Faults and Failures; Test Automation Mix; Unit Testing; Service Tests; UI Testing; Errors in Test Strategy; Acceptance Criteria; Inject Quality Gates; Example of a Quality Gate; Conclusion; Chapter 5: Introduce Shared Incentives; War Study: Magic Kingdoms; What Is a Team?; Goals and Working Agreements; Motivation; Becoming a Team; Tuckman's Stages of Group Development; Facilitator and Caretakers; Success Stories; Aaron Nichols: DevOps at Rally Software.
- Architecture Council and Weekly Sync MeetingsRetrospectives; Embracing Change and Experimenting; Shared Core Values; Lisa Crispin: DevOps, Naturally; Shared Responsibilities; Brainstorming and Experiments; Quality as a Shared Goal; Conclusion; Part III: Process View; Chapter 6: Gain Fast Feedback; The DevOps Area Matrix; Extend Development to Operations; Extend Operations to Development; Embed Development into Operations; Embed Operations into Development; Starting with Kanban; Introducing Kanban; Five Core Properties; An Example Kanban Board for DevOps; Example Use Case.