49
THE BAD GUY IN YOUR COMPANY … AND HOW TO HAVE HIM UNDER CONTROL

The badguy summary

Embed Size (px)

DESCRIPTION

Summary of The bad guy

Citation preview

Page 1: The badguy   summary

THE BAD GUY IN YOUR COMPANY

… AND HOW TO HAVE HIM UNDER CONTROL

Page 2: The badguy   summary

Every company has its Bad Guy.

Page 3: The badguy   summary

The bad Guy …

costs them so muchis so slow

always brings complexity

delivers low quality

Page 4: The badguy   summary

The bad Guy is Mister IS (*) of course !!!

(*) IS : Information system

Page 5: The badguy   summary

What can we do ? We have to find a solution !!!

Page 6: The badguy   summary

“Mister IS should only support us. He is the tool, not the core of our activity. We should fire Mister IS.”

Page 7: The badguy   summary

One hour later …without IS/IT

Employees are nervousCustomers are nervous

Everybody is very nervous

Except competitors who are very happy

Page 8: The badguy   summary

We have to find another solution !!!

Page 9: The badguy   summary

The job of Mister IS is a piece of cake. Each department should manage its own IS. We should do it by our own.

Page 10: The badguy   summary

And they ask each department to manage their own Information

System.

Page 11: The badguy   summary

Several months later …

Page 12: The badguy   summary

What’s going on ?

Page 13: The badguy   summary

We have a teamwork issue.

Page 14: The badguy   summary

In fact, since Mister IS left and all departments are doing his job …

Page 15: The badguy   summary

We have a lot of bad guys !!!

Page 16: The badguy   summary

“Ask Mister IS, to give us his point of view,You should.”

Page 17: The badguy   summary

Hey, Mister bad guy Mister IS, we are not so happy with your job.

Your are slow,

Your are too expensive

You are adding complexity

You deliver low quality

Why are you so bad ?

Page 18: The badguy   summary

“OK. Let’s come with me through my journey : Information System project management through 5 stages.”

Page 19: The badguy   summary

Stage #1 : The selection.

The selection

Page 20: The badguy   summary

“First, despite your perception… I have a lot of success.”

“Everybody wants me to work for them.”

Page 21: The badguy   summary

Be sure that your idea will bring enough value to the company before wanting to start the journey of IS project.

Because competition with your colleagues will be fierce,

Page 22: The badguy   summary

Stage #2 : Booking IS resources.

The selection Booking

Page 23: The badguy   summary

“Our CFO asked us to optimize resources cost. That’s why they are shared resources.”

Page 24: The badguy   summary

That’s why all IS projects must be planed in advance.

Otherwise, minimum delay is necessary to free resources already booked.

Page 25: The badguy   summary

Stage #3 : Designing your idea.

The selection Booking Design

Page 26: The badguy   summary

“First, I need to strongly analyze your idea. What will be the consequences of implementing your idea. ”

Page 27: The badguy   summary

“Your idea is very beautiful.”

“Unfortunately…”

Page 28: The badguy   summary

“I will not design your idea for you.”

“But I will design it for our company.”

Page 29: The badguy   summary

“Your beautiful idea is often a nightmare for your colleagues. It may trigger some changes not manageable at all for them.”

Page 30: The badguy   summary

“Because you are naturally focused only to your activity. I need to explain to the others what will be the consequences of your idea to their activities”

Page 31: The badguy   summary

“In the today digital age of humanity, Information Systems is one of...”

Page 32: The badguy   summary

“…the key assets of the companies.”

Page 33: The badguy   summary

“I (Mister IS) am working like an architect for the company.”

Page 34: The badguy   summary

“Once I have a clear understanding of what are the Business Requirements for all departments related to your idea, I need to find the best way to implement them in our architecture (information System).”

Page 35: The badguy   summary

Stage #4 : Development.

The selection Booking Design Development

Page 36: The badguy   summary

“This is part is usually … a piece of cake.”

Page 37: The badguy   summary

“Development is really a small part of the story…and unfortunately only the visible part.”

Page 38: The badguy   summary

Stage #5 : Tests.

The selection Booking Design Development Test

Page 39: The badguy   summary

“ I will perform as much as tests as you allowed me to perform.”

Page 40: The badguy   summary

“To avoid….”

Page 41: The badguy   summary

Well… The Bad Guy may be not so bad. In fact, the Bad Guy may be a Good Guy.

Page 42: The badguy   summary

The Bad guy is The Good Guy. That’s all ?

Page 43: The badguy   summary

But how to be sure that this new Good Guy is really good and not bad.

Page 44: The badguy   summary

We must be sure that the Good Guy really is a Good Guy.

How to have the Good Guy under control ?

Page 45: The badguy   summary

The answer is …IS Governance.

Page 46: The badguy   summary

Information System is a science.

Researches are done to identify best practices.

Page 47: The badguy   summary

IS Governance procures framework to help Companies to follow best practices in Information System management…

Page 48: The badguy   summary

Business teams don’t need to worry anymore and can focus on their own activities.

Page 49: The badguy   summary

“I Hope you have enjoyed this story.”

The three mains points to remember :

IS Projects are not just pieces of code writing but a complete change of how the company will work,

IS projects are risky … that is why they are so long and complex,

Best practices exist to reduce risk and give transparency and confidence to stakeholders.