There's a lot of effort and different methodologies involved in running a project well. Solverboard Projects helps by providing a single workspace giving you and your team the confidence that you'll achieve your project outcomes.


The starting point is to understand the platform project lifecycle (these are platform phases and different to your organisation's project stages). There are three project status phases in running a project on Solverboard:

  • The Planning Phase
  • The Live Phase
  • The Realising Phase 

Project phases diagram

The project phases on Solverboard with associated processes (click to enlarge)

The Planning Phase

After the creation of the project, the planning phase purpose is to provide a detailed understanding of the project's aim, objective/s and scope. After forming a project team, the team can then go on to construct detailed plans including work assignments, risk analysis and project cost estimating amongst others. The process of planning is iterative until a tolerable level of understanding and uncertainty is achieved.


Scrutinising and maturing the business case throughout this process, the project team's overarching objective is to make sure that the project business case remains viable, and if so, the project can proceed to the Live Phase.


The Live Phase

This phase is concerned with the execution of the project. The teams do their work, completing their tasks and producing project outputs. Ideally, the project will deploy releases to the end-user serving to capture feedback and to start to realise benefits early as possible in the project lifecycle. Through project direction, the project board or steering group manage the stage boundaries determining if the project should proceed to the next stage, be completed or stopped. In Solverboard, these stages are customisable to your organisation's project framework. The end of the Live Phase is when the project has delivered its objectives and marked as 'project complete'.


The Realising Phase

Typically, at the end of the Live Phase the project would have delivered its "product", and the project deemed complete. The use of Releases helps to foster the early realisation of benefits. However, it is more than likely that some benefits will not be realised until sometime after the project is complete and its team disbanded. The Realising Phase is therefore designed to allow for the continual tracking of benefits and learnings after the project has been completed. At the end of this phase, the project is marked as 'project closed'. 

Stuck? Want to talk to us?

Raise a support request, book a call, or send us an email