Tips & Tricks to Master Software Migrations - Part 2

Project Management Methodology – the most simplistic way of looking at a project is as a series of tasks that need to be accomplished in a certain order, you can try using different techniques and ways to make this more efficient, but it mostly comes down to the basics:

It is Not the Software’s Fault! – I have seen many good software products tarnished or given a poor reputation simply because they were not configured correctly or in line with the ‘to be’ business processes.Systems cannot answer back and as such they tend to be an easy thing to blame, but behind every piece of software are the people who develop, configure, and maintain it. Always remember this when something is not working the way you would have hoped.

Having people accountable and responsible for all aspects of the various business processes and functional areas will ensure a sense of ownership and pride in the outcomes being delivered, then there is less chance of it being ‘the software’s fault.’

'Surely' is a Slippery Slope to Circular Conversations – when any stakeholder or team member starts a sentence with ‘but surely’ know that common sense may be about to disappear out of the window and any pragmatic or practical debate will become very difficult, assumptions that are not shared by all parties are highly likely to be introduced at this time. In moments like this, knowing when not to speak is arguably one of the most valuable yet challenging disciplines in business.

Honesty and Transparency with Timelines – try and avoid having dates the steering committee are working towards and dates that are communicated to the team, it doesn’t engender confidence in the team and risks losing the trust of staff if they find out (which they inevitably do) that there were in fact two sets of dates in play.

Navigating the Perilous Pathways – maintain a risk register specific to the project, include the standard elements such as likelihood and consequence. Risk management may not be the most exhilarating aspect of a project, often being overlooked early on. However, it's crucial to exercise discipline in this area by keeping the risk register current and up to date - at a minimum, monthly, though fortnightly updates are ideal.This ensures all stakeholders are well informed about the project's associated risks. Additionally, adopting an approach of open and transparent communication in presenting these risks (as outlined in point 4) is essential for maintaining clarity and trust among all parties involved.

 

Mastering the Art of Transformation – change management is often an overlooked yet essential component of any successful project. Communication should not just be frequent but welcomed, especially if it is clear, tangible, and has a defined purpose. When crafting communications, prioritise addressing the recipient's perspective by answering the question, 'What does this mean for me?' Additionally, ensure the 'So what?' question is answered to clarify the objective of the information being presented. Embracing this approach ensures that every communication is meaningful and directly contributes to the project's success.