Project Management

PMI Global Insights

by , , , , ,
Whether it’s in-person or virtual, PMI events give you the right skills to complete amazing projects. In this blog, whether it be our Virtual Experience Series, PMI Training (formerly Seminars World) or PMI® Global Summit, experienced event presenters past, present and future from the entire PMI event family share their knowledge on a wide range of issues important to project managers.

About this Blog


View Posts By:

Cameron McGaughy
Julie Ho
Heather McLarnon
Laura Schofield
Michelle Brown
Kimberly Whitby

Past Contributors:

Johanna Rusly
April Birchmeier
Nikki Evans
Dalibor Ninkovic
Dr. Deepa Bhide
Chris DiBella
Nic Jain
Nicholas Sonnenberg
Karen Chovan
Jack Duggal
Catalin Dogaru
Priya Patra
Josh Parrott
Scott Lesnick-CSP
Antonio Nieto
Dimitrios Zaires
Ahmed Zouhair
Carmine Paragano
Te Wu
Scott Bain
Katie Mcconochie
Fabiola Maisonnier
Erik Agudelo
Paul Capello
Kiron Bondale
Jamie Champagne
Esra Tepeli
Renaldi Gondosubroto
Mel Ross
Laura Lazzerini
Kim Essendrup
Geetha Gopal
David Summers
Carol Martinez
Tai Cochran
Fabio Rigamonti
Archana Shetty
Geneviève Bouchard
Teresa Lawrence, PhD, PMP, CSM
Randall Englund
Kristy Tan Neckowicz
Moritz Sprenger
Mike Frenette
O. Chima Okereke
David Maynard
Nancie Celini
Brantlee Underhill
Claudia Alcelay
Sandra MacGillivray
Vibha Tripathi
Sharmila Das
Gina Abudi
Greg Githens
Joy Beatty
Sarah Mersereau
Lawrence Cooper
Donna Gregorio
Seth Greenwald
Bruce Gay
Wael Ramadan
Fiona Lin
Somnath Ghosh
Yasmina Khelifi
Erik Rueter
Joe Shi
Michel Thiry
Heather van Wyk
Jennifer Donahue
Barbara Trautlein
Steve Salisbury
Jill Diffendal
Yves Cavarec
Drew Craig
Stephanie Jaeger
Diana Robertson
Zahid Khan
Benjamin C. Anyacho
Nadia Vincent
Carlos Javier Pampliega García
Norma Lynch
Emily Luijbregts
Susan Coleman
Michelle Stronach
Sydni Neptune
Louise Fournier
Quincy Wright
Nesrin Aykac
Laura Samsó
Lily Woi
Jill Almaguer
Mayte Mata-Sivera
Marcos Arias
Karthik Ramamurthy
Michelle Venezia
Yoram Solomon
Cheryl Lee
Kelly George
Dan Furlong
Kristin Jones
Jeannette Cabanis-Brewin
Olivia Montgomery
Carlene Szostak
Hilary Kinney
Annmarie Curley
David Davis

Recent Posts

Are You Going to Be Bitter or Better? Top Takeaways from a Keynote on Change

Lessons Learned From PMI Global Summit 2023

Diversity Celebrated at PMI Global Summit

Lean Portfolio Management to Align Enterprise Strategy

A Glimpse into PMI Global Summit 2023: PMOs, Change Management, Strategy and Networking!


Agile, Agility, alignment, Ask the Expert, Benefits Realization, Best Practices, Bonding, Business Analysis, Calculating Project Value, Capital Projects, Career Development, Change Management, Cloud Computing, Collaboration, collaboration, Communication, Complexity, Congress 2016 Ask an Expert, Construction, Curiosity, Digital Transformation, digital transformation, Documentation, Earned Value Management, Education, EMEA, EMEA Congress Reflections, Engagement, engagement, Ethics, Events, Extra Info, Facilitation, forecasting, future, Generational PM, Global Congress 2016, Global Congress 2016 - North America, Global Summit, Global Summit 2023, Good News, Government, Healthcare, Human Aspects of PM, Human Resources, Identity, Innovation, IT Project Management, Kickoff, Leadership, Lessons Learned, Mentoring, Metrics, Networking, New Practitioners, Nontraditional Project Management, organisations, Organizational Risk, PM & the Economy, PM Think About It, PMI, PMI Congress, PMI Congress NA 2016, PMI EMEA Congress 2018, PMI Global Conference, PMI Global Conference 2017, PMI Global Conference 2019, PMI Global Congress - 2016, PMI Global Congress 2012 - North America, PMI Global Congress 2013 - EMEA, PMI Global Congress 2014 - North America, Pmi global congress 2014 - North America, PMI Global Congress 2015, PMI Global Congress 2015 - Ask the Expert, PMI Global Congress 2016 - EMEA, PMI Hours for Impact, PMI PMO Symposium 2013, PMI Pulse of the Profession, PMI Training, PMI Virtual Experience Series, PMIEMEA17, PMIEMEA19, PMO, PMXPO, Portfolio Management, Procurement, Professional Development, Program Management, Programs (PMO), Project Delivery, Project Failure, project kickoff, Project Planning, Project Requirements, Reflections on the PM Life, Risk, Risk Management, ROI, Roundtable, Scheduling, SeminarsWorld, Social Responsibility, SoftSkills, Stakeholder, Strategy, Sustainability, Talent Management, Teams, Techniques, test, The Moon, Tools, Training, Translations, Videos, Virtual Experience Series, Virtual Teams, Volunteering, war


