New project management articles published on the web during the week of February 5 – 11. And this week’s video: Mike Clayton explains organizational change management, as a complement to project management—we need to be able to work in both areas. 3 minutes, safe for work.
- Scott Galloway makes the case for busting up Big Tech—Amazon, Apple, Facebook, and Google—the way earlier generations busted up Big Oil, Big Railroads, and AT&T. A long read, upwards of a half hour, but worth your time.
- Gabriel Weinberg alerts us to the impact that Google and Facebook have on our privacy—76% of websites contain hidden Google trackers. 5 minutes to read.
- Ben Tarnoff presents the case for and (mostly) against de-regulation of data collection, as advocated by Google, Facebook, and other tech giants. 5 minutes to read.
- John Goodpasture observes that we may soon be managing project budgets denominated in cryptocurrencies. It’s time to figure out what that means! 2 minutes to read.
- Dmitriy Nizhebetskiytutors us on creating a project communications plan. 6 minutes to read.
- Kiron Bondale points out that the Kotter model for leading change benefits from continually injecting a sense of urgency.
- Richard Paterson does a deep dive on writing a useful test plan, including one unusual observation—you might not need one. 9 minutes to read.
- Michael Bolton tells us how to report progress on testing, as a story woven of three strands. 5 minutes to read.
- Brad Egeland reminds of us the variables to account for when planning projects—even if it’s a similar project for the same customer as the last project. 5 minutes to read.
- Stefan Wolpers curates his weekly list of Agile content, from habits of organizations vulnerable to disruption to Jeff Sutherland’s Scrum@Scale Guide to creating a product wall. 3 minutes to scan, 7 outbound links.
- Pavel Kukhnavets gets deep into the differences between a Scrum daily stand-up and a Kanban daily stand-up. 6 minutes to read.
- Ramakanth Vallur explains how personas—a generalization of a customer segment— add value to user stories. 3 minutes to read.
- Henny Portman reviews How to Lead Self-Managing Teams, by Rini van Solingen. 2 minutes to read.
- Doug Arcuri finds more wisdom in his third read of The Mythical Man-Month: it is important for the team to track decisions made, as close to the code as possible. 7 minutes to read.
- Roman Pichler describes product leadership as a collaborative pursuit of a chain of shared goals. 5 minutes to read.
- Gustavo Razzetti describes the shift from right decisions to safe to try “Perfectionism is the enemy of change.” 5 minutes to read.
- Leigh Espy follows up on her recent book, listing three critical reasons to run effective meetings. 3 minutes to read.
- Derek Huether explains key performance indicators, lagging indicators, and leading indicators for product and services teams. 4 minutes to read.
- Julie Giulioni notes that leaders who are too helpful can leave their staff helpless—or at least stunt their professional growth. 3 minutes to read.
Technology, Techniques, and Human Behavior
- Bob Tarne has started applying Crew Resource Management techniques, which originated in the airline industry, to help Scrum teams become more effective. 3 minutes to read.
- Dan Birch and Neal Murray identify some project planning, risk and issue identification, and status reporting analytical opportunities that might benefit from AI. 4 minutes to read.
- John Felahi expounds on the risks inherent in data management, from ingest through usage. Data integrity should be a big part of our thinking. 3 minutes to read.
Working and the Workplace
- Traci Duez interviews Cesar Abeid, team lead at Automattic, the globally distributed company behind WorPress.com, on leading remote teams. Podcast, 52 minutes, safe for work.
- Craig Brown updates on the Allen Curve—a finding from the 1970s that the further away someone is, the less likely they will initiate communication. 1 minute to read.
- Stephanie Vozza lists some don’t-dos that could be making your to-do list less effective. 5 minutes to read. Yes, that was a cheap witticism, but admit it—you liked it.