Summary of The bad guy

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

2. Every company has its Bad Guy.

3. The bad Guy …
costs them so muchis so slow
always brings complexity delivers low quality

4. The bad Guy is Mister IS(*) of course !!!
(*) IS : Information system

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

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

7. One hour later …without IS/IT
Employees are nervousCustomers are nervous
Everybody is very nervous Except competitors who are
very happy

8. We have to find another solution !!!

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

10. And they ask each department to manage
their own Information System.

11. Several months later …

12. What’s going on ?

13. We have a teamwork issue.

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

15. We have a lot
of bad guys !!!

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

17. 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 ?

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

19. Stage #1 : The selection.
The selection

20. “First, despite your perception… I have a lot of success.”
“Everybody wants me to work for them.”

21. 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,

22. Stage #2 : Booking IS resources.
The selection Booking

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

24. That’s why all IS projects must be
planed in advance.
Otherwise, minimum delay is
necessary to free resources already
booked.

25. Stage #3 : Designing your idea.
The selection Booking Design

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

27. “Your idea is very beautiful.”
“Unfortunately…”

28. “I will not design your idea for you.”
“But I will design it for our company.”

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

30. “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”

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

32. “…the key assets of the companies.”

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

34. “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).”

35. Stage #4 : Development.
The selection Booking Design Development

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

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

38. Stage #5 : Tests.
The selection Booking Design Development Test

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

40. “To avoid….”

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

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

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

44. We must be sure that the Good Guy really
is a Good Guy.
How to have the Good Guy under control ?

45. The answer is …IS Governance.

46. Information System is a science.
esearches are done to identify
est practices.

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

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

49. “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.