New project management articles published on the web during the week of October 22 – 28. And this week’s video: Mike Clayton explains a common term encountered in implementation projects: the business blueprint. Less than 4 minutes, safe for work.
Business Acumen and Strategy
- Greg Satell contrasts innovation practices at IBM, Google, and Amazon—three very different firms with very different cultures. There is more than one way to sustained success. 5 minutes to read.
- Hannah Fry notes the ethical questions of developing applications for cutting-edge technology that might be used for evil purposes. 5 minutes to read.
- Dave Gershgorn reminds us that companies are responsible for the algorithms that they use. Especially if they display bias. 4 minutes to read.
- Elizabeth Harrin notes that the Iron Triangle—Time, Cost, and Quality—are no longer the most significant drivers of whether a project will be perceived as successful. 6 minutes to read.
- Dale Howard helps us diagnose a common problem with MS Project: “I can’t see all of the tasks in my project.” 2 minutes to read.
- Leigh Espy tells us when and how to use an Ishikawa or fishbone diagram for root-cause analysis. 4 minutes to read.
- Mark Bails reviews an example of risk mitigation strategy, as practiced at Symcor. 6 minutes to read.
- Kiron Bondale notes some lessons about project management that we can pick up while shooting pool. 2 minutes to read.
- Glen Alleman ilustrates a few of the problems encountered when trying to apply agile software development principles to program management practices. 3 minutes to read.
Managing Software Development
- Stefan Wolpers curates his weekly list of Agile content, from Agile collaboration to useful metrics to escaping the feature factory mindset. 7 outbound links, 3 minutes to read.
- Craig Smith interview Michael Feathers on working effectively with legacy code. Podcast, 33 minutes, safe for work.
- Erik Dietrich explains how to determine the level of effort required for “enough” testing for quality assurance, based on your backlog of user stories. 6 minutes to read.
- Emily Esposito recaps five trends in UX design, from voice-first to emotional design. I can’t keep up! 5 minutes to read.
- Greg Paciga defends his claim that you can demo things that aren’t done, aren’t working, or even not yet started. 6 minutes to read.
- James Gallagher gives us some pointers for preparing a code review checklist. 5 minutes to read.
- Alexander Maasik curates his weekly list of leadership content, from ignoring your customers to startup hires to structuring your OKR’s. 5 outbound links, 3 minutes to read.
- Suzanne Lucas explains how to empower your employees to make better business decisions. 4 minutes to read.
- Khalil Smith and colleagues explain how to gracefully exclude colleagues from meetings, Emails, and other marginal uses of their time. 5 minutes to read.
Research and Insights
- Neema Singh Guliani and Jay Stanley preview the coming battles over US legislation governing data privacy in the wake of California’s groundbreaking new law. 5 minutes to read.
- Josephine Wolff explains why it’s so hard to punish companies following a data breach, and thus why it will be difficult to craft legislation to regulate it. 5 minutes to read.
- Andrew Burt notes the potential downside of privacy legislation, arising from another law—the law of unintended consequences. 4 minutes to read.
- YK Sugi gives us a tutorial on quantum computers. 8 minutes to read.
Working and the Workplace
- Lisette Sutherland explains how to interview candidates who will be working remotely. Podcast, 9 minutes, safe for work.
- Simone Stoloff notes that, in the future, companies won’t just hire remote employees—they’ll hire remote teams. 3 minutes to read.
- John Goodpasture reminds us that a seemingly silly question might just be a poorly phrased request for important information. 2 minutes to read.