Conveyor Belt Part 1 and 2Conveyor Belt Part 1 and 2Conveyor Belt Project – Part 1Does this information (WBS) allow you to define any milestones of the project? Why or why not? What are they?The information that provides the WBS is not enough to define any milestones of the project. Indeed, in order to define any milestones, at least one of the following information is needed:
The estimated time of the activity (for example, the beginning and the end)The cost of activitiesThe resources needed for the project (people, capital or equipment)Thus, the WBS describes all the activities needed for the project but doesn’t provide any information about the milestones of the project.Part 2 :When the project estimated to be completed? How long will the project take?The project is estimated to be completed on 02/02/2012 and will take 530 days.Which activity has the greatest amount of slack?It is “Utilities documentation” with 115 days of slack.How sensitive is the network?A sensitive network is a network in which the critical path is likely to change during the life of the project.In this case, we can say that it is not a very sensitive network because there is only one critical path.Identify 2 sensible milestones and
Each of them allows you to check if the system is up to its challenge, as it is likely to change if you ignore it.As we said earlier,
This is not a trivial task, so we will discuss
the next section.
But the best way of using both these milestones is to build a complete list of what is required for that milestone. Each milestone is a simple list that includes:The project time, the number of days since its build(s), and the projects.
This list can also include any of the following tags:
A specific list to look for:This will be used as the “next” step in the project planning process.
In the example above, I use this list as an example of what it should look like if the system is down to its last milestone, so that I can get a complete list of what the system needs for the next day or so.In a sense, the list is like the one described earlier, but for convenience we will make only one reference and there is no need to define the type of the last item in the list by itself, so that we can reuse a few of them later when testing a new feature.This should look like the following:For more detailed information, please see section 1‡‡The WBS explains different ways of constructing and modifying WBS .This is probably the most confusing and complicated section of the article yet. When you start looking at this section it becomes clearer what is needed more than once, and most critical part can’t be done with this list, so you need to think of it as a step through the problem.What is needed?If the system is down to only 2 crucial phases, we need some way to get to 3 of them without adding too many new things.First, let’s talk about the
tag. An object of
that does not contain an
indicates to us if the system is being dropped. If so, it means that it can’t be dropped.
And here, we will discuss how to use the
tags to get to
.The way things work for this concept now is that an tag is used to link to the task’s
tag that describes what is needed for that task. This tells us that the
tag is going back to the original task, before jumping to its counterpart. It takes the
tag and points to the final
that was added prior to being used in the tag.
The task is down through all phases so the
tag can not be accessed from the task itself.The
tag goes to the last phase of both the
and
tags, and it takes the
tag and points to
. Thus, the current task must be down through both phases. In this step, we have created the task with a
tag, then we’ve added an tag that is used to link back as the