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 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.
New project management articles published on the web during the week of January 15 – 21. And this week’s video: Allison Osborn explains the “Quarter Life Crisis,” an interesting view of the stress felt by so many millennials as they search for personally meaningful work. 17 minutes, safe for work.
Patrick Gillespie collates reports from around the U.S. indicating that American businesses can’t find workers. Note that 18 states will raise their minimum wage this year. 2 minutes to read.
Peter Fleming notes the science-based backlash against long hours of desk-based work. 4 minutes to read.
Glen Alleman overviews Improving Project Performance: Eight Habits of Successful Project Teams by Jerry Wellman. 3 minutes to read.
Nick Pisano reviews the HBR OnPoint Magazine issue, The Data-Driven Manager: Make the Numbers Work for You. 6 minutes to read.
Mike Clayton shares several stakeholder engagement strategies. 5 minutes to read.
Human Motamedi identifies the challenges to expect when integrating an off-shore team with a near-shore 5 minutes to read.
Geraldine O’Reilly describes the role of Project Champion and what to look for when recruiting one. 3 minutes to read.
John Goodpasture gives a high-level explanation of four very different views of risk. 2 minutes to read.
Luca Collina walks us through the common points of recovering a project that has slipped into the Red. 5 minutes to read.
Stefan Wolpers curates his weekly Food for Agile Thought, from the ‘too many Scrum meetings’ myth to knowing what not to build to the agility assessment framework. 3 minutes to scan, 7 outbound links.
Ryan Ripley interviews Jessie Shternshus on helping teams un-learn the old so they can learn new Agile behaviors and habits. Podcast, 27 minutes, safe for work.
Rik Marselis recaps Brian Marick’s idea of Agile Testing Quadrants. It’s a shame that after more than 14 years, this isn’t more widely used. 4 minutes to read.
David Robins explains the difference between a project manager and a product manager. 2 minutes to read.
John Cutler shares a thought experiment on the relative merits of fixed length iteration and continuous flow in Sprint goal planning. 7 minutes to read.
Rob Lambert explains active listening—why it’s valuable and how to do it effectively. 7 minutes to read.
Tom Cagley begins a new series on coaching and mentoring—similar but different activities. 3 minutes to read.
Derek Huether tutors us on objectives and key results, a well-established process for setting, communicating and monitoring goals and results in organizations. 3 minutes to read.
Technology, Techniques, and Human Behavior
David Balaban presents his analysis of the critical security vulnerability introduced by Apple with the introduction of iOS 11. 7 minutes to read.
Bob Martin uses the aviation concept of going into a stall when behind the power curve as a metaphor for software quality. “Rotten code is induced drag.” 4 minutes to read, even if you’ve only ever been a passenger.
Martin Fowler asks us to reconsider what we mean by an integration test and whether we have a clear understanding of what we’re trying to confirm. 5 minutes to read.
Alexa Roman introduces product analytics as a means of measuring the effectiveness of a UX design. 8 minutes to read.
Working and the Workplace
Brendan Toner presents the ultimate tutorial on how to create and maintain your to-do list. 15 minutes to read.
Anett Grant offers some excellent advice for when your presentation is running longer than the time available. 4 minutes to read.
Ryan Born has some excellent advice: instead of apologizing, say “Thank you!” A minute to read.