Documentation & maintenance of documentation is one of the hardest and important activities in Project Management. Hundreds of plans, mails, progress tracking, change requests, document updates, contract documents, etc are few examples of documentation events in project life cycle. There are three main formats used to represent information in documents.
1. Text format – This is most used format as we are trained to write paragraphs & pages from our childhood.
2. Tabular format – This is used when a matrix or log type of information representation is required i.e. responsibility matrix, risk log.
3. Tree hierarchical format – This type is used to depict whenever parent-child relationship exists between different elements. This is the prevalent type used in all “Breakdown Structures”. If you analyze you can see, basic structures built-in Mind mapping is very much tree hierarchical in nature. That’s why Mind Mapping technique can be used directly into your project documentation.
Project Management Documentation formats
Breakdown structures are important document formats throughout Project Management Life Cycle. One can see Work BS, Resource BS, Risk BS, Organizational BS used in most of the Project.
Breakdown structures follow the general principle of life –
“What you think as a big & unachievable can be achieved by breaking it down into smaller pieces & successfully finishing all smaller pieces leads to completion of the big”.
I like to give simple and effective example here. You are about to have a big buffet lunch. If you think of eating all in one stretch, then it is surely unachievable. You are finishing that tasty feast by eating one mouth at a time.
In Project Management, Breakdown structures are hierarchical representation of information based on certain broad element at the higher level and detailing it out in the descending levels (This is what you do exactly in Mind Mapping too!). A breakdown structure has nodes that represent some text attached to it that conveys some specific information. Nodes are connected with branches in a parent-child tree structure that follows parent = sum of all children rule.
Few other general design principles applies to breakdown structures like 1) 100% Rule 2) Mutual exclusive elements 3) Level of detail. Here are few commonly used breakdown structures and their explanations.
Work Breakdown Structure (WBS) – The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Resource Breakdown Structure (RBS) – The resource breakdown structure is a hierarchical representation of resources by category and type.
Organizational Breakdown Structure (OBS) – A hierarchical representation of the project organization that illustrates the relationship between project activities and the organizational units that will perform those activities.
Risk Breakdown Structure (RBS) – A hierarchical representation of risks according to their risk categories.