A planned release
Turn a feature list into a defined version with acceptance criteria and a manageable release sequence.
Prepare a software product for release, from the features still to build to the materials needed for distribution and handover. Agree the release scope, responsibilities and publishing route before implementation.

Possible starting points for discussion. The final scope depends on your requirements.
Turn a feature list into a defined version with acceptance criteria and a manageable release sequence.
Clarify the intended channels, packaging requirements and responsibilities for accounts, licences and approvals.
Identify the changes and documentation needed for a new release or a different audience.
Deliverables, responsibilities and timing are agreed for each engagement. The following is a starting point for defining the scope.
Review the product, outstanding requirements and what belongs in the agreed release.
Implement the agreed changes and review them against the functional requirements.
Prepare the agreed build, release notes, usage documentation and distribution materials.
Coordinate the agreed release steps and document ownership, access and future responsibilities.
The final deliverables are agreed before work begins. Depending on the scope, they may include:
Tell us what you need. We can begin with an outline and work through the details together.
Discuss your project