Project scoping

Scoping a project is the starting point of project planning where we work closely with our clients to establish and document project goals, deliverables, features, functions, tasks, deadlines, and ultimately, costs.

In order for prad to accurately scope a project, we will work with you to define a detailed brief which encapsulates all of the requirements.

If the project requires, we may need to enter into a discovery phase where we spend time with key stakeholders determining the project requirements and even delivering some elements of work to help us further determine project needs and requirements.

Once we have worked with you to define the requirements, we will be in a position to recommend the best solution for your project and deliver a Statement of Work with costs, deliverables, and timelines.

This statement of work sets the expectations of all parties so you can understand what we’re creating for you, and our practitioners fully understand your goals and needs.


Waterfall projects

The Waterfall methodology follows a sequential approach where each phase of a project must be fully completed before the next phase begins.

This is often shown in a GANTT chart format in which progress is shown flowing steadily downwards, with dependencies on the completion of the previous phase.

At prad, we recommend that you use a Waterfall approach if your project fits the following criteria.

All requirements are determined before project commencement and there will be minimal change to scope thereafter.

  • There is a fixed deadline.
  • You want to launch a fully formed product by the fixed deadline.
  • We will work with you to determine if this is the best approach for your project.


Agile projects

The Agile methodology is an approach that enables a project team to effectively manage a project which does not have fully defined requirements and where project priorities change; it’s incremental and iterative.

In a nutshell, the most complex and innovative technical projects tend to lend themselves to the Agile framework as it focusses on delivering working software in short periods of time that can be quickly improved upon.

prad applies the Agile with SCRUM framework where the focus is on delivering the highest priority features in short project cycles, called Sprints. At the end of each Sprint, there is a shippable product which will be signed off before moving to the next Sprint.

The product will be launched when it achieves the Minimum Viable Product (MVP) which would have been defined at the requirements stage.

As Agile with SCRUM promotes a collaborative process, we expect the client to be involved during the development process so that we can deliver the best results at the end of every sprint. prad does this by adhering to a number of Agile meetings or ‘ceremonies’ (in Agile geek speak) that promote collaboration between the teams.