What should be done for technical documentation if the technical writer is on vacation during the Sprint?

The Development Team handling the documentation themselves during the absence of the technical writer is a pragmatic approach. In Scrum, the Development Team is cross-functional, meaning that all members are collectively responsible for delivering a potentially releasable product increment by the end of each Sprint. This includes not just coding but also ensuring that necessary documentation is completed.

When the designated technical writer is unavailable, the Development Team can step in to maintain continuity and meet the Sprint goals. This fosters a collaborative environment and enables the team to adapt to changes swiftly. It ensures that documentation does not fall behind or become a bottleneck in the development process, allowing for a more flexible adherence to the Sprint commitments.

By taking on documentation responsibilities, the Development Team also gains valuable insights into the project and enhances their understanding of the product. This aligns with Scrum principles of self-organization and commitment to team accountability, enabling the team to support each other and facilitate ongoing learning and improvement.