A project team consistently delivers value-added features each sprint but is neglecting documentation. How should the project manager ensure documentation stays current?

Making documentation a standard part of the Definition of Done (DoD) ensures that documentation is completed concurrently with feature development, promoting a "done increment" that is truly ready for use. This integrates documentation into the team's regular workflow, preventing it from becoming a separate, neglected task. Assigning a dedicated resource might create a bottleneck or disconnect between the feature development and documentation, potentially leading to inaccuracies. Creating a specific sprint for documentation delays its completion and contradicts the agile principle of delivering working software frequently. Handling documentation after feature delivery is complete is a waterfall approach that leads to outdated documentation and technical debt, undermining agile principles of continuous delivery and readiness.