I've spent some time recently going over the PMBOK Sixth Guide, Sixth Edition PMP training materials created and published by Velociteach. At the same time, I'm using Mike Bissonette's book Project Risk Management: A Practical Implementation Approach to gain a deeper understanding of risk management. How can the PMBOK processes, including the tools, be leveraged to improve on project risk management?
The current PMBOK Guide, Sixth Edition, has this Risk Management process structure:
Earlier today, I submitted an Ex Libris Users of North America (ELUNA) presentation proposal on the subject of project management. I hope to follow an excellent ELUNA 2018 presentation on project management approaches by SUNY's Jan Waterhouse.
Earlier this fall, I published a post on the Library Services Platform (LSP) in this space. I'm building on these ideas with this take:
This is where strategic vision and mature project management skills support tool exploitation. For the latter, the implementation (supported directly by a vendor) and follow-up projects can lay the groundwork for the ongoing enhancement of user services with the LSP as the foundation.
A Twitter discussion earlier today regarding PMP certification application reviews by PMI highlighted the importance of PMI's Code of Ethics and Professional Conduct. This code includes a combination of mandatory and aspirational standards, with the latter being “an expectation that we have of ourselves as professionals—it is not optional."
I summarize the four primary areas of this code, below:
Responsibility: We accept only those assignments that are consistent with our background, experience, skills, and qualifications.
Analysis: This is one area that was covered in discussion during my 2016 PMP certification training with Steve Norton. For a stretch assignment, it's essential to be candid and complete in describing your PM experience so that the employer can make an informed judgement on your hire.
Respect: Respect is our duty to show a high regard for ourselves, others, and the resources entrusted to us.
Fairness: Fairness is our duty to make decisions and act impartially and objectively. Our conduct must be free from competing self interest, prejudice, and favoritism.
From the Mandatory standard section: "We do not discriminate against others based on, but not limited to, gender, race, age, religion, disability, nationality, or sexual orientation.”
Analysis: I see this as one of the most challenging areas, given the current US political and cultural climate - Note, nationality.
Honesty: Honesty is our duty to understand the truth and act in a truthful manner both in our communications and in our conduct.
I don't see the code referenced often on projectmanagement.com, where the focus is often on technical project management and the use of predictive and agile approaches. I'm now inspired to work on a post for that space.
I'm currently focusing on the Create Work Breakdown Structure process in the PMBOK Guide Scope Management Knowledge Area.
Louis Alderman (in the audio recordings for Velociteach's PMP examination preparation textbook, Sixth edition) notes the importance of the WBS: employing a WBS is the number one way for a PM to improve his/her project management practices.
How to build the WBS? In my job, I currently do a lot of task management work using the Smartsheet tool. Smartsheet has the advantage of being employed as a tool across multiple units in my organization. But I'm skeptical of Smartsheet's support for building graphical presentations, including the WBS chart. There are likewise limits to Microsoft Excel. As a result, I'm using the Cacoo online diagram and flowchart software.
Cacoo has templates for WBS charts (like the section of a WBS shown below. Note that I added numbering manually - it isn't included on the template.
Beyond WBS charts, Cacoo has templates for other project management needs, including fishbone diagrams, and Gantt charts.
PM & Tech Blog
"Nothing so sharpens the thought process as writing down one's arguments. Weaknesses overlooked in oral discussion become painfully obvious on the written page.”