2-1-1 Purpose

2-1-2 Copyright
Summer 2004, Irvine, California, USA, copyright by Robert E. Perrine, PMP. Offered as is, with no warranty regarding the accuracy or suitability of this material. Copyright reserved. You are, however free to copy and distribute these documents with the following restrictions.

• You may not charge for use or distribution of this material.
• Your usage of this material is conditioned upon your compliance with the PMI Code of Ethics.
• All distributions must be made with the intent to further the collected wisdom of humanity.
• You may not remove my name or my copyright notices from these documents.

2-1-3 Table of Contents
Recursion Project
2 Scope
2-1 Product Description
2-1-1 Purpose
2-1-2 Copyright
2-1-3 Table of Contents
2-1-4 Product Description
2-1-5 Product Details
2-1-6 Revision History

2-1-4 Product Description
The product to be built during the course of this project is a set of documents. It is expected that there will be about thirty total documents, but that number will be refined during the course of this project. These documents must be made available through an internet portal.

2-1-5 Product Details
This product is based upon the Project Management Institute A Guide to the Project Management Body of Knowledge (ISBN 1-880410-25-7), also known as the PMBOK 2000.

When completed, there will be one document to represent each of the key documents described in the PMBOK 2000. Note that the intent is to represent the documents typical of a mid-sized project. Thus, some documents will be merged and others will be excluded. This is necessary so that the methodology is not obscured in a clutter of documents some of which are only meaningful on larger projects.

For a small project, a subset of that methodology can be implemented with about ten documents. A goal for this project is to move beyond the scope of a small project into more of a mid-ranged project. Based upon a preliminary analysis it should be possible to build this product with about thirty documents.

These documents must be easy to maintain, easy to format and easy to distribute. The primary author currently uses Microsoft Word for document creation and a combination of Adobe Acrobat, HTML and zip archives for document distribution. Based upon what is known today, those tools should suffice.

Each document will be created with the intent that it will later be used to generate a template for future projects.

There must be consistency of style across the document set.

The formatting of this set must be appropriate such that templates can be readily applied to professional projects.

In general, it seems that bordering adds to the appearance of documents. However, prior experience has shown that excessive formatting require unnecessary effort to preserve the format. It is recommended that page borders be used instead of section borders to preserve the appearance while simplifying the administration and maintenance of the document set.

This product is expected to have a life well beyond the life of the project. Prior experience in tool creation has shown that a well built tool can continue to be useful for many years. This project should not span more than a few months. This product must be designed to last at least three years.

2-1-6 Revision History

Date	Author	Description
3 Jul 2004	Robert Perrine	Initial release.
4 Jul 2004	Robert Perrine	Wording improvements.
5 Jul 2004	Robert Perrine	Renumbered all documents to match the Work Breakdown Structure.
6 Jul 2004	Robert Perrine	Updated style template and rebuild this document.
7 Jul 2004	Robert Perrine	Re-generate the table of contents.
11 Jul 2004	Robert Perrine	Converted from MS Word to Adobe InDesign
17 Nov 2007	Robert Perrine	Converted back from Adobe to html. I recommend against using Adobe products.