New project management articles published on the web during the week of March 5 – 11. Daylight Savings Time began in North America today, March 11 but won’t begin until March 25 in the UK and most of Europe. And this week’s video: Chris Pond shows how to generate reports from Microsoft Project. 3 minutes, safe for work.
Schaun Wheeler: “Most ethical mistakes come from the inability to foresee consequences, not the inability to tell right from wrong.” 8 minutes to read.
Bill Taylor notes the passing of Roger Bannister, who ran the mile in under four minutes by ignoring conventional wisdom. There’s a lesson here for those who would lead change. 4 minutes to read.
Ephrat Livni interviews futurist Richard Watson on how to be better informed—start by avoiding the news. Television journalism is to journalism as television personality is to personality. 3 minutes to read.
Elizabeth Harrin extracts actionable ideas from 15 women in project management that she’s interviewed over the years. 8 minutes to read, with links to each of the interviews and the LinkedIn profiles of each project manager.
Mike Clayton offers a primer in change management for project managers. 6 minutes to read.
Doug Thorpe revisits David Gleicher’s 1960’s era model for resistance to change. 4 minutes to read.
Guilherme Caloba shares an approach to integrating qualitative and quantitative risk analyses. 6 minutes to read.
Sai Prasad shows how to display the MS Project timeline as a countdown, in under a minute.
Brad Egeland walks us through the steps to replace the project manager n a failed project. 5 minutes to read.
Stefan Wolpers curates his weekly list of Agile content, from the Agile Fluency model to why projects are always late to choosing your battles. 2 minutes to scan, 7 outbound links.
John Yorke contemplates the notion of delivering value in two posts, the second one applying Eli Goldratt’s observations on how measurement influences behavior. 10 minutes to read both.
Johanna Rothman notes that traditional measurements focus on resource efficiency rather than flow efficiency. There are better alternatives. 5 minutes to read.
Michael Stahl offers some “test cases” for the practical application of ethics in software testing. 7 minutes to read.
The Clever PM refines our approach to retrospectives as a key component of continuous improvement.
Kiron Bondale asks the rhetorical question: shouldn’t we all be agile project managers? Just over a minute to read.
Henny Portman reviews Tribal Unity: Getting from Teams to Tribes by creating a one team culture. 2 minutes to read.
Bruce Benson reflects on how poor management practices often start at the top. 3 minutes to read.
Deborah Riegel tells us how to solicit negative feedback when your manager doesn’t want to give it. Lessons here for managers, too. 4 minutes to read.
Cory Foy presents a purpose-based strategy alignment model. 3 minutes to read.
Technology, Techniques, and Human Behavior
Hanan Benold explains how to communicate technical debt to non-technical decision makers. 4 minutes to read.
Michael Solomon tells how to manage penetration testing like a project (which it is). 5 minutes to read.
Paramita Ghosh notes the evolving use cases for the Internet of Things. 5 minutes to read.
Working and the Workplace
Leigh Espy shares a simple technique to help deal with nervousness before and during a presentation. 5 minutes to read.
Gina Abudi catalogs some of the challenges in managing remote workers. 2 minutes to read.
Mike Vardy interviews Dr. Mary Lamia on her new book, What Motivates Getting Things Done. And she never heard of David Allen’s book before writing it! Podcast, 26 minutes, safe for work.
In addition to meeting the current needs of the users, a good design (and a good implementation of a good design) has to be capable of being supportable once it makes the transition to production. We have to be cognizant of both the history of the legacy system we’re replacing and the potential for evolution of user requirements over time. Both technical debt and Lehman’s Law come into play here and good project managers help the designers keep past, current, and future needs in mind.
As always, thanks for taking the time to read my stuff.
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.