A product has many components to be delivered to the customer. The documentation is one of these components. Although the documentation is often developed with the product features, it is also often difficult to get both right at the same time. How can we handle required updates to the documentation if there are no required changes to the product?

The product and the documentation of the product should be in different release cycles.

The reason for this separation is that the documentation responds to different forces than the product. While it is true that a new feature probably needs also to be documented in the user guide, bug fixes do not necessarily do. Feedback from users may demand that the user guide needs to be updated to make the information easier to understand. Maybe there is an error in the documentation that is not related to the product. Therefore there are situations where the product needs to be released, but not the documentation. And on the other side, the documentation needs to be released, but not the product.

So it is beneficial to have the two release cycles separated.