Agile development is about productivity. While traditional waterfall methodologies support long-term development projects with fixed feature sets, Agile strives to create useful code in constant cycles, providing an ever-evolving product that generates value with every iteration. DevOps builds on Agile by pairing development and operations teams and adding a healthy dose of automation.
Agile and DevOps are powerful tools, helping development put more usable, valuable software in the hands of their users more quickly, but that speed has a downside. Traditional documentation and support processes build for waterfall simply cannot support agile workflows. By the time businesses create or update documentation, the product has moved on. This results in inaccurate, incomplete, and often unusable documentation that provides little value to support staff, end-users, or developers.
If traditional documentation is not going to provide support, something has to help organizations understand what they have, how it’s configured, and how to plan for the future. To meet those needs, a modern, “continuous documentation” is beginning to emerge, built on the same pillars of efficiency and automation as the DevOps methodology it supports. Modern documentation is fundamentally different from traditional documentation in that its creation requires almost no human interaction, but the creation and management of the process that creates it requires a substantial amount of planning.
This Gigaom Research webinar will discuss the technologies that will enable this change and the applications that will drive adoption. We will also evaluate the long-term future and our role in it, and provide advice to technologists and manufacturers looking to participate in the coming era of device intelligence. Join Gigaom Research and VictorOps for “Documenting DevOps: Agile, Automation, and Continuous Documentation,” a free analyst webinar on Wednesday, February 18, 2015, at 10 a.m. PT.
What Will Be Discussed
- What is the purpose of documentation, and how has it been used in traditional software development?
- How do the efficiencies and procedures of Agile and DevOps break traditional documentation?
- How should businesses reimagine modern documentation to provide the same benefits as traditional documentation?
- What is the role of automation and tooling in modern documentation?
- How should IT create a system of record for automated documentation?
- How should IT approach ongoing development and tuning of a documentation system?
Who Should Attend
- CIOs and CTOs
- Application Developers & Architects
- QA Staff
- Operations and Support Staff
- Project Managers