projectthorts.blogspot.com
Project Thoughts: October 2016
http://projectthorts.blogspot.com/2016_10_01_archive.html
Saturday, October 29, 2016. I recently presented on Achieving Project Success. Most discussion on this topic that I've heard wanders around matters related to requirements, definition and budget. But there's more. Sure those topics are important, and neglected will frustrate success, but they are not sufficient. Others discuss project processes: particularly relying on the setting of acceptance criteria at relevant points in a project: for deliverables, but also for completion of capability elements.
projectthorts.blogspot.com
Project Thoughts: January 2017
http://projectthorts.blogspot.com/2017_01_01_archive.html
Monday, January 30, 2017. The strategy process is historically separated into planning and execution phases. Some writers tie the two together: Mintzberg and Quinn spring to mind. I do too. This diagram attempts to capture the dynamic as a feedback system revolving around performance (which is where projects live). Links to this post. Friday, January 20, 2017. The coffee queue problem. This is what we usually have:. Links to this post. Wednesday, January 18, 2017. What do you mean, 'value'? I'd prefer to...
projectthorts.blogspot.com
Project Thoughts: September 2016
http://projectthorts.blogspot.com/2016_09_01_archive.html
Thursday, September 8, 2016. Change failures I've seen. Current delivery systems or system interfaces are insufficiently known or understood. Systems are not studied for change opportunities or responses. Where the work of change is on separate projects that deliver lovely pieces of paper, but no renewal, renovation or abandonment of systems. It also fails, or is hampered by:. Neglect of subject matter experts (who probably know more of issues and opportunities than any consultant will imagine), and.
projectthorts.blogspot.com
Project Thoughts: Project predictions
http://projectthorts.blogspot.com/2017/01/project-predictions.html
Friday, January 6, 2017. Most of the formal measures we have of project performance (including progress) are backward looking. They report what has been done, sometimes when it is too late to bring corrective action to bear if performance is below expectation. There is plenty to do to avoid project mistakes: credible baselines, to borrow from Glen Alleman's blog. All well and good, but how do we look ahead? I recently received a newsletter from Charles Pellerin. In $300m major urban renewal project that ...
projectthorts.blogspot.com
Project Thoughts: May 2016
http://projectthorts.blogspot.com/2016_05_01_archive.html
Wednesday, May 25, 2016. 10 factors 8: risks. Risk management is a great proactive way to solve potential problems before they occur. Identify risks early in the project and continue to manage risks throughout the project. Is sort of famous for his statement that risk management is how grown-ups manage projects. What does this mean? A major risk is that there will be cost and time over-runs. How do we manage those? Others have also commented. Links to this post. Subscribe to: Posts (Atom).
projectthorts.blogspot.com
Project Thoughts: April 2016
http://projectthorts.blogspot.com/2016_04_01_archive.html
Monday, April 25, 2016. 10 factors 7: issues. Jump on issues as soon as they are identified. Prioritize and resolve them before they impact on your project. Take pride in keeping issues to a minimum. Minor matters that the PM and his or her team must deal with pop up ALL THE TIME on any active project of non-trivial scope. Examples are: Meridian Systems. And, at the simpler end, Project Perfect. Prominent issues need to be tracked in production meetings and quickly updated. However, issues are only p...
projectthorts.blogspot.com
Project Thoughts: August 2016
http://projectthorts.blogspot.com/2016_08_01_archive.html
Monday, August 29, 2016. I used to disparage the triple constraint: I thought it simplistic and unhelpful. The three constraints (triple, because they interact) are illustrated below. More recently, this has been elaborated into a double triangle: attempting to be all things to all people describing project factors, rather than the constraints. I like Glen Alleman's. I've adapted Alleman's TPM to be 'objective', although 'performance' as the out turn result of the project is what we are after. Fussin...
projectthorts.blogspot.com
Project Thoughts: June 2016
http://projectthorts.blogspot.com/2016_06_01_archive.html
Saturday, June 25, 2016. 10 factors 9: deliverables. As each deliverable is complete, hand it formally over to your customer. Ask them to verify acceptance to make sure it meets their expectations. Only then can you consider each deliverable as 100% complete. The 'deliverable' cycle starts with their identifcation in a work breakdown structure and the setting of their performance requirements, tradeoff criteria and acceptance rules. Without these, no one knows when they have a 'deliverable'. Value for mo...
projectthorts.blogspot.com
Project Thoughts: February 2016
http://projectthorts.blogspot.com/2016_02_01_archive.html
Thursday, February 25, 2016. 10 factors 5: communication. Make sure you keep everyone informed by providing the right information at the right time. Produce status reports and run regular team meetings. Communication is more than just communication in projects, particularly the more complex projects. The PM/PM office needs to have a very clear appreciation of the information flows and needs of the project, the sources and destinations of information, and what 'meta-information' to keep track of. If the g...
projectthorts.blogspot.com
Project Thoughts: Risk Criticaility
http://projectthorts.blogspot.com/2016/10/risk-criticaility.html
Sunday, October 23, 2016. We've all been down the risk ceremony path: where risk management starts with a 'workshop', descends into a matrix, then disappears. You probably know the near-pointless and potentially misleading 'matrix' that both Eight to Late and Cox. The outcome of basing project management on a mature understanding of risk. Subscribe to: Post Comments (Atom). Blogs You Might Like. Operations, Finance, and Accounting for the Development of Software. Statistical Modeling, Causal Inference.
SOCIAL ENGAGEMENT