Our Approach
Our Salesforce experts are proud of what we do and we want our customers to be proud of their platform. We have broken down how we run our projects into a systematic and linear approach so that all parties are clear on how we can get to the end goal and be confident on what has been planned, implemented and adopted. This is your journey and we want to be there to help guide you along the way, therefore, it is imperative that you know what is happening every step of the way so that you can own the solution and platform moving forward.
Preparation
Discovery Workshops & developing a project plan and strategy
Implementation
Build and scale the solutions and processes defined in the preparation phase
Adopt & Train
Delivering Training Sessions and Materials to drive adoption
Methodologies
We work closely with the Agile, Waterfall, or "Wagile" methodologies, however; it's your project!
During the planning phase we will explore the available methodologies and as a unified team we will agree on the best methodology that makes sense for the project and the business. Below we have listed out some basic details on the approaches that we can take during a Project.
Below we have listed out some basic details on the approaches that we can take during a Project.
Agile
Agile methodology is an iterative approach to project management, this means the project team can design and develop software that is constantly being reviewed and reworked, ensuring the "best in show" software solutions.
This is immensely beneficial to project teams who are able to use this methodology, due to the ability to quickly turn around new requirements and implement them.
However, due to the iterative approach allowing fast redesign and reimplementation, means that Agile projects can become quite lengthy.
Waterfall
Waterfall methodology is a linear, phased approach to running projects. The Waterfall phased approach is dependant on the previous phase of the project, meaning that phases have to be completed prior to the next phase starting.
This can be very beneficial to project teams, as they have a full set of requirements and all information on the project prior to implementing it.
However, this can also be its downfall; as the requirements are gathered up front and implemented from start to finish, it can cause issues with customers deciding that they want to change a requirement mid Project.
Wagile
"Wagile" is a blended methodology that is adopted by most Consultancies. The reason behind this is; not many project teams like to implement pure Agile or Waterfall, due to the potential issues they can cause.
The term Wagile was coined, which is intended to be a mix of both methodologies. With Wagile, you get the iterative support of Agile, but with the benefits of having a set of upfront requirements.
Whilst we understand that project teams do not like the hidden costs of having to change requirements mid build. Wagile allows this to happen in a smoother way then it would with a Waterfall project, but it also means we shouldn't hit any surprises that might popup during an Agile Project.