Bluefin › About Methodology


In today’s competitive world, agility is critical to the success of many businesses as it can significantly accelerate time-to-value.

The principles of Bluefin’s methodology are tried and tested at achieving quick business outcomes; and they remain constant regardless of the methodology chosen for the project or programme. Furthermore, they can also be integrated into agile, waterfall or any variation of your own methodology.

Our methodology principles

The three components of our methodology principles are collaboration, visualisation and iteration, which help to:

  • Shape, deliver and manage successful programmes and projects

  • Provide a collaboration focused delivery model

  • Ensure you receive the best return-on-investment (ROI) 

  • Leave behind an effective way of working that can be adopted for future projects


Experience tells us that the most successful SAP projects are typically business-led. However, this can be difficult to achieve as projects are often initiated and run by IT. Projects must reflect the interests of the business.

Striking the right balance between the business, IT and the Bluefin project team is essential. It enables the project team to hit the ground running and deliver quality results quickly. Strong project management and sponsorship is essential backed up by regular and appropriate communications.


Business users need to really understand the process of developing a systems solution. For this reason, we show them the process through use of demos, playbacks, mock-ups and storyboards. These bring the process alive and give the users the opportunity to ask questions, discuss gaps or issues and suggest changes. 

Engaging business users early on and inviting their input at key stages, means there are no surprises down the line.  Consequentially, re-work  is minimised and the process of developing a systems solution is far faster. When we do our demonstrations, the role of the IT community becomes very important. They can hear the business users’ feedback and provide their own.


Business change can impact project priorities. Flexibility to respond to changing requirements, adjust scope and re-evaluate priorities is therefore essential. Iteration is used throughout the process and, where possible, in the way functionality is delivered to the business, i.e. in iterative drops. It can also increase time to ROI as users have access to live functionality as early as possible.

Choosing the right methodology

Using the right methodology for the right project is essential. So our approach is always aligned to your individual business objectives. It combines a focus on ROI with business buy-in and the minimising of risk with the flexibility to respond to changing needs.

Our principles can be applied to a prototype scenario providing early visibility of the solution, resulting in reducing ambiguity.

The same principles can also be applied to deliver early solution drops as part of the ASAP methodology. This provides early ROI utilising an agile approach whilst retaining waterfall controls.

The choice of methodology is dependent on a number of things including the business case, the solution / product being implemented and a client’s preferred style or approach.

Possible implementation approaches

Different methodologies can be adopted with distinct differences in the way that outcomes can be achieved.


An ASAP-based approach with clear stage gate controls between the standard ASAP delivery stages and governance controls aligned to Prince 2 recommendations. This approach provides clear decision and sign off points between stages, whilst delivering to a comprehensive approved business blueprint. It typically delivers all functionality in a single drop.


As per the ASAP-based waterfall approach, this method provides clear stage gate controls, whilst delivering to a comprehensive business blueprint. This approach however, allows multiple functionality drops with each drop potentially undergoing a separate test cycle to take into account business-as-usual changes during project drops.


Following a more agile-based approach, this method allows clear visibility of the scope to be delivered without needing to provide a comprehensive blueprint. This allows some flexibility in the prioritisation and delivery of the scope areas with the functionality seen in incremental drops. The learning’s can then be fed back into the next iteration along with the ability to re-plan and prioritise each time.


A full agility based model without the need to set a clear scope and agreed business blueprint. This method allows rapid ROI with focus placed on prioritizing and delivering the areas of most value first, quite often driven by the MoSCoW approach. This method allows complete flexibility to reset the scope each time a new iteration starts, allowing for changes in the business needs.









We use cookies on to ensure that we can give you the very best experience. To find out more about how we use cookies, please visit the cookie policy page.