1 / 15

COMP2001 HNC Project

COMP2001 HNC Project. Project Characteristics. A project must have: clear objectives planning & control resources assurance of quality. Project Definition. A project is defined in terms of its: - background - objectives - scope - constraints. Project Schedule.

timothy-booth
Download Presentation

COMP2001 HNC Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COMP2001 HNC Project

  2. Project Characteristics • A project must have: • clear objectives • planning & control • resources • assurance of quality

  3. Project Definition A project is defined in terms of its: - background - objectives - scope - constraints

  4. Project Schedule • Determine project approach (buy or build) • Estimate effort • Prepare project plan • Prepare project budget • Document project progress

  5. Project Schedule • Time ordered sequence of deliverables • Used for: • organising work effort • working towards project goals & obj. • tracking the project

  6. Tasks • Smallest unit of work • Each task only occurs once • Suitably described • Enough details to be measurable

  7. Milestones • Point in schedule to measure progress • Contains a sequence of tasks

  8. Project Management Techniques • Traditional project management techniques widely used in many other industries. • These include:- • Work Breakdown Structure (WBS). • Gantt chart. • PERT chart (critical path or network diagram).

  9. Work Breakdown Structure • Very useful for initial planning. • Helps identify required resources. • Structured list of all tasks and activities that must be carried out to complete project. • Usually, sequence is unimportant. • Main purpose is checklist for completeness.

  10. WBS example: “clean bedroom” hoovering • get hoover • move furniture • hoover floor dusting • get duster • move ornaments • do dusting change bed, etc.

  11. Gantt Chart • The classic “bar-chart”. • Often based on WBS, but includes time dimension. move furniture get hoover hoover floor put furniture back put hoover away time

  12. PERT Chart or Critical Path Chart • “Programme Evaluation and Review Technique”. • Designed to show interdependencies between tasks: • “get hoover” must be complete before “do hoovering” starts (i.e. B depends on A); • “move furniture” can happen before or after “get hoover” (no dependency). • Often derived directly from Gantt Chart.

  13. 2 3 3 0 1 2 0 0 3 3 0 0 Network Diagram Event No. Event Earliest Time Event Latest Time AGet Hoover TM(2) Slack/Float CHooverTM Floor(14) 3 17 17 0 BMove Furniture(3) Activity Event

  14. Resource Levelling • First-cut chart is not always the most efficient. • It may be possible to: • reduce overall resources required, • reduce total project time. • “Levelling” means: • use available float time on non-critical tasks, • move spare resources from one task to another. • A matter of judgement - no one best way.

  15. Suggested Reading Project Management for Information Systems D Yeates & J Cadle

More Related