Project support can be categorized into three main areas of support, namely:

Level 1 support: Basic support that must be resolved within two hours.

Level 2 support: Intermediate support that must be resolved within one day.

Level 3 support: Advanced support that has to be resolved within one week.

4. First, you would need to assess the situation and solicit valuable input from project managers, executives, and project staff as to the shortcomings of the enterprise project methodology. You should concurrently assess the current project tools, techniques, training, and processes being used and then formulate a recommendation with an action plan. This is to be presented to the company executives, recommending the support needed, including the support agreements that need to be put in place to get the methodology back on track.

5. Either the QA or the PMO department can maintain the methodology, depending where it is located. It really depends on the organization.

6. To support any methodology, you need to understand the size and complexity of the methodology (i.e., complex waterfall or open source methodology), the number of users, and which components of the methodology were being used at which times. This could imply that you may need to support project templates or processes, provide continuous training to the users, and upgrade existing methodology software tools. It is wise to establish a service-level agreement with the organization or project teams to provide a support model for them.

И Л1ММ1Ы1ДДД1

Chapter 7: Project Templates and Techniques

Establishing a Template Road Map

Templates also referred to as artifacts or boilerplate templates are essential to the success of any project. Templates are seldom found bundled together nicely in a box, ready for use. Project or development managers do not want to spend the time to create new project templates for their projects. Instead, they benefit greatly from using a wide variety of tried and tested methodology templates, which gives them time to concentrate on the actual project.

This chapter provides a reliable source of useful methodology templates that might be required by project or development managers during specific project phases. Whether managing projects or actually developing the technical detail (i.e., design or build phase), you will face constant change. Methodology templates support the user in creating and maintaining project data/information in a formalized and structured manner. Templates also focus on guiding users to specifically define key deliverables, addressing issues such as quality, scope, resources, risk, and cost. These templates help project team members gain a better understanding of the project and its associated tasks. Table 7.1 lists advantages and disadvantages of project templates.

Table 7.1: Advantages and disadvantages of project templates

Although the lightweight methodology family discussed in previous chapters does not encourage large amounts of project documentation, it requires some methodology templates.

iJJ..Hl8W

лл1мм1ы1ВДД1