............................................................................

presents

presents
"THE LIGHTER SIDE OF PROJECT MANAGEMENT"

HOW PROJECTS ARE BORN

((POSTING ON A LIGHTER NOTE))

How Projects Are Born

Programmer to Module Leader:
"This is not possible. **Impossible**. It will involve design change and no body in our team knows the design of the system. And above that nobody in our company knows the language in which this software has been written. So even if somebody wants to work on it, they can't. If you ask my personal opinion the company should never take these type of projects."

Module Leader to Project Manager:
"This project will involve design change. Currently we don't have people who have experience in this type of work. Also the language is unknown so we will have to arrange for some training if we take this project. In my personal opinion, we should avoid taking this project."

Project Manager to 1st Level Manager:
"This project involves design change in the system and we don't have much experience in that area. Also not many people are trained in this area. In my personal opinion we can take the project but we should ask for some more time."

1st Level Manager to 2nd Level Manager:
"This project involves design re-engineering. We have some people who have worked in this area and some who know the language. So they can train other people. In my personal opinion we should take this project but with caution."

2nd Level Manager to CEO:
"This project will show the industry our capabilities in remodeling the design of a complete system. We have all the necessary skills and people to execute this project successfully. Some people have already given in-house training in this area to other people. In my personal opinion we should not let this project go by under any circumstance."

CEO to Client:
"These are the type of projects in which our company specialize. We have executed many project of the same nature for many big clients. Trust me when I say that you are in the safest hand in the Industry. In my personal opinion we can execute this project successfully and that too well with in the given time frame."

 

[Mathew@PM4K]

HTTP://WWW.ANISHMATHAIMATHEW.BLOGSPOT.COM

HTTP://WWW.ANISHMATHAIMATHEW.WORDPRESS.COM

0 Comments:

INDEX: BEST OF PM4K

27. PM BASICS 007: DECUPLE CONSTRAINTS [POST @ PM4K]

26. PM BASICS 006: SEXTUPLE CONSTRAINTS [POST @ PM4K]

25. PM BASICS 005: PROJECT TRIPLE CONSTRAINTS [POST @ PM4K]

24. UN PROJECT MANAGER UN Superhéroe [POST @ PM4K]

23. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (006) [POST @ PM4K]

22. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (005) [POST @ PM4K]

21. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (004) [POST @ PM4K]

20. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (003) [POST @ PM4K]

19. SWEET DREAMS BUSINESS ANALYSTS [POST @ PM4K]

18. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (002) [POST @ PM4K]

17. TRAITS OF A 'HALO EFFECT' PROJECT MANAGER (001) [POST @ PM4K]

16. PM BASICS 004: WHAT IS PROJECT MANAGEMENT? [POST @ PM4K]

15. PM BASICS 003: WHY DO PROJECTS? [POST @ PM4K]

14. TOP #1 CAUSE OF PROJECT FAILURE [DISCUSSION @ PM4K]

13. PM BASICS 002: PROJECT vs OPERATIONS [POST @ PM4K]

12. PM BASICS 001: WHAT IS A PROJECT? [POST @ PM4K]

11. IN PROJECT MANAGEMENT LOGIC = LOYALTY [POST @ PM4K]

10. PROJECT MANAGEMENT - TWO TO TANGO [POST @ PM4K]

09. TOP #1 QUALITY OF A PROJECT MANAGER [DISCUSSION @ PM4K]

08. ARREST THAT SCOPE CREEP [POST @ PM4K]

07. BEWARE OF FRIENDS IN PROJECT MANAGEMENT [POST @ PM4K]

06. A PROJECT MANAGER IS A SUPER-HERO!!! [POST @ PM4K]

05. PROJECT MANAGEMENT IS NOT A FREEDOM STRUGGLE [POST @ PM4K]

04. PROJECT MANAGEMENT: STAIRWAY TO COMPETENCE [POST @ PM4K]

03. PROJECT MANAGEMENT CIRCLE OF KNOWLEDGE [VIDEO @ PM4K]

02. SECRET RECIPE TO SUCCESSFUL PROJECT MANAGEMENT [POST @ PM4K]

01. PROJECT MANAGEMENT: 3-STEP CIRCLE OF KNOWLEDGE [POST @ PM4K]



[Mathew@PM4K]

 
©  free template by Blogspot tutorial