Estimate and schedule documentation work

For each pillar/domain, the software development is managed in a separate DevOps project.
The product owner provides:

• A documentation epic for each pillar/domain.
• In this epic, a documentation feature for each of the pillar/domain products.

For each product increment, the technical writer creates a separate product backlog item.

For each product backlog item, the technical writer creates the related work breakdown structure and estimates for the documentation work. So, the documentation work can be scheduled/picked up in the sprints of the related product team.

The product increment document work breakdown is created:

• Based on the product increment release notes.
• In consultation with the product owner where needed.

To set up documentation tasks in DevOps, it is best practice to:

• Copy release note section content to the related task.
• Add a textual reference to the related release notes section.
• If already clear, make notes on what must be done/changed/added to the documentation and where this must be done in the documentation.

Of course, both the Budget (which is the estimate) and Remaining hours must be entered. On estimations, these two values must be the same.

Product management, in consultation with technical writers and product owners, prioritizes the overall documentation work.

Usually, prioritizing the documentation work is done once per product increment. Preferably, prioritizing is done before or early in the product increment.