At Rokk our initial discussions with our clients allow us to form the framework of the project that will address the business challenge or issue. Whether this is developing software for use by field service engineers, or a web application to allow our client’s customers to share information on food produce it is important to understand what will be delivered, and just as importantly what won’t be delivered as part of this project.



It is important to identify the scope of the project and ensure that essential requirements are included. An outline of what will not be included in the project is also outlined to ensure there is no ‘scope creep’ which can cause assumption and confusion on what is being delivered within the software, mobile app or website.


We also reach an understanding with our clients on changes that the product we deliver will make on the client’s business processes and what information needs to be available for the product to function. This is agreed at the outset so any internal change management or information required for product testing can be requested as soon as possible to avoid delay in delivery.


An agreement is reached on communication and collaboration processes between our team and our client’s team who are involved with the design and delivery of the software, app or website.

Benefits of exploration and scoping

Completing the initial exploration and scoping phase allows both the client and ourselves to move forward with confidence into the product development phase of the project and knowing:

  • What will be delivered
  • What won’t be delivered
  • What business processes would be subject to change
  • What information is required for the product to function
  • Where the client is required to collaborate on the project
  • Frequency of communication is agreed

Does your business have an Exploration and scoping challenge? We'd love to hear about it...

Contact us