There is a phase in implementation projects where it seems like nothing is happening.
Executive stakeholders begin to wonder what is going on?
Why isn’t there a lot of noise and drama and excitement?
What they don’t see are the members of the project team, heads down, testing.
Doing that first pass.
Making sure that when we engage a larger group of testers that all of the big technical issues have been resolved so they can concentrate on making sure they can do business when it goes live.
This is the un-glamorous work. The risky work. The work that, to do well, requires tremendous concentration.
The work that many organizations gloss over. And pay the price at go-live.
How do we educate executives and stakeholders of the importance of this process? Of the need for concentration during this process? Of the importance of this stage for ultimate implementation success?
In an attempt to make the testing process more visible, we opened up the Issue Log and the Testing Plan for organizational consumption.
If anyone is interested, they can manipulate the Testing Plan to see where we are at in testing.
If someone has an outstanding issue (or are just curious about a pet feature), they can manipulate the Issue Log to see what is out there and what has been resolved.
This visibility has mitigated some of the complaints of “project stagnation” … somewhat.
But this is what is needed to move forward. To provide the foundation for further business improvements.
We can continue the sexier work of shiny new business processes and features later.