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

News

The Rubber Hammer. Designing out problems before they occur.

Just after writing one of our previous posts, I was listening to a book called ‘Start With Why: How Great Leaders Inspire Everyone To Take Action’, by Simon Sinek.  During one of the early chapters, Sinek Read more…

News

In-house testing and ‘no, we don’t test data’

As I mentioned a few weeks ago, I spent the day at SITS.  I had some really interesting conversations  and some truly frightening ones, so beware.  We’re also working on bringing some guest posters to Read more…

News

An Approach to Estimating

Our experience within IT projects and particularly within ITSM projects revolves around the time critical nature of projects and the need to have everything immediately (whether this is true or not is up for discussion). Read more…