Web site designers - Chapter 10: Working the Project Plan 221 If
Chapter 10: Working the Project Plan 221 If your organization already has certain methods that they use for defining terms and concepts for creating risk categories, use them when defining your risk management plan. Examining typical risks The following list includes some examples of some of the risks you may encounter and should plan for during your software project: Key resources (materials and personnel) leaving your project Technology becoming obsolete Stakeholders attempting to enhance the scope of your project (scope creep) Leadership changing direction Labor disputes or strikes Schedule delays due to issues with off-site resources Personnel resources being squeezed because they are working on too many projects simultaneously Lack of commitment to project funding Software testing revealing major bugs that could impact the timeline Getting a plan together We re sure you can think of other risks for your specific projects. The more often you create project plans and risk management plans for your software projects, the easier it will become to develop risk management plans. As we said in Chapter 1, there are nine knowledge areas, identified by the Project Management Institute (PMI), to consider in project management. These knowledge areas interact with and affect each another. The knowledge area that impacts risk is (unoriginally) called project risk management. Table 10-1 lists the six processes involved with project risk management, as well as a brief definition of each process.
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.