Scribd
Upload
9 views18 pages

Planning I_110817

The document outlines the essential components of project planning, emphasizing the importance of a Project Plan Document that includes work breakdown structure (WBS), scheduling, budgeting, and resource allocation. It details the steps to create a WBS, which helps in task identification, cost estimation, and progress measurement. Additionally, it highlights the need for a structured approach to building schedules and managing project execution effectively.

Uploaded by

abomohammed9499
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views18 pages

Planning I_110817

The document outlines the essential components of project planning, emphasizing the importance of a Project Plan Document that includes work breakdown structure (WBS), scheduling, budgeting, and resource allocation. It details the steps to create a WBS, which helps in task identification, cost estimation, and progress measurement. Additionally, it highlights the need for a structured approach to building schedules and managing project execution effectively.

Uploaded by

abomohammed9499
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

Planning I

Project Planning (Plan document)


• Identify the work to be done, who is going to do it, how long everything will take, when things
will happen and how much it will cost.
• It also include how will you run the project, communicate, control change, and risk management.
(direct, track, correct, communicate)
• All this must be included in Project Plan Document
• Project Plan :
• Pointing the Team in the Right Direction
• Tracking Progress
• The plan will be your guide during project execution:
What work do we have to do? Work Breakdown Structure (WBS)
When will we start and when must we finish? Schedule
Who is going to do the work? organization and resources.
How much is it going to cost? or How much do we have to spend? budget.
• It must include :
• Task breakdown, cost, and resources
• Schedule
Project Planning (Plan document)
Define
• Plans Change (Still need a Plan) WBS
• Project Planning Step by Step
Estimate Sequence
Tasks Tasks

Build Assign
Budget Resources
Adjust
Schedule
The Components of a Project Implementation
Plan
Work breakdown structure (WBS)
• First process in project planning is to identify the work that has to be
done.
• A WBS shows the work in a project broken down into progressively
smaller tasks. The tasks at the lowest level represent work you can
assign to team members to perform.
• “How do you eat an elephant?” The answer is “One bite at a time.”
• WBS is a tool used to break the project work into pieces.
Work breakdown structure (WBS)
• Why DO we need WBS:
• Helps the project planners identify the work to be done and determine
the best way to decompose the work
• Helps stakeholders visualize the scope of the project
• Shows the work defined by the scope statement in more detail
• Helps people understand their work assignments
• Exposes additional work to be done
• Helps the planners develop more accurate estimates of a project
schedule and costs
• Provides a foundation for measuring progress
Work breakdown structure (WBS)
WBS
• Why WBS
• Easy cost estimation (smaller chunks of work)
• Easy time estimation (smaller chunks of work) Summary Work
• Easy to assign work to project members Tasks packages
• Project monitoring (progress measurement)
• WBS tasks
• Summary tasks (high level tasks) like : Project
• Software design
• House design
• ‫إعادة تأهيل القاعة‬ Task Task
• Work packages(lower level tasks describes work details) like:
• Design the use case diagram
• Conducting the workshop
Work Work
• ‫طالء القاعة‬
Work work
Work breakdown structure (WBS)
• How to build WBS?
• Top down approach
• Work as a Team to identify top level tasks
• Split the team among top level tasks to identify sub-tasks (according to
responsibilities)
• Gather the team to review and correct any issues
• Start with scope and deliverables to identify top level summary tasks
• Then break them down
WBS

For Larger projects use a team to


identify Summary Tasks
- Use Scope and deliverables
- Divide into groups for every task
Work breakdown structure (WBS)
• Steps To Build WBS:
1. Identify High-Level Tasks Using Project Deliverables and the Scope
Statement
2. Fill In the Remaining Levels of Tasks That Make Up the Work in the Top-
Level Tasks
3. Revise the Structure of the WBS
4. Verify the Structure of the WBS
Work breakdown structure (WBS)
• When To STOP!!!!!
• Progress and completion are measurable
• Task duration is a reasonable length
• Time and cost are easy to estimate
• The work package has a clearly defined start and finish
• Work packages can continue without input from another task
• The detail is at a level that you can manage
Work breakdown structure (WBS)
• How much breakdown is enough?
• Mach the status reports (measurable progress)
• Take work packages (tasks) between 8 to 80 hours
• Better to use the following test:
Define work packages
• Write enough details
• List of things to do
• Expected Deliverable to
measure
• If it is not unknown/new
consult
specialized people
• Create work package
document
Define work packages
Build WBS for
• Install a network infrastructure @ CCIT
• Implement school mgt system
• Start/Business Development for Internet Café
• Organize IT-Event@CCIT
Building a schedule
• WBS doesn’t tell you:
• (how long, when )
• To do Schedule tasks:
• Put Tasks into schedule
• Use Gaunt chart (familiar and simple)
Finish to start
• Order them in sequentially
• Identify dependencies
(Identify sequential and parallel
tasks)
• Estimate Time
• Identify People & responsibilities (Resources) Why to start with!!!
• Finally, take into account any constraints (like deadline)

You might also like