New project management articles published on the web during the week of January 22 – 28. And this week’s video: Harry Hall explains the concept of risk velocity—the relative amount of time you have until an identified risk manifests as an issue—and how to include it in your qualitative risk assessment. 4 minutes, safe for work.
Must read (or Listen)!
- Connor Forrest describes Amazon’s new retail artificial intelligence technology, called Just Walk Out. It’s the brains behind Amazon Go—a convenience store with no checkout line. 3 minutes to read.
- Devin Coldewey reports on the surveillance technology behind Amazon Go. 6 minutes to read.
- Dan Smiljanic reveals the results of Binfire’s analysis of the status of project managers and the profession, with global statistics and a survey of 1080 PM’s in the USA, UK, Europe, Israel, India, and Japan. 7 minutes to read and very enlightening.
- Glen Alleman tutors us on physical percent complete—also called, “Are we done yet?” in the context of an integrated master plan and integrated master schedule. 8 minutes to read.
- John Goodpasture answers a key criticism of Monte Carlo simulations: you don’t really know what distribution should apply. 3 minutes to read.
- Dmitriy Nizhebetskiyoffers a practical guide to identifying project risks. 6 minutes to read.
- Mari Rengarajam Deenadayalu tutors us on managing project scope in the presence of complexity and uncertainty. 5 minutes to read.
- Mike Clayton curates an excellent list of the best books about communication skills (and there are several types of skills represented) for project managers. 10 minutes to read.
- Stefan Wolpers curates his weekly list of Agile content, from the state of Agile engineering to SWARMing to why the velocity of experimentation is worth measuring. 3 minutes to scan, 7 outbound links.
- Gojko Adzic says that tools like Kanban and Scum boards are only mirrors—they reflect where you are. To make them actionable requires context and experience. 8 minutes to read.
- Johanna Rothman shares some ideas for helping your team finish all of their work inside a sprint. 4 minutes to read.
- Vrushali Umbarkar coaches us on why, when, and how to make the move from Scrum to Kanban.
- Renee Troughton lists the seven habits of highly effective Agile sponsors. 9 minutes to read.
- Pete Houghton describes the gamification of automated software testing. 5 minutes to read.
- Kate Paulk lists ten bad reasons to not hire additional software testers. Some of these are funny because they’re both terrifying and common. 8 minutes to read.
- Walter Frick describes three ways to improve your decision making. 4 minutes to read.
- Scott Berkun says that there are several ways to say “no,” and as leaders and decision-makers, we should master all of them. 5 minutes to read.
- Ryan Ogilvie correlates a shift in the weekday with the number of reported software incidents with a shift in the weekday that changes are moved to production. 4 minutes to read.
- Art Petty points out the liberating power of accountability. 2 minutes to read.
Technology, Techniques, and Human Behavior
- George Krasadakis describes the ways in which the economy—from transportation to insurance—will be impacted by autonomous cars and trucks. 6 minutes to read.
- Fergus from TechRogers created an infographic that shows all of the sensors and other components that make up a self-driving car.
- Seth Godin describes four postures to consider when working with a good designer, from “I know what I want” to “I’ll know It when I see it.” Just over a minute to read.
Working and the Workplace
- Leigh Espey takes us through the steps for dealing with a difficult team member. 4 minutes to read.
- Tom Cagley helps you to decide whether you need a coach or a mentor. 3 minutes to read.
- Elle Griffin shares a nifty flowchart to help you decide whether to have a meeting. Maybe 2 minutes to read, if you don’t stop to giggle.