New project management articles published on the web during the week of July 2 – 8. And this week’s video: Bill Gates discusses his pledge of $2 billion for investment in new alternative energy technologies. 3 minutes, safe for work.
Business Acumen and Strategy
John Detrixhe points out some of the reasons that European “Big Tech” companies are smaller than their US and Asian counterparts. 4 minutes to read or scan the high points.
Benjamin Gomes-Casseres examines the apparent death of the “GE model” in the aftermath of that company’s removal from the Dow Jones Industrial index. 4 minutes to read.
Peter Diamandis summarizes three ways that technology is making a huge difference in healthcare, from personalized medications to intelligent prevention. 6 minutes to read.
John Goodpasture notes that schedule slack is your most powerful tool for managing risks and explains why. 2 minutes to read.
Rob England follows up on the 20 IT project management dysfunctions he gleefully listed on Twitter. “If only the strong survive your system it’s time you fixed your system.” 3 minutes to read.
Michael Wood identifies the challenges inherent in managing projects in a change-resistant culture. 7 minutes to read.
Brad Egeland warns us not to let the project become about the technology. 5 minutes to read.
Mike Clayton explains the Belbin Team Profile, a widely used team assessment tools. Think of it as roles defined by behavior, useful for diagnosing team dysfunction. Video, 6 minutes, safe for work.
Joel Carboni posts another in his occasional series on the characteristics of a sustainable project manager; this time focusing on the PM as an agent of change. 2 minutes to read.
Elizabeth Harrin interviews Bill Dow on the PMO life cycle, including the need to eventually close them down. 3 minutes to read, or watch the video, just over 3 minutes, safe for work.
Managing Software Development
Stefan Wolpers curates his weekly list of Agile content, from scaling Scrum to whether Agile is a cult to Agile organization design. 7 outbound links, 3 minutes to read.
Chris Kenst makes the case for including testers in code reviews. 5 minutes to read.
Kiron Bondale asks: when a team member leaves and knowledge transfer is required, does it matter whether the team is using Agile methods? 2 minutes to read.
Roman Pichler advocates a growth mindset to improve your product management skills. 6 minutes to read.
Jennifer Bonine interviews Gene Gotimer on a practitioner’s view of the pervasive role of QA in DevOps. Video, 12 minutes, safe for work.
Alexander Maasik curates his weekly list of leadership articles, from team goal-setting to why team-building exercises don’t work as well as team nurturing. 5 outbound links, 3 minutes to read.
Scott Cochrane says that the way to avoid decision-making disasters is to always know who “holds the key” to the decision. 2 minutes to read.
Melody Stone shares some insights into selecting meeting attendees and some behavioral “failure modes.” 4 minutes to read.
Research and Insights
Lila McLellan reports on a new study that found open office layouts may make people less productive and change the way they communicate. 3 minutes to read.
Scott Gerber recaps input from the Young Entrepreneur Council on the new technologies that appear ready for widespread use. 4 minutes to read.
Teppo Felin reconsiders the “gorilla on the basketball court” experiment: if humans are blind to what is obviously out of place, does that simply mean we are good are focusing our attention? And what does that imply about artificial intelligence? 18 minutes to read.
Working and the Workplace
Suzanne Lucas reflects on the growing gap between biology and social mores in the age of #MeToo. The law isn’t keeping up, so corporate rules need to adapt. Quickly. 7 minutes to read.
Alicia Adamczyk notes that requesting help from people with whom we have “weak ties”—not friends or family—can be more effective precisely because they are not like us. 3 minutes to read.
Leigh Espy tells us how to build rapport with remote team members. 5 minutes to read.
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.
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.