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 […]

Trust

I believe that when you hire a hound with a good pedigree and training, you ought to follow where it is going and not stop it so you can insist it explain why it uses one sniffing technique and not another.

It seems to me that this is generally the case […]

Make assumptions

In the world of systems development, “assumption” is kind of a dirty word, but sometimes it can be a good thing.

Assumptions are only bad when they are not confirmed with the customer. However, as a business analyst, your job is to put your thinking cap on between interviews/workshops and you […]

Amongst our business rules are… I’ll come in again

Business rules are key to the efficient and flexible functioning of BPM systems, but what should the analyst do when the Business does not know what the rules are?

Wait a moment! Surely the Business always knows what its own rules are. Not necessarily. Businesses often have to respond quickly to […]

Who holds the stake?

On any project, it is important to understand who the stakeholders are, what the nature of their stake is and what effect they are likely to have on the project.

No, not this kind of stake holder.

And by “stakeholder“, of course, I don’t mean Buffy the Vampire […]

The Grand Masque Ball

What does it mean to say “this is a solution masquerading as a requirement“?

Years ago, as a junior analyst, I worked on a project for a holiday company. The specific functional area I was involved in had to do with making the bookings themselves. A thorny topic within that was […]

The customer isn’t the only consumer

It is all too common for analysts to submit their artefacts only for customer review.

Certainly, the business SMEs have to confirm that the business analysis artefacts accurately reflect their business model and that the requirements artefacts accurately represent their business needs.

However, the business customer is often not […]

Four monkeys

Does your organisation have a process or a behaviour which you cannot explain? When updating your IT systems, do you insist on replicating those processes within the new solution, even though there is no benefit to your business? Do you continue to do things the same way because “it has always been done […]