Buffer sizing methods COLLAPSE Top of Form Project buffers are used to provide cushion for the project and the individual task that make up the project. The buffers provide extra time, so the project can remain on schedule even with minor delays. CCPM uses four different methods for working with buffers. The four methods are 50% of the difference, square off the sum of the squares, bias plus SSQ, Monte Carlo analysis (Leach, 2014). Each method has strengths and weaknesses, but when used properly they can be beneficial to a project. The first method or 50% of the difference estimates buffers by calculating the difference between low-risk and the average task and dividing that in half. This is a simple method, but sometimes causes buffers to be too large. The second method or square of the sum of the squares also uses the difference between low-risk and the mean, but it uses the square root of the difference squared. This method takes into account unexpected variation, but can create undersized buffer. The third method or bias plus SSQ combine the first two methods. The fourth and final method or Monte Carlo analysis is the most complicated, but encompasses many of the other advantages of the previous method (Leach, 2014). Each method has its advantages, but I would suggest using method 3, bias plus SSQ. This method provides a simple platform that offers a high level of control over accuracy. Reference Leach, L.P. (2014). Critical chain project management. (3rd Ed.). Boston: Artech House Bottom of Form 2-Bottom of Form Less is more... COLLAPSE Top of Form Class, The “less is more” more approach is interesting to me because I have grown up in a military culture where if it is not on paper then it won’t happen or it didn’t happen. Leach did discuss where some project managers are very proud of having very high number of tasks associated with the project because they have “thought of everything”. However, as a project manager you are not as worried with the individual tasks that it takes to complete the work packages and the overarching project as you are with big muscle movements and milestones being accomplished on time and budget. Additionally, as a project manager you have a vast amount of breadth, but typically very little depth in the various specialties that are required to accomplish the project. Therefore, it is not feasible nor necessary for a project plan to identify every single task that will be accomplished. The project manager should allow is section managers/leads run their part of the project the way they see fit because they have a better handle on their resources and what needs to be accomplished. I would suggest that project managers focus on the big moving parts and go to the individual section leads to determine the time, budget, resources, and project flow and use that large scale information as the skeleton for their project plan. Also, when you plan out every single task, if something ...