Published: 25 August 2011
Summary
Enterprise IT groups have started migrating to agile methodologies and are seeing good results. By performing requirements creation, development, and testing in parallel, development teams focus completely on business value. But agile only addresses half the problem that many groups face: Because agile leaves out operational staff, developers lose a crucial mechanism for feedback. Sean Kenefick shows how DevOps applies inherited agile principles of discipline, collaboration, and early feedback to tasks such as deployment, environment configuration, monitoring, and maintenance.
Included in Full Research
- Achieving Agility
- A Cultural Schism
- DevOps Defined
- Success Stories
- Adopting DevOps in Less-Than-Agile Environments
- The Cultural Ramifications of DevOps Team Integration
- Practice Makes Perfect
- Continuous Improvement
- Configuration as Code
- Automate Everything
- Use Production Tool Chains for Development
- Monitoring as a Testing Tool
- Strengths
- Weaknesses
- Evaluate a DevOps Strategy for Your Team
- Integrate Operational Staff on to Agile Cross-Functional Teams
- Teams Must Address Non-Functional Requirements as Part of the Development Process
- Place Configurations Under Version Control
- Consider Self-Service Provisioning Solutions
- Automate Whenever Possible
- Enforce Development Tool Chain Parity with Production
- Monitor Everything