Промышленный лизинг
Методички
Are not functional or do not address crucial areas (i.e., QA, CM, testing). Ignore the industry standards and best practices. Look impressive but lack real integration into the business. Use nonstandard project conventions and terminology. Compete for similar resources without addressing this problem. Dont have any performance metrics. Take too long to complete because of bureaucracy and administration. Projects Influence Methodologies Not one single project methodology can solve every project across all industries. For example, the Channel tunnel project linking the United Kingdom to France came with many problems and had major cost and schedule overruns. Project methodologies were developed to prevent such problems. Many project methodologies come close to preventing problems, and many are tailored to specific uses, but it finally boils down to applying solid project management principles. Methodologies affect project management; they affect any project universally in the sense that each methodology: Contains project phases. Measures progress. Takes corrective actions based on defects found. Assigns resources to various phases. Project methodologies are useful to companies only when the tasks are appropriate and applicable. In many project studies, project plans are seldom updated. Why is this? Many projects focus only on satisfying clients during the initial deployment phases instead of conforming to the actual plan as the project proceeds throughout the project life cycle. In Figure 1.2, we see that Project A has no methodology and is filled with process issues as well as problems that actually increase as the project moves along. Additionally, Project B, which has a structured methodology with defined and operational project processes, minimizes the number of problems that may occur on the project. I do not contend that there will never be any problems if a project methodology is in place; it does, however, mean that you have planned for all areas of the project to function while trying to meet the objectives. Figure 1.2: Difference in using a methodology. In assessing any company, we see that project management (PM) methodology does not exist in isolation. Instead, there are other interrelated, connected methodologies, which have a dependency on one another. Figure 1.3 illustrates that there is more than one methodology in an organization, and you need to be prepared for the one you will be using or interacting with. There is a relationship between the various methodologies, including: Sales and marketing methodology. Recruitment methodology. Project management methodology. Development methodology (i.e., specific technical build). This implies that the software or product is built more from a technical perspective than the way a project methodology is managed (e.g., when you think about building a new car, you think about the project methodology youll be using, but hidden within the project methodology is the specific development methodology, which is precise technical steps). Operations and support methodology. Figure 1.3: Typical methodologies used in an organization. It is crucial to understand the bigger picture of what is involved before undertaking any project. For example, the fastest house builders in the world Habitat for Humanity International broke the world record in 1999 by building an entire four-bedroom house in 3 hours 44 minutes and 59 seconds in Auckland, New Zealand, including electrical and plumbing systems. However, the planning and coordination of this project took 14 months, which is another matter. You should not focus just on the actual build phase, which the record focuses on, but see which other methodologies contributed toward making this possible. Habitat for Humanity International used the following methodologies to build this house: A marketing methodology to market the idea to their stakeholders. A recruitment methodology to recruit the necessary volunteers to build the house. A basic project management methodology to estimate and plan this effort. A well-orchestrated development methodology emphasizing teamwork and multiple tasks being performed at the same time. 1 2 3 4 [ 5 ] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 |