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.
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.
New project management articles published on the web during the week of January 29 – February 4. And this week’s video: Personal Kanban author Jim Benson introduces a new series of videos—The Agile Heretic. “We’ve gone from Death Marches to Death Sprints.” Sounds interesting! 7 minutes, safe for work.
Tsedal Neeley expounds on swift trust, passable trust, direct knowledge, reflected knowledge, and how we build trust with colleagues we rarely see. 5 minutes to read.
Jesse Lynn Stoner explains how to make an effective apology and increase trust. 3 minutes to read.
Henny Portman reviews Patrick Lencioni’s The Five Dysfunctions of a Team, a classic work on getting to collaboration by beginning with creating trust. 3 minutes to read.
Harry Hall explains the what, why, and when of evaluating project risks. 3 minutes to read.
John Goodpasture unpacks the concept of coupling to explain why, even in an Agile approach, dependencies can be reduced with a proper temporary architecture. 2 minutes to read.
Laura Barnard notes that Agile and PMO are not mutually exclusive concepts. In fact, they can complement each other. 7 minutes to read.
Elizabeth Harrin curates her list of recommended project management certification training courses, for PMI and PRINCE2 certifications. 5 minutes to read, 6 outbound links.
Elise Stevens interviews Marisa Silva on positioning the PMO to deliver impactful value. Podcast, 18 minutes, safe for work.
Stefan Wolpers curates his weekly Agile roundup, from useless Agile metrics to big room planning, to the case for fewer product managers. 3 minutes to read, 7 outbound links.
Dan North coins a new term: SWARMing, Scaling Without a Religious Methodology. 17 minutes to read.
Kiron Bondale looks at the leadership problem of Agile adoption—organizational adoption of an agile mindset. 2 minutes to read.
Tom Cagley has collected a few metrics that can determine if our objectives in adopting agile methods are being met. 4 minutes to read.
Mike Clayton explains Kanban, from its roots in Toyota’s JIT manufacturing system to adoption by the Agile movement. Video, 6 minutes to watch; safe for work.
Paul Merrill explains why you won’t be able to convert your entire testing team to use automated test tools. 6 minutes to read.
Art Petty recaps an anecdote that illustrates how to handle an attack on your credibility during a meeting. 5 minutes to read.
Bob Tarne notes that psychological safety—the perceived ability to push back on a management request—is created by managers, not team members. 2 minutes to read.
Doug Thorpe receives an Email from a former colleague that was “less than flattering,” and notes that leaders can’t win over everyone. 4 minutes to read.
Technology, Techniques, and Human Behavior
Jeff Furman tips his hat to Mary Ann Jensen, the neglected co-author of the update to Dr. Bruce Tuckman’s Stages of Team Development Dr. Jensen is now a psychologist in private practice. 2 minutes to read.
Amy Hamilton recommends some small behavior changes that might help you to avoid a cybersecurity breach—at home, at work, and en route. 3 minutes to read.
Julian Strachan says that it’s OK to be techno-skeptical—after all, a technology does not control how it is used. 4 minutes to read.
Working and the Workplace
Eamonn McGuinness describes a model for handling those little interruptions and distractions that pop up throughout the day. A minute to read, or a video at 3 minutes; safe for work.
Leigh Espy shares her tips for getting things done in a timeframe a little closer to your original estimate. 3 minutes to read.
John Yorke notes numerous studies that say there is an inverse relationship between hours worked and productivity. 8 minutes to read.
Nils Salzgeber argues that the key to higher productivity is to manage your energy, rather than your time. 19 minutes to read.
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.