The Money Files

Let’s say that you’ve decided you want to integrate your project management tools with some other platform or software within your organisation – there are lots of reasons why you would want to do this that I have covered in other articles.

So how do you get started? Here’s a quick guide to planning out what you need to do.

Understand your needs

Start by assessing the needs of your project team. Identify which functions are lacking or could be enhanced (e.g., reporting, communication, time tracking, etc.). This will help prioritise which integrations to set up if you’ve got several options.

My suggestion would be to start with something small and easy. That will help you prove the concept of integration, get some useful data and get a ‘win’ that might make it easier to get funding for any larger piece of technical work to do other things.

Choose the right applications

There are probably lots of options for integration. Finance tools for pulling in actuals? Capacity management software for resource planning? Timesheets? Focus on finding applications that complement your project management tool and enhance its capabilities – things where you would actually get use out of the data, the workflow or the interface.

Before you actually make the decision, check that it’s a reliable, supported tool that aligns to the business processes and that it’s going to be worth the effort! Another consideration is your project management tool itself. It seems to me that organisations change tools every few years so you don’t want to invest in enhancing something that is not going to be around much longer. Make sure you’ve got confidence in the longevity of the products you are using.

Review the integration options and approaches

Most project management platforms offer integration options through open APIs or pre-built connectors. You might have an integration hub as part of the tech stack that you would need to  use to pass data from one product to another.

Think about how best to integrate the tools, and lean on enterprise architects and data analysts to work out the best route, and what needs to be done. My recommendation would be to go for solutions that are the simplest, with the fewest data points to reduce the technical complexity.

Test the integration

Before you hit the button, make sure it’s all as tested as it can be. You really need the data integrity to be 100% or people will lose confidence in the data. Then they’ll go back to the original sources and you won’t have saved any time or improved processes at all.

Test with a small group, controlled data and look for issues related to data syncing, user permissions, and overall functionality.

Monitor and refine

As with any software project or process change, you’ll want to keep an eye on it and make sure that it is working as expected. Monitor feedback from users and tweak as necessary to make any improvements.

You might find bugs that were missed during testing or there might be new requirements that help make it more user-friendly or workable.

Once you’ve got one integration set up and working, think about what was the next priority on your list. How can you get that one kicked off? With citizen development and low code development, plus the power of AI, it might be easier than you expect to get something off the ground! Good luck, and let us know in the comments which your most successful integrations have been!

I’m taking a quick break from my mini-series on resilience in project teams as I’ve been doing some thinking recently on how to improve the project management software we have. You might know that I wrote Collaboration Tools for Project Managers so the changing landscape of software products is something I try to stay close to.

One of the conclusions I’m coming to is that tools don’t do everything. As a result, we have to integrate with other products. The software is powerful, but it just can’t/shouldn’t do everything, or you end up with a hybrid product that is rubbish at most things and does everything badly. So integrations so you can use best of breed products is the way forward.

Integrations extend the functionality of your project management tools, and here are 4 benefits to consider.

1. Streamlined workflows

Double-keying data? No thanks! Integrations between apps allow you to automate the flow of information between tools. Need to get that timesheet data into a financial tool? There’s an integration for that. Need to bring in actuals from the accounting software? No problem, we can feed those into the project budget and forecast.

Integrations reduce manual data entry and minimise the risk of human error. And they remove some of the boring work too – win win!

2. Centralised information

How many tabs do you have open? It’s no fun switching from dashboards in one tool to review benefits and then back to the PM tool to enter the actuals, and grabbing stuff from all the places. Bringing in what you need saves time and centralises the data so your team has everything in one place. That should help with transparency and reporting, plus saving time so you don’t have to log in to so many apps in the morning.

For example, integrate with your cloud storage or file-sharing software and then you can access the relevant documents directly within the project management system. To be fair, that isn’t even hard if you’ve got cloud file storage – just add a link! Done!

3. Improved collaboration

