1. True. In traditional organizations, development is often tasked with creating changes to software, while operations is responsible for maintaining the stability of the target systems for these changes. Since changes inherently carry risk and may disturb stability, operations is often resistant to change.
2. False. While, in theory, it is possible to practice the different DevOps practices in isolation from on another, the real value comes from combining them. For example, continuous deployment without continuous integration and test automation does not only make very little sense; it is even dangerous to continuously deploy changes without the quality assurances that continuous integration and test automation offer.
3. The incorrect answer is number 4. DevOps is not a job title, but a cultural movement. Actually, creating a new DevOps team in between development and operations is often at loggerheads with the DevOps philosophy. Instead of two teams or departments with their separate goals, there are now three.
4. Fastlaning is an approach to expediting unplanned, high-priority work over planned work, all while maintaining a single sprint board for the whole team.
5. There are many definitions of DevOps. Some of the main elements that are frequently included are business value, end users, continuous deployment, automation, and collaboration.