New project management articles published on the web during the week of November 13 – 19. And this week’s video: David Dunning (of the Dunning-Kruger Effect) explains why incompetent people think they’re amazing. 5 minutes, safe for work.
Must read (or Listen)!
Bethany Marz Crystal says that the way to battle sexism and harassment is by improving the social feedback loop—call out the behaviors when they happen. 4 minutes to read.
Todd Williams interprets recent statistics that paint a dismal picture of corporate failure to execute on strategy and goals. 4 minutes to read.
Ryan Ogilvie notes that simply asking for feedback at service completion doesn’t help if you haven’t got a strategy to manage and act on that feedback. 3 minutes to read.
Elizabeth Harrin explains how to use graphics, pictures, graphs, and charts to communicate project information. 5 minutes to read, with a link to her white paper on the subject.
Erik van Hurk explains why we should set the Status Date and automatically update the project schedule when US MS Project. 5 minutes to read.
Harry Hall tutors us on planning for project risk management. 2 minutes to read.
Kiron Bondale suggests that we listen for the Cassandras, those subject matter experts who warn of impending risks and issues, even if they seem unlikely. 3 minutes to read.
Nilanjan Kar makes the case for integrating information security management into the PMBOK Guide. 12 minutes to read.
Glen Alleman clarifies why independent cost estimating is valid, even when performed by someone who won’t be party to execution. 3 minutes to read.
Nick Pisano points out the difference between earned value management and cash flow analysis in project management. 5 minutes to read.
Stefan Wolpers curates his weekly Agile roundup, from a Jeff Patton lecture to the problem with Scrum to brilliant jerks and the immorality of addicting users. 8 outbound links, 2 minutes to browse.
Dave Prior interviews Jurgen Appelo on his new crowd-funded app/platform project: Agility Scales. Video, 18 minutes, safe for work.
Jerry Doucett shares a litmus test for getting your organization on track to being Agile (as opposed to doing Agile). 7 minutes to read.
John Yorke describes the zone of acceptance—the collection of tasks that each team member believes is a part of their job—and how to extend it in a self-organizing team. 6 minutes to read.
Tamás Török notes the importance of knowledge transfer in a software development team and describes four complementary techniques for sharing the learnings. 6 minutes to read.
Tom Cagley interviews Johanna Rothman on creating a successful Agile project. 30 minutes, safe for work.
Mike Cohn explains why it’s important to have a consistent sprint duration. 3 minutes to read.
Poornima Vijayashanker and Leslie Yang discuss product debt and why you should pay it down with every release. Video, 6 minutes, safe for work.
Cesar Abeid and Traci Duez talk about getting to self-leadership. Podcast, 28 minutes, safe for work.
Mike Clayton gets into the details of how to manage the transition when a team member leaves your project. 9 minutes to read.
Alyse Kalish gets advice from Katia Beauchamp, CEO of Birchbox, on how to make the best use of advice—as opposed to getting someone to make the decision for you. 3 minutes to read.
Chris Rainey interviews Suzanne Lucas, the Evil HR Lady, who says,” We don’t have a talent shortage, we have a training shortage.” Video, 32 minutes, safe for work.
Working and the Workplace
Brad Feld asks the question: Do you reduce stress for others or increase it? 2 minutes to read.
Scott Berkun explains the pay to stress ratio: “You can always earn more money, but you cannot earn more time.” 3 minutes to read.
Shayna Hodkin posts her occasional advice column, answering “how do I ask for a raise” and “how do I handle hating my job?” 6 minutes to read.
New project management articles published on the web during the week of August 15 – 21. And this week’s video: a tutorial on conducting a Monte Carlo analysis using Excel. Just 11 minutes, safe for work.
Michael O’Brochta looks at the cultural, experiential, and situational drivers of how we perceive behavior as ethical, or not. Including our own.
Kayleigh Töyrä explains how we can apply Finnish culture and values to project management.
Hope Reese reports on a life saved when Tesla Autopilot drove a man to the hospital. Ethical dilemmas, minimum acceptable reliability, and other social risk considerations will make future projects even more complicated.
Harry Hall describes seven simple actions to take that will make your risk management efforts more productive.
Andy Jordan explores the risk management techniques applicable to protecting project benefits.
Nick Pisano makes the case for incorporating measures of technical performance in earned value management.
Glen Alleman lists units of measure meaningful to expressing value.
Kenneth Ashe gives us a refresher course on the basics of project budgets and ROI.
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.