Typically, the test environment down times and the associated tester idle time is tracked across the STLC. In fact the 'Environment Availability' forms one of the dependency metrics. When the Test Manager closely monitors this downtime statistics, several risks, rework, cost overruns can be mitigated or planned around.
For instance, if there is a downtime observed due to access blockage on other interfacing systems, there can be service virtualization implemented. A downtime associated with the DB down for backups or for batch runs can be avoided by scheduling the backups or job runs as a nightly run.
The real catch is when it comes to T&M project, where you will tend to bill this downtime but have to negotiate with customers with right rationale!
No comments:
Post a Comment