You’re in your PM tool but you need to flag something… do you have to leave to go to a messaging app or email? It’s better if there is an integration within the tool so your relevant threads can appear linked to the project task, risk or issue etc. If your tool doesn’t have native messaging, integrate it with whatever tool you do use so that status updates can be sync’d across platforms in real time, so the whole team can see what is going on.

4. Enhanced reporting and analytics

Finally, the more data you have in your PM tool, the better your reporting and analytics can be, and the more you can make use of AI. AI needs pools of data to give you forecasts or suggestions, so if your PM tool is scanty in that area, it’s hard for AI to do anything meaningful with your portfolio data.

Sync up your project data with external analytics or business intelligence tools so you can create detailed reports, analyse data trends, and monitor progress without exporting data manually. And you’ll be able to share project performance data with people who don’t have licences for your PM tools. Because that’s a problem, right?

So, integrations for the win! What tools do you link up (or what problems do you face when they don’t)? Let me know in the comments!

Over the past few articles I’ve talked about different aspects of data privacy and how that links to project management deliverables and the ways of working for the team. One of the big things that we use as project managers is our software, and often we’re involved with selecting new tools or upgrading existing tools.

In this article, I wanted to point out a few things you should be looking for in your PM tools to make sure that you’re having the right conversations about whether they are secure enough for your data. I’m sure your info sec teams will also have a lot to say, so use the content below as a starting point for a discussion, not a replacement for guidance from your internal teams!

Access control and permissions

Ensure that the tool allows for granular control over who can access sensitive data. Role-based access control (RBAC) is essential for minimising the risk of unauthorised access.

What this looks like in practice is that you might have one person on the team with admin or ‘override’ permissions, and everyone else just enters the data. In one company I know, the workflow pushes a project between stages. While it’s going through the approval process, no one can edit the data. That’s good because it means all approvers are seeing the same thing, but also a bit annoying if you’ve accidentally left something out or there is another very valid reason for needing to add another attachment, for example. Admin users could have the power to make changes while a record is blocked for editing by ‘normal’ users, but it’s a power to use very carefully!

Data encryption

Verify whether the tool provides end-to-end encryption for both data at rest and data in transit. This ensures that data remains secure even if intercepted, which is important for software that is hosted in the cloud, or for financial information. I don’t know why you’d need information like bank card records in a project management tool, but even your business case information should be company-confidential and you wouldn’t want it accessible in case of a data breach.

Data storage and backup

Assess where the data is stored and whether that meets your requirements. For example, in the UK there are rules around where patient data is stored in the healthcare industry – we couldn’t have certain data stored in off-shore data centres, for example. Check out your regional data privacy laws.

Again, project management software isn’t going to have the kind of sensitive, personal information that’s on the same scale as medical records, but you still want to be sure it meets your company’s policies for storage.

The same goes for backup. However good your internal systems and however reliable your supplier, can you get the data back when there’s a problem?

Audit logs

This feature is so helpful in the project management software that I use. It’s great to easily be able to see what changed, when and who changed it.

Check if the tool has built-in auditing and tracking features that allow for monitoring access to data and changes to project information. And if it does, who has access to see the audit logs (I’m a believer in transparency here – why not make them available to everyone?).

Certifications

If you’re using software that you’ve bought in, check to see if it (or the company that makes it) has any data or compliance-related credentials like ISO 27001, SOC 2, or EU-U.S. Privacy Shield, which indicate that the tool has passed rigorous security and privacy assessments.

That’s not an exclusive list, but you can use the ideas above as a starting point for thinking about the requirements for data security and privacy for your project management software. What did I leave out? Let me know in the comments!

While so many of us still use the humble spreadsheet for project management and tracking, there are lots of cool technologies out there that will (eventually) be game-changing for project managers. And I’m not talking about AI, although of course that is huge in our industry at the moment.

Project management tools are often seen as task-based, schedule-based, scenario-based products, but will that change when we bring more elements of gaming into the way that teams and results are managed?

Gamification

Gamified project management systems could incentivise teams to make progress. We could introduce a bit of healthy competition. I know not all teams are going to love the idea of gamified work, but in some teams it could provide a bit of engagement and interest. If your project management software has the option to award stars (for example) for contribution, then take a look at what features you could switch on.

