Business Rules

What happens when you develop a report?

You first outline what question you are trying to accomplish.

You get this by asking the user.

What's next?

You translate the business requirements into working code?

And what if you don't know where to get the data from or how the business rules operate?

You are at the mercy of asking someone else.

And there lies the problem.

Because some people don't necessarily give you what you're asking for.

And they give you the wrong information.

Or incomplete information.

Or don't take the problem you are trying to solve deep enough.

And then you go back to your desk and create a report, which is wrong.

And then it's your problem for creating a piece of crap.

But wait, you say such and such person gave you the wrong information.

They deny it or say they didn't understand the question or didn't have enough time to think it through.

I'm telling you that the report developer is at the mercy of the business domain expert to provide fast accurate business rules which can then be translated into workable code.

And what if you're business rules are not documented.

Well, then, you do have a problem.

That's the way I see it.

When a report developer is dependent on other people to supply what he needs, namely business rules, he is at their mercy for their time and for receiving correct information, because to be honest, the business user doesn't give a crap about you or your project.

To them you are cutting into their precious time and they're trying to get rid of you as fast as they can.

So go ahead and blame IT for all the problems in Reporting and I'll tell you why it's not 100% true.

So when you have a question, choose from the following:

A. Go Away!
B. Incomplete Answer
C. Wrong Answer
D. I don't know
E. Go ask someone else

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Thoughts to Ponder