In a nutshell, Scrum requires a Scrum Master to foster an environment where:
- A Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
DevOps vs. Scrum
- With DevOps, you deploy code in production at the end of each iteration (sprint), whereas with Scrum, your goal is to only prepare shippable code at the end of each iteration
- With DevOps, test automation and continuous software integration which are prerequisites of continuous software delivery are in the DNA of software development practices, whereas with Scrum, software delivery is an afterthought that must be planned and operated by people who are totally out of software development practices.
- With DevOps, projects are oriented on products and services who create business value for organization, whereas Scrum does possess no maturity to contribute business results.
- With DevOps, all engineers in your team are concerned about quality of service (quality of software), excellence in operations, whereas with Scrum, software quality assurance and operations are job of somebody else.
- DevOps contributes how you should architect your software to enable quality and continuous deliverability, whereas Scrum has no support to build your software with correct architecture.
- DevOps focuses on an end-to-end Software Engineering Organization to enable amazing business results, whereas Scrum is only concerned about software developers.