What Is Project Management?

Homework: What are some IT-project management cases I can write a research and analysis about?

• I'm required to perform research and analysis on an IT project management success or failure case. Based on what we have learnt in class, analyze as to why the project succeeded or failed to meet its project objectives. I cannot find a suitable case, the case is IT-related and should include how the project manages risk, control, resources, time/schedule, cost and so on. Only based on these management criterias can I do an analysis report.

• Answer:

  Communication - Just one word we use everyday in many contexts but is the key element for any IT project to be a success or failure. There are other important factors, whether your team is globally dispersed, did you handpick your team based on the technology/platform your apps are on and their skill sets? In today's world, you cannot ignore the offshore team management, handling multi vendor relationship and how often you visit offshore to see how teams work thousands of miles away and if they have any zeal in them to work for you or your just another run of the mill client, they are asked to work for by their employer. Its not just important but imperative to have frequent meetings and any/all channels of communication with the team open - written, verbal, formal, informal. Clear Requirements (or not) could as well affect the project schedule, planning and risks. I have first hand experience working for companies that have no formal/frozen requirement but they have ridiculous  deadlines which everyone knows from the beginning can never be met but they still keep on beating the bush to chase something they can never achieve as they have still not realized that IT is an enabler or a catalyst but the business requirement is a fundamental core which has to be in place to make the foundation strong. Clear requirements are required to get clear estimates Documentation is crucial and developers tend to take it lightly as they think its a shear waste of time. This thinking should be changed and its the IT Managers job to plan and budget time/resources for the same. Testing/QA - Discuss with business and Define standards for your product and make sure it is tested thoroughly before released for the business review. Unit testing, Peer reviews, System testing, Integration testing, Smoke & Sanity testing must be done before launching the project. Add Buffer time in your plan for each task to mitigate any risks due to any reason. Hire Technical Leads/Architects sooner than later. You need to have appropriate ratio of motivators to followers within the team. Do not entertain Change Requests as Requirements during construction phase. Stay Cool and Calm but keep your eyes/ears open and must not ignore the team's grievances. Keep the team's spirit high. Discuss the issues with the team in a formal or informal way. Each of the above sub headings can be elaborated and there can be n number of case studies just on each topic. Let me know if this helps else I can try to assist you some more pointers and real time examples.