Issacons - Guidelines for Project Managers

Notes:

Issacons open a new browser window. If you prefer to read the Issacons as text rather than slides, click the 'A' button on the first slide. To return to the Issacon index page click the light bulb button. To return to this page when done, just close the window.

If this is your first visit to this Issacon page, then take a look at Issacons 1001 and 1002 first.

IAC1001 discusses four fundamentally different "Areas of Project Management Application" (APMA), i.e. different types of project each requiring different approaches to their management.

IAC1002 describes the structure of the "Issacon Knowledge" in terms of level in a knowledge hierarchy.

1001 (General) | 1030 (PM Guidelines) | 1060 (WBS, Planning)
1100 (Risk) | 1125 (Scope) | 1150 (PM Models) | 1175 (Quality)
1200 (PM Forms) | 1275 (Job Descriptions) | 1300 (Time) | 1325 (Cost) | 1350 (People)
1400 (Contract/Procurement) | 1430 (Info/Coms)

Issacons© (Issues and Considerations):
Project Management Guidelines for Program Managers
A basis for "Good Practice" in a multi-project organization

If an organization is to be successful in the delivery of its projects, it is essential to establish standards by which those projects are selected, managed and delivered. And these standards must be consistent with the organization's strategic plans. While tomes have been written on "What is project management" or "How to do it" there appears to be very little in the way of step-by-step recommendations for establishing consistent successful performance across many projects in the same organization.

The following Issacon presentations have been adapted from work done by teams of project managers working in large public and private organizations. These managers were responsible for projects ranging from a few thousand dollars to multi-million, and across application areas ranging from construction, operation and maintenance to information systems, software and R&D.

A set of twenty-four Guidelines are offered in a "Universal" format and are recommended as "Good Practice". By adopting them and customizing them to suit your particular environment, they can become the basis for "Best Practice" in the management of projects in your organization. They are listed in the approximate order in which they will be encountered in the basic four-period sequence of the natural life cycle of a typical project. Of course, some will argue about the sequence, but we've done our best!

The content and structure we have used throughout is shown in Issacon #1030, slide #7.

Preamble to project management guidelines

1030a. The What, Why and How Much of Successful Manuals: What can you tell me about developing successful manuals for project management?
1030b. Benefits and Tips on Writing Successful Manuals: What tips can you give me about developing successful manuals for project management?
1030c. Developing Successful Manuals: How do I go about developing a successful manual for project management?
1030. Project Management Guidelines: Introduction to Good Practice: Why guidelines, what should they consist of, and why not policies and procedures?
1031. Project Management Guidelines: Checklist: What Guidelines do I need?
1032. Project Management: Introduction to Model Guidelines: Please tell me more!

Phase 4: Transfer

1056. Project Management: Model Guideline #22: Transfer of Product to Customer
1057a. Project Management: Model Guideline #23 - Part A: Final Project Review & Audit 1
1057b. Project Management: Model Guideline #23 - Part B: Final Project Review & Audit 2
1057c. Project Management: Model Guideline #23 - Part C: Post-Project Operational Review
1057d. Project Management: Model Guideline #23 - Part D: Post-Project Deliverable Review
1058. Project Management: Model Guideline #24: Project Close-out
1059. Project ManagementGood Practice Guidelines: What are some of the management issues we may face in introducing your guidelines?
1059a. Procedure Manual (EngCon): I have to prepare a Procedures Manual for my construction project. What should I include?
1059b. Procedure Manual (NewTech): I have to prepare a Procedures Manual for my IS/IT (or R&D) project. What should I include?

1001 (General) | 1030 (PM Guidelines) | 1060 (WBS, Planning) 1100 (Risk) | 1125 (Scope) | 1150 (PM Models) | 1175 (Quality) 1200 (PM Forms) | 1275 (Job Descriptions) | 1300 (Time) | 1325 (Cost) | 1350 (People) 1400 (Contract/Procurement) | 1430 (Info/Coms)

Issacons© (Issues and Considerations): Project Management Guidelines for Program Managers A basis for "Good Practice" in a multi-project organization

Preamble to project management guidelines

Phase 1: Conception

Phase 2: Definition

Phase 3: Implementation

Phase 4: Transfer

Home | Issacons | PM Glossary | Papers & Books | Max's Musings Guest Articles | Contact Info | Search My Site | Site Map | Top of Page

1001 (General) | 1030 (PM Guidelines) | 1060 (WBS, Planning)
1100 (Risk) | 1125 (Scope) | 1150 (PM Models) | 1175 (Quality)
1200 (PM Forms) | 1275 (Job Descriptions) | 1300 (Time) | 1325 (Cost) | 1350 (People)
1400 (Contract/Procurement) | 1430 (Info/Coms)

Issacons© (Issues and Considerations):
Project Management Guidelines for Program Managers
A basis for "Good Practice" in a multi-project organization

Home | Issacons | PM Glossary | Papers & Books | Max's Musings
Guest Articles | Contact Info | Search My Site | Site Map | Top of Page