If you're part of a business that needs to share information a lot among users of Project, you should seriously think about implementing a system to do it. The Enterprise Project Management system allows any team member access and sharing rights across the whole business - from the executives to the accountants and so on. If you're all using Project, it makes sense to share your data to keep the business running smoothly and on track.

Do you really need it though, and is your business ready for it? There has to be a certain culture of collaborative working already in place before you expect all your Project users to take to the new system. Does your team already share information? Do you have good communication between the very top (executive) and the team members (or new starters?).

Some people are only used to sharing information with their line manager or immediate team, and of course there's some sensitive information (salaries tendered, for example) that should only be accessed by some and not others. In the spirit of getting a Project done, though - consider if you could benefit from EPM by asking these kinds of questions about how you already work.

Remember that take-up on a new system is slow, initially, and your staff or project team members might need training in how best to use the system. If you involve everyone from the start, it will get easier for people to help each other out with the Project technology.

Even if you, as manager, are the only Project user, the software has sharing in mind - you can implement an Excel spreadsheet of budgets from the account department, you can get the newsletter editor to publish your most recent report for feedback. Give yourself and your team some time to get used to the system and to iron out any teething problems you might have.

Ensure that your business can cope with what is needed to use EPM. You'll need a Windows server, SQL databases and also the latest version of Project (2007 is good, 2010 is better). Have a practise with the team on how to use it, how to share, and how to manage data protection for each area.

Remember that communication is key - just because all members of your team have Project and are using the EPM, don't presume that everyone suddenly knows everything. Make sure important elements such as costs and goals are shares to that you can collaborate for a better final result. If you don't set what objectives your team have, then no matter how good the software, a breakdown in communication can send it off the rails.

Once everything is in place, remember not to neglect individual needs - does someone need training in Project? Can you do more in team meetings now that you're all on the same page? Do new starters to your company automatically get access and training so that they can quickly feel "part" of the project? These are all considerations that any good project manager should think about.

Overall, EPM is an excellent tool to run alongside Project, but it also needs excellent management - coming from you!