A structured mechanism ensures individual business needs and wants are clearly documented.

Relationship rules exist between individual business needs and wants to aid the capturing and tracing of items with Stakeholders.

A logical tree structure clearly shows the relationship between business needs and Stakeholders, which can easily be transformed into individual Stakeholder requirements using the user-friendly editing tool.

The documenting of Stakeholder requirements aid Product Owners and Business Analysts who are responsible for the documenting of the project's entire library of unique Epics and Stories.

The ability to focus on a single Stakeholder and their unique requirements, the Product Owner and Business Analysts can quickly get on with the task of developing the Product Backlog.

With an ever-growing library of standardised workpacks, each containing the following data an overall Sprint roadmap is quickly established;

- coding instructions

- research and documentation

- staffing and administration

- testing options

- sourcing options

A wealth of supporting material (e.g. completion estimates (hours), references to support material and suggested 3rd party products) is also included.

Efficiently converting user stories into implementation tasks forms the majority of the work undertaken by the Product Owner and Business Analysts prior to Sprint Planning.

The rapid and accurate definition of achievable Epics and Stories is made possible because of the baseline set of tasks that make up the standardised workpack. Special attention is given to customising these recommended tasks and their associated supporting material to meet the unique requirements of the project.

As a result of the work performed prior to the Sprint Planning session, a far greater set of documented Epics and Stories are available. With Monetical for CMS these sessions spend far less time elaborating Stories, instead more time is focused on implementation options and developing a far more accurate estimate for completion.

The output from Sprint Planning sessions, i.e. the Sprint Objectives sheet is comprehensive due to the fact that all the individual tasks are well documented, assigned to individuals, prioritised and all the currently available supporting material is provided.