1 / 28

Project Plan

Project Plan. “What are you going to do in the project?”. Lecture Objectives. To discuss the tasks in planning a project To describe the tools that can be used for developing a project plan To illustrate the use of graphical representations of project activities

johana
Download Presentation

Project Plan

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. Project Plan “What are you going to do in the project?” TCS2411 Software Engineering

  2. Lecture Objectives • To discuss the tasks in planning a project • To describe the tools that can be used for developing a project plan • To illustrate the use of graphical representations of project activities • To understand the importance of the critical path in scheduling TCS2411 Software Engineering

  3. Planning Meaning: “Organizing project in logical order and Identifying and defining work activities in a manner that help achieve project objectives” TCS2411 Software Engineering

  4. Basic Reasons for Planning • To element/reduce uncertainty • To improve efficiency of the operation • To provide better understanding • To provide a basis for monitoring and controlling work TCS2411 Software Engineering

  5. Project Planning and Control System Goals/ Objectives Work Description and Instructions Network Scheduling Master/ Detailed Schedules Management Decision- Making System Reports Time/Cost/ Performance Tracking Budgets TCS2411 Software Engineering

  6. Planning Steps • Establish objectives • Develop a plan • Construct project planning diagram • Identify timing duration of each activity in planning diagram • Identify costs and labor/personnel associated with each activity TCS2411 Software Engineering

  7. Establish Objectives • State objectives • Project start/end dates • Budgets • Technical results • List milestones • Milestone: a scheduled event for which some person is held accountable and which is used to measure and control progress. • Designate responsible personnel to meet objectives TCS2411 Software Engineering

  8. Develop A Plan • List activities • Develop Work Breakdown Structure (WBS): The WBS reflects the decomposition of a project into subtasks down to the level for effective planning and control. • Determine relationships of activities • job precedence/succession • concurrent jobs TCS2411 Software Engineering

  9. Work Breakdown Structure • Break project tasks into successively finer levels: Program - Project - Task - Work Package - Work Unit • Each work unit • short time span • specific start & end point • budgetable in terms of money, resources • can be assigned an individual responsibility • can be scheduled TCS2411 Software Engineering

  10. Purpose of WBS • Manageable • Independent • Integratable • Measurable TCS2411 Software Engineering

  11. WBS Example Level 1 ABC Project Level 2 Definition Analysis Design Programming ... Level 3 Requirements Documentation Feasibility Study Risk Analysis ... TCS2411 Software Engineering

  12. Project Test Code Design Test plan Code B Code A WBS of a simple project • Each activity has a duration and consumes resources. • Each activity has a constraint(example: one must be finished before the other starts; so activities are executed in order). TCS2411 Software Engineering

  13. Test plan 10 Code A 18 Design 15 Test 15 Code B 18 Program Evaluation and Review Technique (PERT) diagram • The numerical number represents the duration of each activity. • PERT is mainly concerned with time of each activity and interrelations among activities. TCS2411 Software Engineering

  14. Critical Path Method (CPM) • By drawing a network diagram, you can figure out the critical path of your project. • The critical path is the longest path through the network.If something falls behind schedule on the critical path, the whole project falls behind schedule unless time is made up elsewhere. • It’s easier to adjust other activities (allocate more/less resources) when you know the interdependencies of activities TCS2411 Software Engineering

  15. Construct Project Planning Diagram • Draw the logical sequence of activities • Precedence Diagramming Method (PDM) • Activity on Node (AON) • Arrow Diagramming Method (ADM) • Activity on Arrow (AOA) TCS2411 Software Engineering

  16. Terms • Activity - A task or job which takes time & use up resources Represented by labeled arrow A • Event - An instantaneous point representing the start or finish of an activity Represented by node • Slack time: indicates that the corresponding activity may consume more than its estimated time, or start later than the earliest possible start time, without affecting the total duration of the project. • Critical path: a path that has activities without any slack time 1 TCS2411 Software Engineering

  17. Activity-on-Arrow (AOA) Diagram G D 2 5 A E B 1 3 6 F C 4 Each activity has only one arrow associated with it. TCS2411 Software Engineering

  18. Activity Precedence TCS2411 Software Engineering

  19. Network Characteristics • Construct from left to right • Any activity can have only one start node • No two activities can have the same start and end node • Dummy activities are used in AOA • Start the network by finding those activities that have no predecessors • Calculate activity times using probabilistic or deterministic means TCS2411 Software Engineering

  20. Dummy Activity • Represented by dotted arrow • Used when relationships between activities require no work • Applied when • two activities start and end similarly • succeeding activities have partial dependencies on predecessor activities TCS2411 Software Engineering

  21. PERT R&D Development Originally focused on time only Uses probabilistic time estimates AOA based Critical path & slack CPM Construction Time and Cost Uses deterministic time estimates AON based Critical path & slack Used in most software PERT and CPM TCS2411 Software Engineering

  22. GANTT Charts • Horizontal time representation of PERT/CPM, aka Timeline charts • Slack times shown as dashed lines • Critical path events are often milestones • Inadequate for showing dependencies • PERT/CPM is required to control the schedule • Can be used as a scheduling mechanism. TCS2411 Software Engineering

  23. Gantt Chart Example A D B C E G F time Milestone TCS2411 Software Engineering

  24. Project Planning Summary Objectives Scope Specs Organizational Structure Technical Criteria Documentation Responsibility Chart WBS Project Plan Material & Manpower Work Packages Networks Schedules TCS2411 Software Engineering

  25. Decision Tree Analysis • Software engineering managers are often faced with a make/buy decision to acquire a computer software. • This decision can be solve by computing Decision Tree Analysis. • Example : System X, can be build (in-house developer), reuse, buy or contract (employees outside vendor). TCS2411 Software Engineering

  26. The Make-Buy Decision TCS2411 Software Engineering

  27. Computing Expected Cost expected cost = (path probability) x (estimated path cost) i i For example, the expected cost to build is: expected cost = 0.30($380K)+0.70($450K) build = $429 K similarly, expected cost = $382K reuse expected cost = $267K buy expected cost = $410K contr TCS2411 Software Engineering

  28. References • “Software Engineering: A Practitioner’s Approach” 5th Ed. by Roger S. Pressman, Mc-Graw-Hill, 2001 • “Project Management: A Managerial Approach” by Jack R. Meredith & Samuel J. Mantel, Jr. , John Wiley, 1989 • “Project Management: Principles and Practices” by M. Pete Spinner, Prentice-Hall, 1997 • “Goal Directed Project Management”, 2nd Edition, by Erling S. Andersen, Kristoffer V. Grude & Tor Haug, Kogan Page, 1995 TCS2411 Software Engineering

More Related