Business Processes

Project Scoping

A tremendously valuable investment when done right, the project scoping phase produces the effective 'blueprint' for the development phase.


What We Offer

The Project Scoping phase of a software development project starts with the detailed capturing of requirements and ends with a solution design and production plan.

By engaging us to carry out a Scoping Phase, you will leverage our development experience and track record in planning and producing software to set functional requirements and budget constraints.

We offer project scoping as an individual service, so you are under no commitment to employ Governor as your development partner once the scoping is complete.  To allow you full choice, all the documentation we produce during Scoping belongs to you and is written so that any suitably qualified development company could understand it and provide an accurate quote for delivery.


Below is a summary of our approach to scoping projects:

  • After we have reviewed your initial project brief, a senior developer spends time with you to understand your requirements in greater detail. 
  • We test and clarify assumptions about the project, make sure the proposed development is fully aligned to business needs and explore any associated risks. This work involves time spent on site with you, interviewing and involving key stakeholders and staff.
  • We carry out any necessary proof of concept work needed to demonstrate the viability of our proposed solution, particularly in respect of integration with third party services and applications that you may be already using.
  • The remainder is spent back in our offices carrying out research and writing up our findings and recommendations.
  • The end result of the Scoping Phase is a comprehensive document detailing which - depending on the nature of the proposed development - may include:
>  a domain model
>  a description of the underlying business logic required
>  user interface concepts and functionality needs
>  software and hardware requirements
>  proof of concept results
>  a development plan including staged deliverables and milestones
>  identified stakeholders and decision makers
>  an estimated cost of development
>  a list of assumptions/unknown factors that may still impact the development of the solution