November 5, 2020, 8:30 a.m. to 6 p.m. EDT | November 6, 2020 – February 7, 2021, On-Demand | Online Conference
Please login or join to subscribe to this thread
This is a very long process and can't be explained in few lines. However, to start with, you need to:
1- Gather your Milestones.
2- Do a work breakdown structure.
3- Put activities duration.
Is it necessary to start from scratch? did you check the templates? maybe you'll find something interesting.
Anyway, Rami posted already the key points to take in mind.
I agree with Rami that we cannot explain the entirety of creating a project schedule in the limited space we have here. The following is the general sequence of events that I use for most of my projects directly related to schedule creation:
- Divide large projects into phases or sub-projects
- Determine high level requirements and milestones
- Determine measurable project and product scope and objectives
- Complete a ROM estimation of schedule and budget (Rough estimate)
- Determine success criteria (scope, budget, schedule)
(Assumes Project Charter is issued and Project Management Plan is already started)
- Refine high level requirements into more defined terms
- List all known constraints (resources, schedule, cost, etc.)
- Begin description of all deliverables and work required to complete them (also known
as the scope statement).
- With project planning team, develop WBS and WBS dictionary to break down the
project into smaller, more manageable pieces (called work packages). The dictionary
allows you to define the scope of each work package.
- Break down the work packages from the WBS into lists of activities and build a
- Sequence all activities and determine dependencies.
- Estimate all resource requirements and gain preliminary resource commitments.
- Estimate time and cost with the team members actually carrying out the respective
- Determine how long project will take without any schedule compression.
- Develop a preliminary schedule model and reconcile with earlier schedule from
initiation phase and Project Charter. This will verify a final schedule model for the
Project Management Plan.
Review and refine this schedule following Risk Management and Quality Planning as both
usually have an impact on both cost and schedule. When you have your final Management Plan approved by sponsors, team, and resource managers, you will baseline
the schedule and budget.
I hope this helps. Its about as much detail as I can provide in the limited space/time I have. There are many tasks that go into all of those steps and the steps that I have listed are only the steps directly involved in creating the schedule. PMI and Project Management.com both have a lot in the way of knowledge resources that can help fill in some of the blanks.
I will assum that you are talking about a project schedule. The first thing to do is to understand what a project schedule really is. A project schedule is "an output of a schedule model that presents linked activities with planned dates, durations, milestones and resources". So, great part of your question is answered into the defintion. Chapter 6 into the PMBOK will give you a good guide of steps to follow. In our case we follow the steps into that chapter. The schedule we create is started after define the WBS until work package level (for us those will be our summary tasks). We take the WBS`s work package and started to decompose them into an activity list (6.2. Define Activities) and continue as the PMBOK stated from 6.2 to 6.6
The schedule goes hand-in-hand with the project estimate and is correlated with other project documents, such as project charter, project plan and project management plan. Get your hands on the estimates, and together with schedule basics and appropriate judgment for execution of the project scope, a schedule can be created to begin the iterative review process for schedule development.
The estimate should include activities, manhours and crew size that are extended with labor rates, materials and equipment to identify cost. The estimate also should include scope/assumptions for scope, project goal dates, labor agreements, crew size, jurisdiction of work/work packages, interfaces between work packages, work days, holidays, other days work is restricted, work hours, work periods per day, and anticipated productive hours at the work location.
4. Sequence the activities based on dependencies/deliverable
5. Optimize schedule for proper resource assignment, contingency, critical path analysis etc
Before creating a project schedule, understanding some project planning basic will help you map out what it ends up looking like.
You will need to translate, the why, the what, the who, the where, the how, and the how much into the when.
Simply put you need to understand:-
- The business justification for the project
- The project scope
- The resources you need to perform the work
- The geographic locations they will work in
- The project delivery method
- The budget
It’s also worth mentioning that scheduling a project is not a one-off activity. Creating it is just the start, making sure you can easily maintain and update it is another challenge.
You're post is about how to create a schedule, but likely you'll be using some type of tool. If you're using Microsoft Project, do yourself a huge favor and go into the Project Options and set up a few key items such as: when the week starts, how many hours are in a day, new tasks created auto scheduled, start new tasks on start date or status date, default task type and many others. In addition, go into the Project, Change Working Time to set up your calendar to have specific holidays as non-working days etc. Finally, the internet is your friend, start doing your research on schedule attributes and look up "how to create a project schedule." Good luck!
Please login or join to reply