I’m part of a community where likes on posts are rewarded – not for the person doing the liking but for the person being liked. The aim is to encourage thoughtful, helpful comments that the community finds valuable. I think it’s a balance between spending all your time crafting the perfect, likeable comment and doing your work, but I do think we’ll see more gamification coming into project management, and I’ve talked about that at conferences before.

Role-playing

I know, I cringe too when role-playing gets mentioned. However, when I’ve been on training courses and we’ve done some role-playing (for example, having a difficult conversation with a colleague) it has been very helpful in addressing the situation in real life.

If you think about it, you’ve probably used role-playing already in your projects. If you have ever demonstrated a solution to a group of customers, you’ve probably had someone playing the role of a customer placing an order or interacting with your product. Just do more of that! It really helps bring the product to life.

You could also look to incorporate role-playing scenarios in training and change management activities. Work with stakeholders and users to give them first-hand experience of the change in a safe environment, helping them see it from different roles in the journey, for example, what it will be like to interact with the product as a customer.

Virtual reality

Personally, I can’t say I’ve used VR for project delivery (yet) but it is a feature of science-based learning at my children’s school. They use VR headsets for educational purposes to explore science topics. Which is cool.

We could see the same for project deliverables, perhaps a virtual simulation of a building that users could walk around to see what it’s like before the construction is complete, or something like that. Perhaps it will get used for virtual project kick off meetings or simulation-based training. This community has probably seen examples of that in use. If you have, can you drop me a comment below and let us all know how that worked out for you?

How do you feel project management is going to adopt new tech (that may or may not be aligned to AI)? If you’ve seen any of it in practice I’d love to hear how you are using it! Thanks!

Quarter 3 of a calendar year is July, August and September. Your business year might not follow the same quarters, but wherever you are in your business year, it’s probably the right time to be looking ahead at what needs to come next. Here are 3 focus areas for Quarter 3.

Forward planning

Begin strategising and planning for high-priority projects in the upcoming quarters. That might look like warming up stakeholders, seeing who is going to be available to work on upcoming projects, doing some light discovery work or pre-initiation investigation, especially on the areas that are likely to take the most time such as procurement and contract negotiations, or getting suppliers to submit security information and forms, or the RFP process. (Not that I’m speaking from experience or anything!)

Involving the team in these discussions can help maintain their focus on future goals and the bigger picture, while hopefully getting you a head start when you come to get those projects going in earnest.

Process optimisation

There’s never a right time to optimise processes, in my experience. The process is in use and it works, so often it feels better to sort out something that is broken, or that is strategically important. But those inefficient processes contribute to low staff morale and wasting time, month after month, so it’s worth scheduling some time to put some effort in. Each quarter, tackle one point or a couple of points, and soon you’ll build up a momentum and improvements.

So how do we do this? Analyse the project management processes and methodologies. Look for inefficiencies or bottlenecks in workflows that could be streamlined for better performance in busier times. I would look through the lessons learned from recent projects and see what’s highlighted there that could be improved.

Ideally, you’d do a full analysis of all possible problems and highlight one or two from the priority list, but in reality that’s a load of work before you see any improvements. A better option might be to just trust your team. If they are telling you that the change control process is a pain in the behind, just focus in on that for now. Improve what is causing people the most headaches, and trust me, they’ll have an opinion on what that is if you ask them.

Tool use

Do a quick review of who is still using the project management software tools you have. People move on so it might be time to claw back licences from users who are no longer in the business or who have changed roles. And other people might benefit from having the licences.

On the topic of forward planning for the quarter, look at what projects are coming up and whether your current licence package is adequate. You might need to add in more licences if you’ve got more projects or more stakeholders needing access to the tools.

If you foresee a need to add in more users, it might be worth scheduling the training for them now so they can hit the ground running when they get their own account.

What else would you be doing at this time to feel prepared for the upcoming months ahead? Let me know in the comments!