FOR INFORMATION: 1. Please explain, in details, the decomposition technique used in the creation of the WBS.

Please also provide a simple example to further clarify this technique. The decomposition technique in the WBS merely refers to work decomposition. It is about taking the high level deliverables and decomposing them into increasingly manageable tasks, until you reach the work package level, which is the most atomic element of the WBS. A work package is usually easily estimated, scheduled, assigned, and executed (see an example of the work package here: ). Now how do you decompose each major deliverable until your reach the work package level, and when do you know how to stop? Here's how: 1- You take each and every deliverable. 2- You analyze the deliverable and see what are the major tasks that fall under this deliverable, and you decompose the deliverable into these major tasks (which will fall under the deliverable in the WBS) 4- You repeat #2 (I haven't seen a WBS with less than 3 levels) until you reach the work package level, but how do we know that you have reached the work package? This is easy, you either follow the 4% rule or the 40 hour rule (see the example of the work package above). As a rule of thumb (forget about the 4% rule and 40 hour rule), when you feel that the task can be estimated accurately and can be worked on by a single person for a relatively short period of time, then that task is a work package. Note that when you decompose the WBS, you may end up in an unbalanced tree, which means that not all the leaves (work packages) are at the same level, this is normal, and you don't have to worry about this and try to make the tree balanced. 2. I need someone to give me an example of a work package, preferably in an IT environment. Is a work package equivalent to a task in the project schedule? A work package is a set of related tasks, and is the most granular level in the WBS. Before giving you an example of a work package, I would like to list the two theories on how to decompose your WBS into Work Packages: - The 4% rule: Which means that the work package consists of 4% of the total size of the project. - The 40 hour rule: Which means that the work package should consist of no more (and not a lot less) than 40 hours. Here are some examples of work packages in a web development project:

The Task . I don't see any problem in showing to the client.Percentage complete of the task . I don't even have the slightest idea of what it means.Develop the ACL module 3.Status of the risk . What do you fellow project managers think? Unless there are some "trade secrets" and "know hows" in the WBS. The WPI consists of document (usually a spreadsheet) containing comprehensive information about what was already done in the project.Deliverable(s) associated with this task. A project network is a graphic flow chart of a project job plan that is developed from the work breakdown structure (WBS). 6. 5.Create the frontend interface ..3.Description of the risk . Quick question.The start date of the task .The (expected) end date of the task .Status of the task . Again. My personal concern with this is when you involve the client at a such a low level.Id of the risk . what is the difference between the WBS and the project network. It is mainly useful to identify the critical path and understand how best to sequence the activities. I have an idea of what it is used for. which may drive the project manager insane. Work Performance Information (or WPI) is a PMBOK term. Frankly I feel that the WBS is a very technical document that should be only available to those working on the project. he becomes picky and he starts trying to act smart ("hey what happened to task 1. A project network is developed to identify and document dependencies among schedule activities that have been identified in the WBS. please explain in simple language what work performance information means for us. 4. but I have no idea what it is (which is quite odd for me). All the definitions I have found for this term were way too complicated.Name of the risk . aren't they more or less the same? WBS refers to a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. I'm trying to make a list of all the project documents that we need to share with the customer. I'm currently thinking if the WBS is one of those documents that the customer needs to see. the not-very-intelligent-project-managers. their names and their status .The risks associated with the task (this will create the following mini-sheet inside the original spreadsheet) . Here are the typical columns that should be included in a WPI document: . Please explain the PMP term "Work Performance Information".5 in the WBS").

the price. here's how: .. 8. but I prefer the first way as everything (risks/change requests/deliverables/etc.The change requests associated with the task (again. etc.The purpose of the document: A small paragraph explaining what is the purpose of the project brief. 7.Resources allocated to this task (this will also open up a mini sheet listing all the resources allocated to this task as well as their roles) .. How do you write a project brief? What should be included in it? Can you provide with a template or simple guidelines on how to write it? The project brief is a project management document that will both the stakeholders and the team managers a (somehow) detailed idea about the project.Description of the change request .) is associated with a task. The scope of work briefly defines all the work that should be included in the project. their (expected) end date. what was the material purchased. and their current status .Name of the change request . who is the seller.. The project brief should contain the following sections: . Does every project needs a statement of work? Also what is the difference between the statement of work and the scope of work? Yes every project needs a SOW.All the procurement activities associated with this task (this will open up another mini sheet listing detailing each and every procurement activity.. execution can start once the project brief is approved by the project board. In construction projects.Id of the change request .. Please give me an example of a project SOW (Statement of Work). who should use it and how.Background information: Why is this project undertaken? How was it selected? What are the . the scope of work is part of the statement of work.Action done to mitigate the risk . Note that the second way of doing the WPI is the most common..Quality issues pertinent to this task (mainly quality compliance) .Some technical details about the task .Total costs associated with this task (a detailed breakdown should be included) .etc.You then list the risks (and all pertinent information) ..You then list the deliverables (the deliverables here are not associated with tasks) .Change Requests ... . we will have another mini-sheet) .You first list the started tasks.) Note that the WPI can also be done in a completely different manner. their start date..Status of the change request .