Agile NASA software? Are you Crazy?

Going to the 2017 PMI Global Conference in Chicago?  

Don’t forget about ASK THE EXPERTS!

Stop by and talk to Dave Maynard or one of the other experts.  There’s more information about it at

Sign Up Now

NASA JSC Engineering

Isn't NASA the epitome of the double-cursed WATERFALL technique?

Wrong NASA was agile before agile was a common term.  As a matter of fact, One of the 17 original authors of the agile manifesto -- Jim Highsmith used to work at NASA.   The question that NASA asked itself was: “How can we, the space ops community, adopt state-of-the-art software development practices, achieve greater productivity and lower cost, and maintain safe and effective flight operations?”

NASA Ames, together with my old “home” JSC (Houston) and JPL are developing “Mission Control Technologies (MCT) software in an integrated agile environment --- with modifications necessary because of human life and safety factors (in a *very* harsh environment).

Traditional requirements processes and documentation was replaced with a team design process which included the customer, design experts and paper prototypes. (Sorry Systems Engineering).  Iterations were delivered to the customers every three weeks with a full release every three month (Sound like NASA-Agile now?) 

Nightly builds were made available to facilitate customer feedback on the team’s progress.  This effort replaces the traditional intensive NASA documentation and reviews with ongoing interactions.  Technical documentation is maintained on a team Wiki which everyone has access to and can contribute to.

Why do this? 

To shorten the delivery cycle, break large software development efforts into smaller more easily manageable pieces. To facilitate direct interaction between the developers and the users.  And to produce a download daily so users always have the means to access the latest version of the code.

Replaced Predictions with Actuals.

Progress is measured by the state of the code, rather than estimations and presentations.  For the MCT this takes three forms.  First, the nightly build, second are the iterations (every three weeks) typically installed in a Mission Control test facility.  And after four iterations the software is released for operational mission control certification.

Manageable Deliveries

With a longer delivery cycle, the more the code, the greater the complexity and the larger number of tests that must be conducted.  A longer cycle means more time from specification of function to delivery.  The greater the time from specification to use, the greater the room for error between user expectation and the software product.  Using a shorter cycle reduces the number of new features and possible regressions.  Agile may not reduce the total number of tests, but it distributes them over time, making it a more manageable effort.

Development Team / Customer Interaction

With a short delivery cycle, the availability of working code for evaluation and feedback, makes it possible to have closely coupled interactions between the development team and the customer.  The developer-customer interaction is very useful to verify new features as they are rolled out.

Fast Response to Change

The shorter development cycle allows the team to better respond to changes.  The software is rolled out in stages, the users respond then the development team can act on this feedback. 


Next time: NASA Agile: Delivery Cycles. 

Reference: American Inst. of Aeronautics and Astronautics; Reston, VA, United States; Agile Development Methods for Space Operations Jay Trimble Nasa Ames Research Center Mountain View CA and Chris Webster University of California Santa Cruz, Nasa Ames Research Center, Mountain View, CA

Posted by David Maynard on: October 18, 2017 02:00 PM | Permalink | Comments (14)

Answering Dave Davis' Risk Question

Hi Mr. Davis!

First, you’ve asked an excellent question.   I think there’s really two parts to it.   Some of the ones you list could affect the project only (resignation) but some of them are corporate level risks (cyber-attack). 

There should be good risk-stewards at the corporate level, working with the accounting and general management folks to forecast and protect against hurricane, tornados, zombies, whatever.   These risks are out of the project manager’s hands and are part of the overall business risk assessment.  You *could* say these are “organizationally accepted risks.” 

That’s all “C-Suite” stuff.   Sure, your project may get washed away in a hurricane, but the PM isn’t really held responsible for insurance, or claims, or set-asides for that.  Perhaps, a PM may get involved in planning for data safe-backups (offsite) but even that is not common.

