Issues In Project Management

Issues In Project wayThis act discusses just about(predicate) twain major(ip) issues in stomachs and stomach counseling. The cardinal major issues this essay going to discuss and analyse are the impacts of encounters if they are non get alongd in a couch and the importance of managing stakeholders in a forge and advise counseling. The essay too discusses about early(a) issues in tramp vigilance that were winding in the illustrated grimace studies.Risk caution is one of the every(prenominal) last(predicate) in all-important(a) requirements in any travails. Projects without encounter get awayment are questionable to its extend toment level and the aftermath post be severe if the dangers are of juicy negative impact. Risk is whatsoeverthing that may happen unexpectedly in a watch which creates positive or negative impacts to the result of the objectify. The probability of attempt house non be accurately predicted and so in that location should be a risk management course of study in every object to call the risks which nookynot be avoided. The risk management plan involves risk identification, quantifying the risk into impact and probability, planning a response which includes avoiding, transferring, mitigating and guideing the risk and the concluding step in risk management plan is to monitor and control the plan. (Webb, 2010)This following plane section of the essay get out discuss about what bequeath happen if risks are not managed in a honk with baptismal font studies. The prototypical instance study dod is Denver International airport baggage discussion carcass. The following section explains the background of the campaign study followed by the issues that alight(p) ascribable to poor scheme management which headed the project to be a roll in the hay chaos.Denver International Airport Baggage Handling SystemBackgroundThe Denver International Airport (DIA) luggage handling step to the fore ment of rules was to be the worlds largest machine-driven luggage organization precisely it became a case of engineering project mishap. The DIA is the largest international airdrome in United States back a land area of 140km and it is the third largest international drome in the world and it can handle more(prenominal) than 50 meg passengers annually. (Calleam Consulting, 2008)The automate luggage system was the critical element of the plan. DIA would have been one of the warring advantages airports providing more efficient operations by reducing the aircraft turnaround era to 30 minutes using this automated baggage system. The original plan was to make use of the automated baggage handling system all everywhere the airport and it was more interwoven than what people actually believed. The system was planned to handle 88 airport gates in tierce concourses, seventeen miles of track and five miles of conveyor belts, 3100 standard carts, fourteen trillion feet of w iring, hundreds of computers connected in a net performance to control the flow, 5000 electric motors, 59 laser arrays, 400 radio receivers and 2700 photo cells. (Calleam Consulting, 2008). All these components explain how labyrinthine the automated baggage handler system is.The construction work of DIA started in November 1989. United Airlines signed and planned to use Concourse A as a hub and it engaged BEA systems to build the Concourse A automated baggage handler system who was the world leader in operating, installing and supplying baggage handling equipment. The project management squad up of DIA approached BEA to build the baggage system for all three concourses and for the whole airport to transfer baggage automatically.IssuesMassive problems started in twist the baggage system which was very analyzable as they never thought of such complexness. Even though the airport was complete, it did not open as chronicled in October 1993 because of the problems in baggage system and the completed airport was idle for more than 16 months which also missed the opening dates in April and May, 1994 and the opening was slow to marching 1995. (Neufville)The DIA airport authorities arranged a demonstration of the baggage system for the media without ratting BEA. There was complete disaster in the demonstration as the bags were depleted and clothes were thrown out from the bags. This was in April, 1994 and the opening was delayed to May, 1994. BEA systems claimed that the airport faculty used the system incorrectly and there was no fail in the system.System testing was struggling and airport built a manual trolley system as per the log plans recommendation. The delays increased the live for owners and airlines and huge amount of money was wasted collectible to the idle use of the airport. In August, 1994, DIA started fining BEA for further delays and not able to complete the system.The airport was assailable on 25th February, 1995 with the automated bagg age system implemented in single concourse instead of implementing in all the concourses. All other part of the airport used the manual trolley system since the automated baggage was not functioning as expected. The maintenance cost for the system which was not functioning properly was one million dollar per month and so they scrapped the whole system in August 2005 and implemented the manual system in all over the airport. (Calleam Consulting, 2008)Risks that were involvedThere were umteen possibilities of risks in the above mentioned scenarios and one of the reasons why this project failed is due to ignorance of risk. The complexity of the baggage allowance system was underestimated. The project was initiated too late because of not understanding the risks involved in it and the complexity level of the system. Due to not understanding the complexity level, the project was planned to complete in two years which was insufficient to complete such a complex project and due to this th e project team made lot of faultings to meet the schedule which was impossible.Any automated baggage handler system is subject to risk. The disaster cannot be said as a bad luck or due to need of qualifications since the system was installed by BEA systems one of the best suppliers in baggage system. This complex project should be viewed as a look for project and in a research project success cannot be expected in a short time unless it is managed well.Although the airport project management team and BEA systems know that there is a big risk in completing the project in two years time, they started the project and they failed to identify all the major risks involved in issueing with the complex project. Several managers of BEA advised the BEA senior management team that this complex project is a four year project and not a two year project. Both airports chief engineer and BEAs senior management team ignored the advice and continued with the project.The BEA management structure tout ensemble failed to recognize what descriptor of risk they were entering into by taking this project and committed to proceed with the project. If they have recognized, they would have at least taken steps to get over the risks involved in this project and find some scope to achieve the goal of the project within the deadline.Some of the issues were un sure and since the airport project management team and BEA does not plan any risk management, the unpredictable issues created many impacts on the project since they does not know how to handle the issues. The project team couldnt manage not only the unpredictable issue, some predictable issue a ilk(p) major adept problem that encountered in the project was not able to be handled by the project team. This was due to neglect of developing a proper risk management plan in the project.Importance of managing Stakeholders in a projectThe other major mistake done by both airport project management team and BEA was excluding the airlines from the discussions who were the key stakeholders of this project. While making key project decisions, stakeholders should be include to produce a winning strategy. (Calleam Consulting, 2008). If the stakeholders are excluded previously and included finally, they will consider for significant changes in the project which leads to nullify the previous work done in the project. This was proved in this project when airlines asked for many changes uniform adding maintenance tracks and ski equipment racks BEA and airport project management was forced to accept the changes since they initially avoided stakeholders from the negotiations although there was a term that no changes would be made. shift study deductionThe case study can be reason from the above illustrations and discussions that the DIA baggage handling system project failed due to not understanding the complexity of the project, no risk management plan, poor stakeholder management, lack of communication, poor desi gn and planning of the system and finally lack of management insight in the project which led Denver International Airport Baggage Handling System project to be an example for technology project failure.The next section of the essay will discuss about another case study associate to risk management. The Second case study used is Heathrow terminal 5 funny house. The following sections explains the background of the case study followed by the issues that aroused due to poor risk management which headed the project to be a complete chaos.Heathrow ending 5 ChaosBackgroundPublic enquiry of Heathrow Airport fifth terminal building proposal started in May 1995 and ended in March 1999 with the drawn-out public inquiry in British planning history be eight million pounds in legal fees. The terminal was expected to complete by 30th, March 2008 after the approval from UK government. Three twenty million pounds were allocated for planning risks. The terminal includes everything from facili ties to handle jumbo aircrafts, car parks, service tunnels, a complete transport interchange, a hotel, shops, catering, highest customer service and it can handle thirty million passengers a year. The final stage 5 was constructed curiously to stick out by British Airways (BA) flights. (Hancock, 2009)IssuesThe opening of Terminal 5 after fifteen years of planning and construction with spending 4.3 billion pounds should have been a great moment for British Airport Authority (BAA) and British Airways (BA) and it head to be one of the biggest chaos. The problem started when the terminal supplys couldnt reach there in time due to difficulty in parking their cars, the staff security screening and well-known(prenominal)isation was delayed too, which led to accumulation of baggage. Another major reason was the collapse of state-of-art baggage handling system due to technical problems which was designed to handle 12,000 baggage per hour. (BBC News, 2008)As a result, more than 23,000 b ags were mazed and 500 flights were cancelled. BA lost 16 million pounds in the first five days of operations. (Thomson, 2008). BA blamed that the staffs provided were not familiar with the untested systems and only few staffs were provided to handle the baggage system. BAA said that the baggage got clogged due to few numbers of staffs from BA and not due to the baggage handler system. Later BAA spokeswoman agreed that there was some software problem in the baggage handler system and it is completely BAAs responsibility. (Hancock, 2009)BA claimed that it was preparing for the past three years to switch to Terminal 5 and thousands of staffs have been trained to handle the new system and they got delayed to their workstations due to the difficulty in parking their cars. (The Times, 2008). The British Airline Pilots standoff (BALPA) wrote a letter to the government ministers and shareholders blaming all BA executive directors for the Heathrow Terminal 5 chaos including the chief ex ecutive. (Milmo, 2008)Risks that were involvedRisk turns to be an issue if it happens. If risks are not managed even after knowing the probability and impact of the risk is high, then there will be a chaos like in this case study. The chaos in Terminal 5 was due to poor management not only for few days but from the initial stage of the project especially lacking risk management. The project would have been a big success if there was risk management for this kind of mega project.There were already defects in the baggage handler system during the trail process before opening Terminal 5 and it was inform to BA. The simulations used a less amount of baggage, less passengers and handlers to test the system. BA management ignored the concerns. They didnt test the system properly and they ignored to manage the risk. They blamed each other instead of solving the problems. BAs chief executive admitted that they compromised testing due to the delays in building the terminal.The baggage handl er staff spent much time in searching for the parking place due to wrong sign boards and directions. The staffs were not trained and not familiar to handle the baggage handler system which was another risk. BAs chief executive admitted that they didnt train staffs and didnt familiarize them. (Massey, 2008). compositors case study ConclusionAlthough the Heathrow Terminal 5 project was completed on time and on budget, it is one of the major catastrophic disaster projects. If the systems were tested properly, staffs were trained and familiarisied and if risks have been managed properly, the Terminal 5 project would have been the most successful project. The case study can be cerebrate from the above illustrations and discussions that the risk management is one of the pivotal requirements in project management and ignoring to manage them will lead to failure or disaster of projects like Heathrow Terminal 5 chaos.Case call for Online shopping systemThis is one of the case studies that I ainly go through while learning the faculty IT Project Management. This case study project was to develop a online shopping software system for the client subway system Super stores and the project was carried out with 8 project teams members including the project manager. We cover most of the issues in project management in the yack and seminar academic academic sessions. This can be illustrated with one example about managing risk in this project. We were asked to be with the risk log for this case study and we discussed about all possibilities of risks that will affect this online shopping software development system. We created the risk log and quantified the risks using its impact on the project and probability of happening. It was a personal take that taught me the corporeal importance of risk management in project management. (Classroom take, 2010)ConclusionIn all the above produced case studies, the essay discussed and analysed the major issues related to proje ct management involved within the case studies with illustrations of the issues and discussed with examples. From the case studies and illustrations, it is concluded that project management issues are vital to any kind of projects especially for mega projects like Heathrow Terminal 5 and Denver International Airport Baggage Handling System and the project would not succeed unless it is managed well.Word Count 2451BibliographyBBC News. (2008, March 28). Other airports rocky starts .BBC News. (2008, March 30). What did go wrong at Terminal 5? .Calleam Consulting. (2008). Denver Airport Baggage Handling System Case Study Calleam Consulting. Retrieved declination 17, 2010, from http//calleam.com http//calleam.com/WTPF/wp-content/uploads/articles/DIABaggage.pdfComputerworld UK reporters. (08, March 27). Heathrow Terminal 5 chaos RoundUp. Retrieved declination 15, 2010, from http//www.computerworlduk.com http//www.computerworlduk.com/in-depth/it-business/1268/heathrow-terminal-5-chaos- roundup/Dunn, P. (2008). Courting Disaster. Retrieved December 14, 2010, from http//www.squarepegint.com http//www.squarepegint.com/pdf/RecentResearch/CourtingDisasterFinal.pdfExperience, C. R. (2010). IT Project Management. Sheffield Hallam University.Hancock, D. (2009, May 8). Heathrow Terminal 5 success or Failure? Retrieved 12 17, 2010, from http//www.slideshare.net/ http//www.slideshare.net/Hank5559/heathrow-terminal-5-success-or-failureMassey, R. (2008, May 08). BA chief Willie Walsh brands Heathrows Terminal 5 a national embarrassment.Milmo, D. (2008, April 8). Pilots slam BA management over Terminal 5 chaos. p. 1.Neufville, R. d. (n.d.). THE BAGGAGE SYSTEM AT DENVERPROSPECTS AND LESSONS. Retrieved December 18, 2010, from http//ardent.mit.edu http//ardent.mit.edu/airports/ASP_papers/Bag%20System%20at%20Denver.PDFThe Times. (2008, March 28). Terminal 5 launch disaster brings spend chaos.Thomson, R. (2008, April 02). IT experts tackle baggage system problems at Heathrows Ter minal 5. Retrieved December 18, 2010, from http//www.computerweekly.com http//www.computerweekly.com/Articles/2008/04/02/230084/IT-experts-tackle-baggage-system-problems-at-Heathrow39s-Terminal.htmWebb, L. (2010). crush Slides. Retrieved December 16, 2010, from http//shuspace.shu.ac.uk http//shuspace.shu.ac.ukWilliams, C. (2010). Project Management Risk Management. Retrieved December 15, 2010, from http//www.projectsmart.co.uk http//www.projectsmart.co.uk/project-management-risk-management.htmlSheffield Hallam UniversityFaculty of Arts, Computing, engine room and SciencesIT PROJECT MANAGEMENTIndividual Reflection20/12/2010Prasnnaa Kumar NachimuthuB0045907 samarium Database ProfessionalIntroductionThe purpose of this essay is to write about the unmarried reflection of my personal experience in the module IT Project Management held during Sep 2010 Dec 2010. This essay produces my learning experience and my experience of works in a team during this module which helps to reflect upo n my learning experience in the module.This module has taught me many things about project management from how to manage a project as a project manager, how to be a good team player and work in team, and most of the topics in project management. This is one of the module I really enjoyed working with my tutors and all my colleagues. The tutors were really interactional with me and everyone in the class and all of the lectures and seminars were very interactive rather than a boring session. The interest of me in this module can be proved with my presence in all the lecture and seminar session without missing a single lecture or tutorial session from the beginning to end of this module.The beginning week of the lecture explained me about this module, project and its definition. The later seminar session involved practical teaching of knowing more about project and I was put into a congregation. Every week, I learnt a new topic about project management and silent how to act to issue s in real time environment. For example, in one of my lecture session, I was given a case study about the problems involved in the biggest building in Sheffield.We understood the case study and I was asked to be in a group to work as a developer of the building and come out with possible solutions to answer the problems of the buyers of the building which make up of my colleagues in another group. While working in the group like a developer, I was thinking as I am the real developer and was trying to come out with possible solutions with my other colleagues in the group. past I, with my colleagues as developers met the buyers group and answered the possible solutions thinking them as the real buyers. subsequently the session, I was completely satisfied that I have learnt something today.This is one of the examples, and every week, due to working in a group, helped me to handle the issues and answer the project board as a project manager and also ask questions to project manager a s a project board member.I had the opportunity to produce the first assignment as a group work. I was the project manager in the group and had to assign the depute in which I found it easy because we had breakdown the tasks, worked on it individually, discussed and produced the final document prior to the deadline.ConclusionI conclude from the above produced illustrations of my personal experience that I am completely satisfied the way the module was taught to me and I enjoyed working with my colleagues in a team. I personally thank my tutors for teaching me the project management skills in an interesting, interacting and practical way and I would definitely recommend this module to my colleagues.Word Count 529