1. Develop Schedule
1.1. Input
1.1.1. Common: OPA, EEF, Proj Mgmt plan
1.1.2. Project docs
1.1.2.1. common: assumption log, lesson learn
1.1.2.2. Schedule doc
1.1.2.2.1. Duratioin estimate
1.1.2.2.2. Activity list
1.1.2.2.3. Activity attributes
1.1.2.3. Resource doc
1.1.2.3.1. Project team assignment
1.1.2.3.2. Resource requirement
1.1.2.3.3. Resource breakdown structure
1.1.2.4. Risk register
1.1.3. Agreements
1.2. Output
1.3. Tools&Tech
1.3.1. Critical path
1.3.1.1. a **delay in any** one of critical path acitivities will cause the **entire project to be delayed**
1.3.2. the Float of activity
1.3.2.1. can be called as *slack *
1.3.2.2. amount of time -> It **can slip** **before** it cause project to **be delayed**
1.3.2.3. float tell you how much extra time you have
1.3.2.4. some activites **aren't in** critical path but have a **float of zero** => really have to **pay attention** & watch out for **potential** resource problem
1.3.3. Early Start (ES)
1.3.3.1. earliest time -> activity can start
1.3.3.2. acitivity near end of the path -> only start early if all of previous activities aslo started early
1.3.4. Early Finish (EF)
1.3.4.1. earliest time -> activity can finish
1.3.4.2. time that activity will finish, if all of previous activities started early and none of them slipped
1.3.5. Late Start (LS)
1.3.6. Late finish (LF)
2. Step By Step
2.1. 1.Plan Schedule Management
2.1.1. Define process to plan & control schedule
2.2. 2.Define Acitivities
2.2.1. List of activities need to be completed
2.3. 3.Sequence Activities
2.3.1. set the order for each activities
2.3.2. build a Project Schedule Network Diagram
2.4. 4.Estimate Acitivity Durations
2.4.1. estitmate time to do each activity
2.5. 5.Develope Schedule
2.5.1. build schedule from .. => predict the Project End date
2.5.1.1. estimates
2.5.1.2. resources
2.5.1.3. activity infomation
2.6. 6.Control Schedule
2.6.1. monitor & control => make sure it is kept up to date
3. **Plan Schedule**
3.1. Input
3.1.1. Common : OPA, EEF, Project Management Plan
3.1.2. Project Charter
3.2. Tools&Tech
3.2.1. Expert Judgment
3.2.2. Data Analisys
3.2.3. Meeting
3.3. Output
3.3.1. Schedule Management Plan
3.3.1.1. Schedule Model
3.3.1.1.1. Initial with high lvl estimate
3.3.1.1.2. estimate 'll be refined at set interval as requirements are defined
3.3.1.1.3. will be baselined when
3.3.1.2. Level of Accuracy
3.3.1.2.1. initial schedule model is expected by +/-10%
3.3.1.2.2. each week passes -> updated by +/- 3% because team knows more about project
3.3.1.2.3. possible 15% overage for overall estimate as contingency reserved
3.3.1.3. Units of measure
3.3.1.3.1. calendar days
3.3.1.4. Organizational Procedure Links
3.3.1.4.1. follow the WBS
3.3.1.5. Schedule Model Maintenance
3.3.1.5.1. update % complete to keep schedule up to date
3.3.1.6. reporting format
4. **Define Activities** (figure out how project work breaks down into acitivities)
4.1. Input
4.1.1. OPA (lession learn)
4.1.2. Project Management plan ( method to use when define the activities in schedule + scope baseline )
4.1.3. EEF
4.2. Tool&Tech
4.2.1. Rolling wave planning
4.2.1.1. plan & schedule only stuff that you know enough to plan well
4.2.1.2. all about committing to planning out one portion of work -> do & execute, then moving to the next portion
4.2.1.3. Agile methodologies use form of , => using User stories for release up front, build & deliver, then gather more requirement based on user's ideas after working with released version
4.3. Output
4.3.1. **Acitivity list** ( basis for all the estimation & scheduling tasks)
4.3.1.1. need to be done to complete project
4.3.1.2. lower level than WBS
4.3.1.3. all activities must be accomplished to deliver the work package
4.3.2. Activity Attributes ()
4.3.2.1. description of each activity
4.3.2.2. infomation to figure out the order of the work
4.3.2.3. include any predecessor activities, successor activities, constraints
4.3.2.4. information about resource / time
4.3.3. Milestone list
4.3.3.1. all important checkpoint are tracked as milestone
4.3.3.2. list in contract as requirement of successful completion
4.3.3.3. significant point in project you want to keep track of
4.3.4. Change requests
4.3.5. Proj Management Plan
5. **Sequence Activities** (put everything in order)
5.1. Input
5.1.1. common : proj doc, OPA, EEF, schedule plan & scope baseline
5.2. Tools&Tech
5.2.1. **Network diagram**
5.2.1.1. figure out what's important at any time in the project
5.2.2. Dependency determination and intergration
5.2.2.1. Finish to Start (FS)
5.2.2.2. Start to Start (SS)
5.2.2.3. Finish to Finish (FF)
5.2.2.4. External Dependencies (depend on things outside the work you're doing)
5.2.2.5. Discretionary Dependencies
5.2.2.6. Mandatory Dependencies (have to exist just because of work)
5.2.2.7. Internal Dependencies
5.2.3. Leeds & Lags
5.2.3.1. Lag (purposefully put a delay between the predecessor & the successor)
5.2.3.1.1. ex: bride & her father dance, the guests wait awhile before they join them
5.2.3.1.2. ex: book the reception hall -> setup the reception hall ==> have to wait previous wedding in the reception hall for awhile before setuping
5.2.3.2. Leed (give the successor some time -> get started before the predecessor finish)
5.2.3.2.1. ex: Serve dinner -> Prepare dessert ==> let start prepare soon before cooking finish)
5.3. Output
5.3.1. Project Schedule network diagram
5.3.2. project documents updates
5.3.2.1. Activity attributes update
5.3.2.1.1. while sequencing activity -> find out new predecessor/successor => their attributes need to be changed
5.3.2.2. Assumption log
5.3.2.2.1. find out assumption incorrect -> update while making decision about the order activities
5.3.2.3. Activity list updates
5.3.2.4. Milestone list
6. **Estimate Activity Durations** (start with info about activity & resource assigned to it => estimate)
6.1. Start with a **rough estimate,** the **refine** it to make it **more accurate**
6.2. Input
6.2.1. common: OPA, EEF, Plan
6.2.2. Project Docs
6.2.2.1. common
6.2.2.1.1. lesson learn
6.2.2.1.2. Assumption log
6.2.2.2. Schedule doc
6.2.2.2.1. Milestone list
6.2.2.2.2. Activity list
6.2.2.2.3. Activity attributes
6.2.2.3. Resource doc
6.2.2.3.1. Resource calendar
6.2.2.3.2. Project team assignment
6.2.2.3.3. Activity resource requirement
6.2.2.3.4. Resource requirement
6.2.2.3.5. Resource breakdown structure
6.2.2.4. Risk register
6.3. Tools&Tech
6.3.1. Expert judgment
6.3.1.1. huge risk (wrong estimate) if dont get their opinion
6.3.2. Parametric Estimating
6.3.2.1. input data into formula or software (built on a DB of actual past project) => get estimate
6.3.3. Bottom-up estimating
6.3.3.1. build up from estiamte of each individual people who will do work
6.3.4. Data analisys
6.3.4.1. Reserve Analisys
6.3.4.1.1. add extra time to the schedule (called as *Contingency reserve* or *buffer*) to account the risk
6.3.4.2. Alternatives analysis
6.3.4.2.1. all of possible options to fine the most efficient path for delivery
6.3.5. Analogous Estimating
6.3.5.1. look at similar activity on past project then copy the estimate
6.3.6. 3-points Estiamte - get average of
6.3.6.1. **most likely** estimate will happen
6.3.6.2. **optimistic** - best case scenario
6.3.6.3. **pessimistic** - worst-case scenario
6.3.7. Decision making
6.3.7.1. **team decide** the best estimate for activities
6.3.8. meeting
6.3.8.1. team work together to estimate
6.4. Output
6.4.1. Duration Estimate
6.4.1.1. in hours, days, weeks, ... with not exactly how long you can use range like 3 weeks +/-2days
6.4.1.2. **different** with Effort Estimate
6.4.1.2.1. duration = amount of time that an activity takes
6.4.1.2.2. effort = total number of person-hours expended
6.4.1.2.3. ex: build a function with duration = 8h -> work on it with 2 dev the whole time : effort = 8x2=16h
6.4.2. Basis of Estimates
6.4.2.1. describe the approach, assumption, considered factors
6.4.3. Project document updates