New project management articles published on the web during the week of June 27 – July 3. And this week’s video: Australian software project manager Adrian Fittolani’s TEDx talk at Deakin University on why being more selective about your TV watching might be the key to both achieving your goals and feeling more relaxed. Yes, it’s a video – but you can choose whether to watch it.
Louis Columbus reports on the ways machine learning is impacting manufacturing, from production capacity and waste reduction to manufacturing-as-a-service.
Lynda Bourne notes some lessons learned on selling change, in the context of Brexit. “It helps if they are unhappy with the status quo.”
Chris Middleton speculates on the impact of Brexit on data protection, data transfer, and privacy. These issues will matter to IT project managers in almost every country.
Maria Nordberg interviews David Hillson, the Risk Doctor, on how uncertainties in work and project should be handled. Just 17 minutes, safe for work.
John Goodpasture opines that the first question of risk management should be, “Where does the slack go?”
Matthew Squair looks at the ramifications of the first fatality attributed to Tesla’s autopilot, while humming an old song by The Doors.
Nick Pisoni points out the limitations of earned value management, especially in managing contracts and risks.
Elizabeth Harrin has some recommendations for getting benefits from new tools brought in by team members without getting bogged down in tech adoption.
Beth Spriggs notes that a large project has to overcome more inertia than a small one, and describes a process to get things moving.
Ryan Ogilvie looks at the strategic considerations that must be addressed by a knowledge management solution.
Johanna Rothman concludes her series on product owners and learning with parts 4 and 5.
New project management articles published on the web during the week of June 6 – 12. And this week’s video: Ed Deci’s TED Talk on controlled motivation and autonomous motivation. Ed is the co-developer of the self-determination theory, which suggests that we should create conditions under which people can motivate themselves. Just 14 minutes, safe for work.
Johanna Rothman presents the case for and against estimates, in parts 1, 2, 3, 4, and 5. This series should be sufficient justification for you to follow her blogs.
Nick Statt reports on Microsoft’s new project management app for Office 365, called Planner. Not a replacement for Project, but a collaboration and planning tool.
Brad Egeland provides one-page summaries for twelve project management, collaboration, and portfolio management software products.
Elizabeth Harrin collected insights from six PM’s on how they manage multiple simultaneous projects.
Pat Weaver looks into those cases where the critical path includes task dependencies other than Finish-to-Start links.
Clark Wimberly notes that proper preparation is required for a kick-off meeting which will pay dividends throughout the project.
Henny Portman reviews “PPM! Manage Your Organization Masterfully with Project portfolio Management.”
Cameron Conaway interviews Robin Kwong, Special Projects Editor at the Financial Times, who find clarity by beginning each project with the same question: What’s it for?
New project management articles published on the web during the week of May 30 – June 5. And this week’s video: A parody of lousy incident management, “BP Spills Coffee.” Three minutes, not safe for work (especially if you work at BP or Haliburton).
Fadi Shawtah describes political risk management for cross-border operations, which includes exposure to everything from currency risk to sovereign risk, to transfer risk.
Michael Kassner quotes Michael Hayden, former director of the CIA and NSA, on vulnerability management: “They’re going to get in. Get over it.” Focus on managing consequences!
Nancy Settle-Murphy addresses techniques for preventing culture clashes for “mixed” teams, after a merger.
Deb Schaeffer demonstrates how to get a better status on project activities by asking additional questions.
John Goodpasture walks us through the project balance sheet. Not a financial view, but a way to show how resources are being allocated to accomplish project goals.
Coert Visser explains the “circle technique,” a white board and Post-It Notes approach to analyzing goals, progress already made, and actions still required.
Cornelius Fichtner interviews Fernando Remolina, who explains how to create a work breakdown structure. Just 22 minutes, safe for work.