Knowledge (XXG)

Product-based planning

Source 📝

147:
product set necessary for the project, and not just those that are in your scope, you can surface and document the critical assumptions. Another advantage compared to activity-based planning has to do with reporting. Products are either finished or not, activities can be 90% finished for a long time
78:
of the final end-product. Products included might also be products required to manage the project such as paper-based products and quality products such as approvals or quality checks on earlier made products. Examples include such things as requirement specifications, design approvals, test
38:, and is a method of identifying all of the products (project deliverables) that make up or contribute to delivering the objectives of the project, and the associated work required to deliver them. The documents which define the Project itself are also considered Products. 69:
It is important to understand that in this context the term 'product' includes intermediate documentary products that are essential to the work of delivering the project. In this sense the product breakdown structure is a great deal
131:
A significant advantage of product-based planning is the ability to surface critical assumptions and constraints. For example, if your project is to build another floor on top of a house, a required
103:) which identifies the order of precedence of products and will typically include multiple and complex parallel paths. For practical purposes this flowchart is essentially the same as the 148:
even though work is taking place. One tends to forget things that have to be done to complete a project. This method captures them all, reducing the chance that any will be overlooked.
127:
With an understanding of the deliverables required, and the sequence in which they should be produced, work can then begin on defining the tasks required to produce them.
217: 58:
Product-based planning is intended to ensure that all of the necessary products are identified and captured, and begins by identifying a
166:
Each of the sub-products are made up of smaller products such as door handle, insulation, magnetic closure strip and internal covering.
175: 139:
you hope that it is there and will be fit for purpose but as you are not commissioned to deliver it, it falls outside your
163:
is a final product with sub-products being door, shelves, heat exchange unit, fans, ice cube dispensers, lights, etc.
59: 52: 140: 185: 121: 151:
This method is used in PRINCE2, the UK's government mandated method for the management of major projects
62:
which is then repeatedly refined until all of the requisite products are identified. The PBS is thus a
108: 96: 89: 35: 135:
will be the floor underneath on which to build the one you are commissioned to deliver. As a
222: 202: 95:
Once a product breakdown structure has been created, work can then begin on creating a
17: 211: 75: 66:
family tree of all the products and sub-products that comprise the final end-product.
160: 63: 180: 31: 104: 111:
and leads naturally to the development of a project schedule.
143:- and into your assumptions. In this way, by defining the 79:documentation, safety certifications, and so on. 8: 203:Product-Based Planning in PRINCE2 wiki 7: 25: 176:List of project management topics 1: 218:Schedule (project management) 30:is a fundamental part of the 60:product breakdown structure 53:Product breakdown structure 47:Product breakdown structure 239: 119: 87: 50: 186:Managing stage boundaries 122:Work breakdown structure 116:Work breakdown structure 109:critical path scheduling 28:Product-based planning 18:Product based planning 97:product flow diagram 90:Product flow diagram 84:Product flow diagram 36:project management 101:product flowchart 16:(Redirected from 230: 21: 238: 237: 233: 232: 231: 229: 228: 227: 208: 207: 199: 194: 172: 157: 124: 107:chart used for 92: 74:than simply an 55: 44: 23: 22: 15: 12: 11: 5: 236: 234: 226: 225: 220: 210: 209: 206: 205: 198: 197:External links 195: 193: 190: 189: 188: 183: 178: 171: 168: 156: 153: 129: 128: 120:Main article: 118: 117: 113: 112: 88:Main article: 86: 85: 81: 80: 67: 51:Main article: 49: 48: 43: 40: 24: 14: 13: 10: 9: 6: 4: 3: 2: 235: 224: 221: 219: 216: 215: 213: 204: 201: 200: 196: 191: 187: 184: 182: 179: 177: 174: 173: 169: 167: 164: 162: 154: 152: 149: 146: 142: 138: 134: 126: 125: 123: 115: 114: 110: 106: 102: 98: 94: 93: 91: 83: 82: 77: 76:exploded view 73: 68: 65: 61: 57: 56: 54: 46: 45: 41: 39: 37: 33: 29: 19: 165: 161:refrigerator 158: 150: 144: 136: 132: 130: 100: 71: 64:hierarchical 34:approach to 27: 26: 212:Categories 192:References 99:(PFD) (or 170:See also 42:Overview 223:PRINCE2 181:PRINCE2 155:Example 137:product 133:product 32:PRINCE2 145:whole 141:scope 105:PERT 72:more 214:: 159:A 20:)

Index

Product based planning
PRINCE2
project management
Product breakdown structure
product breakdown structure
hierarchical
exploded view
Product flow diagram
product flow diagram
PERT
critical path scheduling
Work breakdown structure
scope
refrigerator
List of project management topics
PRINCE2
Managing stage boundaries
Product-Based Planning in PRINCE2 wiki
Categories
Schedule (project management)
PRINCE2

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.