Whatever techniques and methodologies are employed during a project, we see different stakeholders brought in at different stages. Typically, ITSM projects follow a waterfall process and a quasi Prince 2/PMP approach to managing the project.  This is understandable due to the familiarity of these approaches to many of us.  Certainly, other approaches can be utilized, SCRUM and Agile to name just two.  They certainly have places in various phases of the implementation process.

But what about our actual approach to quality?  Typically, as testers, we’re engaged after projects have been planned, budgets have been signed off and expectations have been set.

We’d like to do things a little differently (and in coming posts we’ll delve more into the ways we can help a little earlier on in the lifecycle).  Ideally, we’d like to work in projects at the planning, budgeting and expectation phase (also often known as initiation)!  Why? Because we think that by looking at quality early on helps to design issues out before they become issues.  Our experience at the tail of the implementation can be valuable at the beginning of a project.

We can help clarify misunderstandings, help clarify the implications of particular decisions.  We can help develop strategies that will save testing time, prioritise risk management and coverage.  We think we can help deliver projects quicker and cheaper.

Related Posts


Is ITSM really ready ‘Out of the Box’?

As ITSM has evolved in recent years, there has been an appetite and ability to move towards ‘Out of the Box’ implementations where not a stitch of code is changed in the ITSM solution during Read more…


Preparation is key

So, you’ve identified the need for a new ITSM system.  You might be starting from scratch (although that’s never really the case).  You might be upgrading between versions or procuring a system from a new Read more…


Don’t Disrespect the Data

There are many moving parts that ITSM Implementation teams need to consider in the scope of a project. Commonly the main focus is on code and configuration and second to this is data. This is Read more…