Scenario 2 Quiz – Organizing DevOps
Question 1:
What could the company do differently to avoid having to spend time coordinating across teams?
- Organize the teams around business domains instead of around technologies.
- Have a Dev team, an Ops team, and a DevOps team.
- Hire more people to process tickets in the system.
- Add a new “coordination team.”
Answer: Organize the teams around business domains instead of around technologies.
Explanation: This approach minimizes cross-team coordination by aligning teams around business needs and product goals, leading to better efficiency.
Question 2:
What could have been done to avoid the missing schema change?
- Avoid bug fixes to the master branch.
- Use automated deployment.
- Prevent developers from making schema changes.
- Routinely check for any unapplied schema updates.
Answer: Use automated deployment.
Explanation: Automated deployment ensures all updates, including schema changes, are consistently applied, reducing errors and omissions.
Question 3:
Should the development team have merged the development branch back into the master branch sooner?
- When the code was complete, it should have been merged into the master branch.
- Someone should have merged their own pull request instead.
- The team was correct to have a long-lived branch for every issue.
- It would have been more effective to make a mono repo instead.
Answer: When the code was complete, it should have been merged into the master branch.
Explanation: Merging frequently ensures that the main branch stays up to date, preventing major conflicts down the line.
Question 4:
What could the development team have done differently to avoid the merge conflicts at the end of the month?
- Prevent code drift through better coordination across the team.
- Provide Roopa with training to resolve merge conflicts.
- The team could have spent time designing the system so there were no conflicts.
- Use Continuous Integration to merge more frequently.
Answer: Use Continuous Integration to merge more frequently.
Explanation: Frequent merges through CI help detect and resolve conflicts early, making them easier to manage.