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.