Project Management

Please login or join to subscribe to this thread

In the PMBOK Guide 6th edition there are several logs that a project manager should keep, how do you keep those logs, what is your practice about it?

linkedin twitter facebook   Consulting   Lessons Learned   PMO  
avatar
Jorge Martin Valdes Garciatorres Managing Director| Proyectum Mexico City, Distrito Federal, Mexico
There are several logs that a PM should keep when managing a project, for instance, assumption log, issue log, risk register, change log. I have the following questions:

1. Do you create and keep all of them?
2. Are there tailoring considerations that perhaps avoid using some of them?
3. Do you create another log?

Thanks
Sort By:
avatar
Milena Ilieva Program Manager Global accounts| VMWare Vienna, Austria
Jorge,

I would say, yes, all of these logs are important for projects and project management.

Additional ones, which I used are: opportunity log (it can be part of risk log or separate), claims log (for contracts with external customers, where claims have been issued, or can be issued), project margin improvements plan/log of activities, new sales pipeline activities log (for new contracts, enhancements, optimisations, etc). Anything that serve the needs to have transparency on the project can be /should be logged and tracked.
Regards,
Milena
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
PMBOK put those logs, mainly the format, as optional. We have to consider it optional and it is something the PMI carries because the PMIS, where PMIS is not a software system, is a system by itself. On the other side, "one of the maxims of project management is what is not written, does not exist" so call it as you need but somebody has to be registered in some place.
avatar
MANSOUR THABET ALQUBATY System Controller| Teleyemen Sana'A, N/A, Yemen
Thanks for sharing
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Jorge -

Tailoring your approach to the needs of the project is key. A small, straightforward project might have a single spreadsheet containing such data (e.g. assumptions, decisions, issues, actions, risks) whereas a larger, more complex project would benefit from the use of a more advanced project information tool.

The important thing is to understand what information is needed by your stakeholders and you to successfully manage, deliver and support the project and come up with the leanest method possible for achieving that within the constraints of organizational policy and standards.

Kiron
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Jorge,

yes, I use at least issue log, risk register, change log in every project. If it is not covered by an integrated IT system, I keep excels maintained in team accessible locations.

Thomas
avatar
Jorge Martin Valdes Garciatorres Managing Director| Proyectum Mexico City, Distrito Federal, Mexico
Thank you everyone for sharing your valuable insights. I will write a post about a log that I am using and it has payed off so far. Tip: it is not in the PMBOK Guide. Stay tunned

Please login or join to reply

Content ID:
ADVERTISEMENTS

Sometimes the road less traveled is less traveled for a reason.

- Jerry Seinfeld

ADVERTISEMENT

Sponsors