Method123

Schedule Estimating Threshold When you create a schedule you generally don’t know enough to enter all of the detailed activities the first time though. Instead, you identify large chunks of work first, and then break the larger chunks into smaller pieces. These smaller pieces are, in turn, broken down into still smaller and more discrete activities. This technique is referred to as creating a Work Breakdown Structure (WBS). A question people ask is how small the activities should be before they do not need to be broken down further. This is referred to as your “estimating threshold”. Work can be broken down into smaller activities than the estimating threshold, but normally no work would be left at a higher level. The threshold can be different based on the size of your project and how well the work is understood. You can use the following criteria as a guide. For a typical large project (say 5000 effort hours or more) the activities should be no longer than two weeks. Medium and smal

Assumptions and Risks - Two Sides of a Coin Let's take an example of a common statement that is included in many Project Definitions - that the resources needed for this project will be available when needed. What kind of a statement is this? Most people would say it is an assumption. After all, when a project starts, you always assume you will get the resources you need. However, is it really an assumption? Can you imagine starting a project where the people and equipment were not available and there was a realistic possibility that they would not be ready when you need them - perhaps because another project needed to finish first? It is not too difficult to imagine that scenario. In that case, the same statement would definitely be a risk - not an assumption. The same statement might be an assumption or a risk depending on the circumstances of your particular project. There is some degree of uncertainty to an assumption. If the event is negative and there is a low probability tha

Manage the Schedule for Small Projects All projects need a schedule. If you have a small project perhaps the schedule is a simple checklist or Excel spreadsheet. As projects get larger they need more formal scheduling templates and tools . The processes you use to manage a schedule also vary depending on the size of the project. Large projects need a lot of schedule management rigor. Small projects can use a lighter process. The following steps can be used to mage the schedule of a small project. Review the schedule on a weekly basis. Identify activities that have been completed during the previous week and update the schedule to show they are finished. Determine whether there are activities that should be completed, but are not. Work with the individual that is assigned to the work see what is going on. Determine how much additional effort and duration are needed to complete the work and update the schedule accordingly. Evaluate the remaining work to see if the project wil

Define the Objectives of Your Project Objectives are concrete statements that describe the things the project is trying to achieve. They are included in your Project Charter . An objective should be written in a way that it can be evaluated at the conclusion of a project to see whether it was achieved. A well-worded objective will be Specific, Measurable, Attainable / Achievable, Realistic and Time-bound (SMART). (SMART is a technique for wording the objective. An objective does not absolutely have to be SMART to be valid.) An example of an objective statement might be to " upgrade the customer service telephone system by December 31 to achieve average client wait times of no more than two minutes ". Note that the objective is specific. The objective is measurable in terms of the average client wait times the new phone system is trying to achieve. You can assume that the objective is achievable and realistic. The objective is time-bound , and should be completed