The key outcome is the shared and documented understanding of your project's goals, vision and requirements

The PDMS Blueprint Discovery process is the best way to ensure you get the best return on your technology investment by ensuring everyone involved has an in-depth understanding of the goals and scope of your digital project.

It involves a short, but intense, period of research, investigations, analysis and planning to help clarify your goals – providing the most effective start to any software project.   It is a great way to help deal with the uncertainty which is present at the onset of any digital project and helps to avoid the ambiguities and misunderstandings that can lead to scope creep further down the line, and ultimately, wasted time and money.

Depending on the nature and complexity of your project, a discovery process will help you and all your various stakeholders understand the business context in which a project is being undertaken. Many digital projects are derailed by issues relating to change management or operational business challenges rather than the implementation of new technologies or platforms.

Who is involved?

It may seem obvious but the most important participant in the PDMS Blueprint discovery process is you!

To ensure successful outcomes, we will need input from some of your key stakeholders and your end users. We always recommend getting together in the same room to facilitate communication and to help develop relationships.

We will be seeking to answer the following questions:

  • What is the business objective?
  • What is the business context?
  • What does success look like?
  • How is success measured?
  • Who are the stakeholders?
  • Who are the service/solution users?
  • What are their needs?
  • What are the constraints?

Deliverables

After we have identified and gathered the key information with your stakeholders and end users, we will then spend time analysing the data and insights and finalise our recommendations.

At the end of the PDMS Blueprint Discovery process we will provide a detailed report. Typical outputs could include:

  • A problem definition (the business challenge/opportunity)
  • User/Customer journey mapping
  • A set of user stories
  • A description of the technical landscape
  • A description of constraints e.g. legacy systems, security, integrations
  • Identification of key risks and opportunities
  • A suggested project methodology and high-level plan
  • Budgetary considerations

We have a number of PDMS Blueprint process packages available which have been designed with flexibility in mind to meet the needs of different types of projects of various sizes and complexity.

If you’d like to find out how a PDMS Blueprint process could help get your digital project off to the best start, please get in touch with Cat Watt.