projectmanagementquestions. as well as the roles of every person on this project. . the description of the work for that work package. what are the .000 Actual Cost: $1. "the project has to be finished by June of 2012".Changing the main menu from horizontal to vertical .Connecting to a web service to retrieve the current weather based on the visitor’s city . E-mail about project closure to customer? Here's a standard email that can be used to be sent to your client once the project is done: "Dear [Client Name]. such as (here are some examples from a web development project): .Constraints: List any constraints you have on this project. Note that it is better to provide a graph representing the project structure (easier to read). .Exclusions: What should be excluded from the project. when it will .Project Definition: The project definition is split in 2 parts: .com/1013/what-isproject-management-structure-in-project-management .Integrating the product with social networks . this is because some features that are usually present in the product may be omitted in this project.Risks: List the known risks for the project. .Project preliminary scope: A listing of the main deliverables in the project. See an example here: http://www.benefits of undertaking this project? .000.Project objectives: See an examples of project objectives here: http://www. Start Date: 01/01/2010 Planned End Date: 05/01/2011 Actual End Date: 06/01/2011 Planned Budget: $1. Here's some information about [Project XYZ].Project Structure: How will the hierarchy look in this project? This is important because in any project we need to know who reports to whom. even though we have processed a lot of changes. for the project nearly met the planned end date and the planned budget. We are happy to tell you that [Project XYZ] is now finished.000 As you can see.pdf 9. and what are the deliverables for these work packages. The project brief is distributed to the project stakeholders (including the project sponsor and the project board). In your document. Here's a great example I have found to be very useful about the project brief: http://www. you have to show to have an Appendix. when will it end. and to the team managers. showing each work package.

Can someone provide me with a standard checklist to be used when closing projects (particularly software projects. and ideally. and an honest assessment about the project (was it a success. sign it. . Make yourself and your team members happy. At this point you should ensure that all the lessons learned were captured.Was the contract formally closed from the buyer-seller perspective? Once the customer is satisfied. was it a failure). 10.Were team members appraised? It is important to thank your team members (in one way or the other) for the work they did on the project. Thank you for your business and we look forward to serving you again. and easy. All the stakeholders also must be informed that the project is now officially closed.Did you celebrate success? You have finished a project.Did you create the final report? The final report is a document that is created at the very end of the project. celebrate your and their success! Some project celebration ideas . Please fill it in. . that will include all the things that went wrong and right. Here's a project closure checklist. . . . You can read more about the final project report here: http://www. such as sharing these documents with other projects).Attached please find the project acceptance document (or project signoff document). [Your Name]. . to be used in any project: . and must take corrective actions (such as re-work) if the customer was not satisfied. after all. the project manager should write this email. The lessons learned report must be sent to the PMO (that will later use it in its knowledge management activities. Project Manager" (this is the end of the email) . . but if the checklist is generic it's also OK)? I think if I follow a standard checklist when I close my projects I will cease to overlook some necessary activities during this phase.Did you capture the lessons learned? Capturing lessons learned is probably the most overlooked activity in project management. the project sponsor should take check it before it is sent. yet it is so important.projectmanagementquestions. then the contract should be formally closed and the customer must sign on the acceptance document.Was the project marked as done? The PMO and the Program Manager must both mark the project as done. the team members must be released and marked available so that they can be allocated on other projects. the project wouldn't have finished without them. The project manager should cc the project sponsor and the main stakeholders on the project. it was successful.Were team members released? Once the contract is closed.Was the customer satisfied? The project manager must ensure that the customer was satisfied with the project as a whole. and send it to use when you get the chance (either by email or by post).Did the customer verify the deliverables? The customer must verify that each and every deliverable in the project plan is done according to his requirements.

. is the element outsourced? If yes.Work: What is the work that this element consists of? .) An example of a WBS dictionary is the following (example is taken from the WBS of a web project): (header) Code | Name | Description | Work | Duration | Cost | Cost Details | More Information (sample row) 1. 18.Duration: What is the duration of that element? .can be found here: http://www. 13. The WBS dictionary contains the following information: . 17. 15. What is the Work Breakdown Structure dictionary? What does it exist (what are its needs?) Can you also give me an example of a WBS dictionary. 14. as examples usually make the concept simpler to understand? A WBS dictionary consists of a database (sometimes an Excel sheet) containing more information about every element in the WBS. .com/693/give-some-ideascelebrate-delivery-major-software-project 11. The name of every element . but then we decided to do it in the company..Cost: How much each element costs . 19.600 | 40 hours of Jane's time @ $40/hour | We were going to contract out this task. then to what company? Etc.1 | Ajax Interface | Development of the AJAX interface | 1) Develop the forms using AJAX 2) Develop the summit of the form using AJAX | 40 hours | $1. as developers will enhance their experience 12.More information: More information about this element (example.2. 16.Code: The code of every element in the WBS .projectmanagementquestions.Cost details: How did we get the cost of that element ..Name.Description: A full description on every element.

Sign up to vote on this title
UsefulNot useful