In the agile world, it’s important to remember that planning and documentation are still important and serve a purpose. While agile promotes “working software over comprehensive documentation,” it doesn’t say ignore documentation as much as we’d all often like to think. When developing a working DevOps pipeline, it is important to understand what your quality gates are, what thresholds you expect, and where you expect these to be. A well-documented test plan should inform the pipeline, and provide information and details as to what constitutes a working code. Too often this DevOps work is done out of sync with Testers, which then either means quality definitions don’t line up, or additional re-work has to be put in to align software confidence goals.
I recently gave an Ignite talk, 20 slides in 5 minutes, discussing exactly this, giving some tips and pointers:
