Starter Checklist for Agile DevOps Needs in Your Scrum Sprint

Scrum teams can benefit from adding DevOps tasks to their scrum sprints.  By recognizing and completing DevOps tasks in sprint teams can be more prepared for shipping code and release faster in an Agile way.

In speaking with scrum teams preparing to add DevOps tasks to their scrum sprints I've been asked about what types of tasks might be commonly expected or what questions are good to ask.

This is an intro checklist/discussion starter to help get some DevOps tasks and topics on the table during Sprint Planning, please build on this list and make it your own depending on your customer needs.

1.) What are the environmental resource needs of the Sprint's output on production?  Memory? Compute sizing? Mirroring? 

2.) What are we doing in this Sprint that might impact other services?  Are we suddenly requiring more database connections? Are the number of connections to other services about to increase? Are we putting more load on a shared ESB (Enterprise Service Bus)?

3.) Have we measured how this sprint output affects lower environments systems incl. memory, connections etc.? Can we extrapolate lower environment effects to determine the affects on production?

4.) Can we measure how this sprint output is affected by load, latency or non-happy path use by testing in a lower environment? 

5.) Are our lower environments accurate representations os set-up, OS configurations, plug-ins and libraries in Productions?

6.) Are third party or other internal services accurately represented in our lower environments so that we can observe the impact of the sprint output on those services?

7.) Are there new logging or instrumentation requirements that we need to account for with this sprint?

8.) Have we advised reliability team or DevOps team (if they perform reliability tasks) of any specific monitoring queries, dashboards or other Service Level Indicators (SLI) for this sprint output?

9.) Has the Product Owner determined a Service Level Objective (SLO) for the services in the sprint? Is the SLO attainable with the resources the new code will have in Production? Is there a similar service functioning in Production now that the product owner can use to estimate a realistic SLO expectation?

10.) Are outage, downtime, issues rules for new services produced by the sprint ready? Triggers sent to PagerDuty or a similar service? Instructions for remediation with triggers? Are thresholds set that align with the SLIs?