Requirements analysts: there are no fences… deal with it!

Once again I have heard from a colleague from the development discipline that a requirements analyst is proving to be an obstacle to success because once the customer signs off on the requirements specification, the analyst considers his work to be done and disappears over the horizon.

Very […]

Process Exercise: 4/6

In Part 3, we identified problems with the As Is process by interviewing our fictional customers individually and by having a group workshop. We did this in the light of the strategic objectives of the business.

We need to restructure the As Is model to take into account these problems and […]

Process Exercise: 3/6

In Part 2 we took a moment to remind ourselves that the customer owns the process and that we must be sensitive to that.

Having been presented with a documented As Is change control process, we must investigate what the stakeholders think about that process. There are different techniques available to […]

Process Exercise: 2/6

In Part 1 we took a look at a sample As Is change control business process as presented to us by our fictional customer.

The customer owns the process

Don't go stomping all over the customer's processes like you own them

Our next goal is to produce a To […]

Process Exercise: 1/6

In a previous series of posts we took a look at drawing workflows. However, before you draw a workflow, you really have to understand the underlying business process.

Remember that our definition of a workflow referred specifically to the identified work object. This is because the workflow does not cover the […]

Introduction to drawing workflows: Afterword

In the previous posts on this topic, I have suggested a definition of “workflow” and I built on some high level statements of requirement to draw a visual model of a leave request workflow.

I have broken down the drawing into several steps for the convenience of demonstrating the technique. However, […]