New project management articles published on the web during the week of May 21 – 27. And this week’s video: an ancient performance of “Chateau Lafitte ’59 Boogie” by Foghat, with the late Lonesome Dave Peverett reminding us how it was done before lip-synching and backup dancers. 8 minutes, safe for work, but put the headphones on and crank it up.
David Harding summarizes current trends in mergers and acquisitions and finds that we are returning to successful models from the early 20th 4 minutes to read.
Quinn Norton reports on the Efail exploit and then goes deep into history to explain why Email is a non-fixable problem with no clear owner. 10 minutes to read.
John Harris notes that most of the new product hype coming from the Big Tech firms is for … well, useless crap. Do you really need a digital assistant to make your phone calls? 5 minutes to read.
Leigh Espy interviews project manager and blogger Dmitriy Nizhebetskiy on how he went from naval officer candidate to software development project manager and what he learned along the way. 8 minutes to read.
Susanne Madsen reviews three well-known projects that ran over budget and schedule and had rough initial roll-outs but are today deemed iconic works. 5 minutes to read.
Mike Clayton explain strategic project definition. Video, 3 minutes, safe for work.
Vivien Gold reminds us of some of the elements to include in a project budget. 4 minutes to read.
Glenn Alleman tutors us on cost, price, and value and how they are used in business decision making. 5 minutes to read.
Nick Pisano begins a series on integrated program management elements. This one is on costs—development, management, and product lifecycle—and why we’re not capturing all of them. 10 minutes to read.
Stefan Wolpers curates his weekly list of Agile content, from working for Scrum-clueless management to mental models to guerilla user testing. 7 outbound links, 3 minutes to scan.
Neil Killick explores alternatives to story points in making delivery estimates. 5 minutes to read.
John Cutler invokes Deming in pointing out that high WIP, resulting from crappy management systems, generates more problems than actual people. 4 minutes to read.
Eric Weiss observes that Scrum is not necessarily agile, and there are several ways to “do” Scrum counter-productively. 9 minutes to read.
Tim Runcie explains the newest Agile features of MS Project. 10 minutes to read.
Kiron Bondale makes the case for using Gantt charts and other project management tools even in projects using Agile or adaptive methods. 2 minutes to read.
Alexander Maasik curates his weekly list of leadership articles, from what people care about to the value of expertise to welcoming new people. 5 outbound links, 3 minutes to read.
David Dye explores what we can do by simply changing the question. Whole new answers appear. 3 minutes to read.
Dan Rockwell explains proactive delegation, because “Desperation is a lousy context for delegation.” 2 minutes to read.
Technology, Techniques, and Human Behavior
Greg Satell notes that you can’t commercialize a scientific discovery—first you have to create a product that incorporates it. And that can be harder than the science. 5 minutes to read.
Youyou Zhou reports on a scary Amazon Alexa “fail” that should make you wonder how fully you can test devices that interpret speech. 3 minutes to read.
Albert Gareev talks about how to find the starting point in business intelligence testing. 5 minutes to read.
Working and the Workplace
Elizabeth Harrin shares a massive infographic on the Art and Science of Networking. Maybe 6 or 7 minutes to read, but very non-linear. Take your time.
Jack White (not the musician) identifies five “routines” that justify procrastination and hinder achieving goals. 4 minutes to read.
LaRae Quy recounts her experience at the FBI Academy in explaining how to build a strong mind. 5 minutes to read.
Cassandra Leung explains her “rabbit poop” model for learning. 4 minutes, but do not read this over certain breakfast cereals.
New project management articles published on the web during the week of May 7 – 13. And this week’s video: Chris Croft explains the difference between program evaluation and review technique (PERT) and critical path method (CPM) diagrams. Less than 3 minutes, safe for work.
Walter Frick summarizes the corporate strategy alternatives of developing a “moat,” or barriers to imitation, and setting a pace of innovation that others can’t match. 3 minutes to read.
Brandon Vigliarolo reports that researchers in the US and China are finding ways to insert messages for digital assistants like Siri into white noise. No hacks in the wild yet, but … 3 minutes to read.
Terena Bell defines cyber resilience—think continuity of operations during a data breach or cyber-attack. This is going to be a critical success metric for a lot of projects, going forward. 4 minutes to read.
Mike Clayton details the steps to create a robust project risk culture. 10 minutes to read.
John Goodpasture contemplates applicability of the firm fixed price contract, as stipulated by the public sector, for work using Agile methods. 4 minutes to read.
Kaleigh Moore examines four trends that are transforming project management. 5 minutes to read.
The folks at Clarizen give us some guidelines on when we should insert milestones in our project plan. 3 minutes to read.
Brad Egeland describes seven big technical advances—from Tupac to Elon—that we should see impacting our projects over the next few years. 5 minutes to read.
Stefan Wolpers curates his weekly list of Agile content, from ‘agile’ as social technology to not-invented-here syndrome to epic corporate innovation failures. 7 outbound links, 3 minutes to read.
Roman Pichler tells us why product owners need to take on a very focused leadership role and leave the rest to the people in the other Scrum roles. 4 minutes to read.
Jesse Fewell maps the career progression from Scrum master to Agile Coach. Video, 7 minutes, safe for work or you can read the transcript in about 4 minutes.
Johanna Rothman examines the challenge (for some teams) of knowing when to release all the value they’ve created. Yes, it’s about done. 2 minutes to read.
Keith Hogan describes “skinny” Agile, as an organizational approach to the adoption of selected practices. 15 minutes to read.
Yuval Yeret gets into the details of limiting work in progress in Scrum by using Kanban concepts and techniques. 4 minutes to read.
Henny Portman reviews The Agile Enterprise, by Mario Moreira. 4 minutes to read.
Alexander Maasik curates his weekly list of leadership articles, from why entrepreneurs start companies to jobs to be done to managing priorities. 5 outbound links, 3 minutes to read.
Tony Schwartz tells us how to deepen, widen, and lengthen our perspective to better think about complex problems. 4 minutes to read.
Hank van der Merwe shares a few tips to help us stop overcomplicating leadership. 3 minutes to read.
Peter Landau has compiled ten classic quotes about management and offers his thoughts on each one. 8 minutes to read.
Technology, Techniques, and Human Behavior
Greg Satell debunks four pervasive myths about innovation. “Don’t look for a great idea, find a good problem.” 5 minutes to read.
Carey Fletcher shares her experience with developing a central testing team in a scaled Agile environment. 3 minutes to read.
Erik Dietrich shoots down five myths about test-driven development. 5 minutes to read.
Working and the Workplace
Liana Brinded recaps research by Robert Half that found employers lose their top candidates if the interview process drags on for too long. 2 minutes to read, interesting graphic.
Craig Brown looks at teams that go through the Tuckman stages of team development—forming, storming, norming, performing—and then stay together. 3 minutes to read.
Faisal Hoque poses three questions that can help you determine your next step in career development. 3 minutes to read.
New project management articles published on the web during the week of April 30 – May 6. And this week’s video: Mike Clayton explains the acronym ITTO, which refers to inputs, tools, techniques, and outputs, and why it takes up so much of the PMBOK. 4 minutes, safe for work. And two pictures from Bisbee Arizona, courtesy of Steve Miller—Thanks!
Avery Phillips notes that ransomware is here to stay. And paying the ransom may not be as damaging as the loss of trust. 3 minutes to read.
Bhaskar Chakravorti observes that, while the GDPR might seem like a good template for data privacy, not all countries agree that regulation is the best solution. 7 minutes to read.
Youyou Zhou analyzes the data, finding that far fewer international students are coming to the United States for an education. 2 minutes to read.
Niansheng Chu tutors us on Failure Mode and Effects Analysis, a structured approach to finding the risks inherent in a design or process, with examples. 8 minutes to read.
Suzanna Haworth gives us a deep understanding of the RACI chart and various alternatives. Also, a template! 15 minutes to read.
Sylvia Gindi does a deep and thorough dive into project deliverables and explains why a milestone isn’t a deliverable. 10 minutes to read.
Elizabeth Harrin examines five common roadblocks to success encountered by many (most?) projects and how to move them off the road. 4 minutes to read.
Brad Egeland also identifies five common causes of project failure and how to avoid them. 6 minutes to read.
John Goodpasture goes back to Nate Silver’s new classic, “The Signal and the Noise,” to frame Bayes Theorem as an iterative process. 2 minutes to read.
Stefan Wolpers curates his weekly list of Agile content, from decisions under uncertainty to minimum-viable-whatever to “other” customer success metrics. 2 minutes to read, 7 outbound links.
Bisser Ivanov begins a series he’s calling Kanban 101. 3 minutes to read.
Johanna Rothman explains the difference between minimum viable experiment (MVE) and minimum viable product (MVP). 5 minutes to read.
Ilia Pavlichenko describes The Speed Boat Game—an interesting product metaphor to get clients to talk about their pains and perceived value of a product. 3 minutes to read.
Marie-Eve Trempe provides a quick tutorial on velocity for Scrum teams and how to measure it and use it.
Alexander Maasik curates his weekly list of leadership content, from why entrepreneurs fail to tackle big problems to your imagination as a superpower. 3 minutes to read, 5 outbound links.
Jory McKay presents 5 key goal-setting exercises for high-performing teams, as practiced at places like Google, LinkedIn, DropBox, and more. 15 minutes to read.
Mary Jo Asmus says that leading means staying out of the weeds—if you love the work, maybe you shouldn’t be a manager. 2 minutes to read.