But!  As a top-notch Project Manager, when you think of these ORGANIZATIONAL types of things, I believe it’s your duty to ensure that the general business folks have considered them.   So, for instance, I had the sprinkler system come on over a weekend (no fire) and it stayed on until Monday.  I never imagined that would happen.  If I was just a bit smarter I would have, and would have politely asked the folks upstairs in the corner office if they had set aside funding to take care 2 feet of water from sprinklers.   I don’t consider this to be a project risk, but an Organizational level risk

So, if you can imagine a business risk and it has some likelihood of occurring you have an honor-bound duty to inform the business risk people about it.    If they don’t take care of it, then you must handle it on the project. 

If it’s a commonly accepted risk taken at the project level (a late deliverable) then it should be in your project’s risk register and you’ll be the grass and the executives will be the lawnmower.

-- Dave

Posted by David Maynard on: October 10, 2017 07:28 PM | Permalink | Comments (5)


Chalk Talk - A Valuable Problem Solving Tool

For some strange reason, I find myself blogging about chalk and chalkboards for a second time.  No, I’m not hung up on them. But, yes, I *do* enjoy good old-fashioned slate and the smell of dusty chalk.  But – that’s not the purpose of the blog.

To make things even more confusing they’ve started painting the inside walls of classrooms where I often show up at - with “whiteboard” paint.  Now that bugs me.   A student walked right up to the wall and started drawing on it with a marker!  It looked pretty much like any other wall.   I kept yelling it was just a wall!   Some of her quicker witted fellow students whipped out their phones and announced, “This is going on Facebook!”  But of course, they were all having a fine time with my old-man ignorance and it was a “white wall.” 

OK.  Back to Chalk-talk. 

Sometimes at NASA, working as a team we’d come across a problem that just seemed impossible.  We’d work for days, sometimes weeks trying to solve a single problem.  I remember multiple times staying up for 30 hours in a row trying to solve one problem – not recommended!  This sort of effort required third-shift coffee, cherry pies from the vending machines and lots of second-hand smoke.  

What’s Third shift coffee?  Each preceding shift was honor bound to have a pot of coffee waiting for the next arriving shift.  So, the guys on second shift, at around 11PM would make an extra strong pot for the third shifters arriving at 11:30 PM.  The first thing a real third shifter would do is to add a tablespoon of instant coffee to each cup.  Everyone knew what third-shift coffee was like.  A hard (not necessarily big) problem required around-the clock third-shift coffee. 

None of this is healthy, smart or conducive to solving complex technical or mathematical problems.  But… we did it.  Our (very good) branch chief would drop in from time to time, ask a few questions and then wander off.  At some point, based upon his instincts, he would call for a “CHALK-TALK.”  This meant we’d have to leave wherever we were working, go to a new / different conference room.  And take turns standing up in front of a chalkboard explaining what the problem was and how we thought it could be fixed.  We each took turns doing this.   

I can’t remember a single time when this method didn’t get us to a solution. We were all tired, grumpy, short-tempered and wired with caffeine, but it worked. Sometimes someone would be talking at the board and the solution would hit us all at-the-same-time like a hammer.  Other times, parts of the group needed to explain it to the others.  A few times only one person would see the solution and explain it to everyone else.   Again, no rules and not much of a pattern fell out.  But I can think of a few guidelines...


  1. Research the problem until you know all about it.  Exhaust all possibilities.
  2. Have a “judge” call for “chalk talk” time.
  3. Remove the group from the area of the problem – the more different the environment is, the better
  4. Have a blackboard, chalk and eraser (OK, whiteboard markers….)
  5. Let one of the group play “teacher” first.  If the solution doesn’t come, someone else takes a turn.  They can restart or build on whatever is on the board
  6. Participants don’t have to be quiet.  I remember them being QUITE vocal.  This involved name-calling, whistling, foot-stamping, whatever… But those sitting couldn’t stop the person with the chalk from expressing what they thought the problem or the path to the solution was.  The chalk was the power.
  7. The person with the chalk could give up at any time.  Someone would have to pick up the chalk, but hopefully not someone who just was “up.”

When a solution is arrived at – everyone knew it.  It was like the room filled with water.  Quiet.  People looked at each other.  Eyebrows went up.  Some people went home to sleep right then!  Other’s went back to (regular) work to try the arrived-at solution

Posted by David Maynard on: September 10, 2017 05:34 PM | Permalink | Comments (9)

"I do not know anyone who has got to the top without hard work. That is the recipe. It will not always get you to the top, but should get you pretty near."

- Margaret Thatcher