Project Management April 26, 2005
Between Now and Lunch <ul><li>Before we begin. </li></ul><ul><li>What is Project Management? </li></ul><ul><li>The Project...
Before We Begin <ul><li>Project Management usually takes between 4 and 8 weeks of intensive training. </li></ul><ul><li>An...
What is Project Management? <ul><li>Project management  is a set of principles, practices, techniques, and facilitation of...
Project Management (Cont.) <ul><li>There are two aspects of Project Management:  What and How. </li></ul><ul><ul><li>The “...
Project Management (What) <ul><li>The  What  -- every project has three primary goals: </li></ul><ul><ul><li>To create som...
Project Management (What cont.) <ul><ul><li>Secondary goals are goals other than the primary goals that must be specified ...
Project Management (How) <ul><li>Process ( How ) will always affect task performance ( What ).  </li></ul><ul><ul><li>In m...
Project Management (How cont.) <ul><ul><li>Most projects fail from the beginning because they are not clearly defined and ...
Project Management (How cont.) <ul><ul><li>All the people within a project (programmers - for an IT project, Sponsors, bus...
The Project Management Triangle <ul><li>Project management control can  only  be achieved when cost, time, performance obj...
The Project Management Triangle <ul><li>When managing any project, there are four constraints you must take into considera...
<ul><ul><li>Cost  (C) refers to the labor cost to do a job. (This may or may not include capital equipment and material co...
The Project Management Triangle   (cont) <ul><li>When one of these constraints changes, at least one of the others must ch...
The Project Management Triangle
Project Methodology <ul><li>Documentation about the consistent way of running projects is called a methodology.  It prescr...
Project Methodology (cont.) <ul><li>It should tell who is responsible for various aspects of the project, and it should sp...
Project Life Cycle <ul><li>Projects have a life cycle.  A complete development process that takes each project  from begin...
Project Life Cycle (cont)
Planning and Establishing the Project Baseline <ul><li>Before you can develop a project's baseline you must complete the f...
Planning and Establishing the Project Baseline (cont) <ul><li>The first priority during implementation planning is to iden...
Planning and Establishing the Project Baseline (cont) <ul><li>The WBS plays a big role during implementation planning beca...
Planning and Establishing the Project Baseline (cont) <ul><li>Because the WBS lists all project tasks, it also provides th...
Planning and Establishing the Project Baseline (cont) <ul><li>A finished WBS looks similar to an organizational chart.  </...
Planning and Establishing the Project Baseline (cont) <ul><li>The final step in developing the WBS is to distribute the fi...
Planning and Establishing the Project Baseline (cont) <ul><li>Further a  network diagram  is developed </li></ul><ul><li>I...
Planning and Establishing the Project Baseline (cont) <ul><li>The illustration pinpoints what tasks must precede others, t...
Roles and Responsibilities <ul><li>Project Sponsor </li></ul><ul><li>Project Manager </li></ul><ul><li>Project Programming...
Process Review <ul><li>The purpose of a process review is to learn from experience so that we can avoid those things that ...
Where do Projects Fail?
Upcoming SlideShare
Loading in …5
×

ELT Project Management Presentation by Bob Morlock

833
-1

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
833
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
48
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The project sponsor makes sure that a need is met or a problem is solved by taking steps to initiate a project. She determines the project scope and oversees development of a project plan. She influences others to be sure that the project is given enough priority and resources to ensure that it is successfully initiated and continues to thrive. The project sponsor is often a senior officer in the organization&apos;s management and may be responsible for securing funding for the project. She reviews and approves the project plan and approves all changes in project scope. The project manager or project leader is responsible for ensuring the success of the project. To succeed, he must work closely with the sponsor to ensure that adequate funding and resources are applied to the project. The project manager or project leader is responsible for ensuring the success of the project. To succeed, he must work closely with the sponsor to ensure that adequate funding and resources are applied to the project. He manages the day-to-day operations of the project activities and works with the project team members to resolve any technical or personnel issues. He also monitors the progress of the project, making sure it is completed on time and within budget. Large projects often include quality assurance testers and documentation specialists as part of the project team. Quality assurance testers test the product or process at various stages of development to ensure that it will meet the needs of the customers or users. Documentation specialists assist the project manager and team by writing product user or technical manuals and reports. They may also record meeting minutes and ensure that a history of the project decisions and milestones is written and preserved.
  • ELT Project Management Presentation by Bob Morlock

    1. 1. Project Management April 26, 2005
    2. 2. Between Now and Lunch <ul><li>Before we begin. </li></ul><ul><li>What is Project Management? </li></ul><ul><li>The Project Management Triangle. </li></ul><ul><li>Project Methodology </li></ul><ul><li>The Project Life Cycle </li></ul><ul><li>The “Movie” </li></ul><ul><li>Planning and Establishing the Project Baseline. </li></ul><ul><li>Roles and Responsibilities </li></ul><ul><li>Where Do Projects Fail? </li></ul><ul><li>Is IT Really Different </li></ul><ul><li>Questions? </li></ul>
    3. 3. Before We Begin <ul><li>Project Management usually takes between 4 and 8 weeks of intensive training. </li></ul><ul><li>Another 2 – 3 years to apply that knowledge. </li></ul><ul><li>The information given here in the next 3 hours is an abridged version, covering the basics. </li></ul>
    4. 4. What is Project Management? <ul><li>Project management is a set of principles, practices, techniques, and facilitation of the planning, scheduling, and control of all activities that must be done to meet project objectives. It is a disciplined way of organizing a job and leading a team to help control costs, manage scope, performance, and outcomes and also to mitigate risks. </li></ul>
    5. 5. Project Management (Cont.) <ul><li>There are two aspects of Project Management: What and How. </li></ul><ul><ul><li>The “ What ” is the task to be performed. </li></ul></ul><ul><ul><li>The “ How ” relates to the “process” used to reach the desired outcome. Process includes both the solving of the task itself, and how the team functions in total – how they interact, solve problems, make decisions, run meetings, and every other aspect of team performance. </li></ul></ul>
    6. 6. Project Management (What) <ul><li>The What -- every project has three primary goals: </li></ul><ul><ul><li>To create something (like a product, procedure, process or other deliverables). </li></ul></ul><ul><ul><ul><li>Deliverables are those clearly defined results, goods or services produced during the project or at its outcome. </li></ul></ul></ul><ul><ul><li>To finish all tasks within an agreed upon schedule. </li></ul></ul><ul><ul><li>To complete the project within an established budget. </li></ul></ul>
    7. 7. Project Management (What cont.) <ul><ul><li>Secondary goals are goals other than the primary goals that must be specified to actually define the project, sometimes referred to as objectives and/or outcomes that are mutual expectations and define the scope of work. </li></ul></ul>
    8. 8. Project Management (How) <ul><li>Process ( How ) will always affect task performance ( What ). </li></ul><ul><ul><li>In manufacturing, managers have studied every step of their process to eliminate non-value-added steps, to reduce scrap and re-work, and to optimize the process as much as possible. </li></ul></ul><ul><ul><li>This same kind of scrutiny can improve non-manufacturing processes as well, to allow faster, smoother processes that can drastically improve task performance and produce a more consistent process. </li></ul></ul>
    9. 9. Project Management (How cont.) <ul><ul><li>Most projects fail from the beginning because they are not clearly defined and poorly planned. Processes are ignored in favor of speed to complete the project – The drive to “just get it done” . </li></ul></ul><ul><ul><li>If we do not have good processes, any tools used will only help us to document failures with great precision. </li></ul></ul><ul><ul><li>Organizations and project teams consist of people. Yet so much time is used for managing the physical resources, inventory, tools, schedules, status reports, and other activities which takes time from the project, that the &quot;people&quot; part is easily overlooked. And, if people do not perform well, neither will the processes and the project's outcome suffers. </li></ul></ul>
    10. 10. Project Management (How cont.) <ul><ul><li>All the people within a project (programmers - for an IT project, Sponsors, business personnel, etc.), their performance, and their communication are part of the Businesses culture. </li></ul></ul><ul><ul><ul><li>Culture comprises accountability, communications, ownership, learning, and embracing change. </li></ul></ul></ul><ul><ul><ul><li>Culture is related to people. It describes the sum total of the values, attitudes, traditions, and behaviors that exist in an organization. One way to know when people are talking about their culture is when they say, &quot;We don't do it that way here.&quot; </li></ul></ul></ul>
    11. 11. The Project Management Triangle <ul><li>Project management control can only be achieved when cost, time, performance objectives and scope are clearly documented, realistically derived, and deliberately managed. </li></ul>
    12. 12. The Project Management Triangle <ul><li>When managing any project, there are four constraints you must take into consideration. These constraints apply to both large and small projects. </li></ul><ul><ul><li>Performance (P) refers to the project's requirements and objectives and the quality level of each. What results must the project produce? What features should it have? What will be needed to meet the customer's satisfaction? What are the deliverables and outcomes? </li></ul></ul>
    13. 13. <ul><ul><li>Cost (C) refers to the labor cost to do a job. (This may or may not include capital equipment and material costs which may by accounted for separately.) </li></ul></ul><ul><ul><li>Time (T) refers to the time required to complete the project. </li></ul></ul><ul><ul><li>The area of the triangle adds another constraint: scope (S). Scope is the amount of work that must be done to complete the project; it is the magnitude of the job. </li></ul></ul>The Project Management Triangle (cont)
    14. 14. The Project Management Triangle (cont) <ul><li>When one of these constraints changes, at least one of the others must change, too, to compensate. </li></ul><ul><ul><li>For instance, if the time to compete is reduced, you must either reduce the performance requirements/objectives or increase the cost (meaning resources). </li></ul></ul><ul><ul><li>Also, if new tasks are added to the project, increasing the scope, then one or more of the other pieces — performance or cost or time — must be increased to accommodate the change. </li></ul></ul>
    15. 15. The Project Management Triangle
    16. 16. Project Methodology <ul><li>Documentation about the consistent way of running projects is called a methodology. It prescribes what kinds of steps must be taken, what kinds of documents must be produced at each step, what kinds of approvals are needed for certain aspects of the project, how changes will be handled, and what records must be filed when the project is closed out. </li></ul><ul><li>It must also specify what approvals are needed for various actions, such as procurement, changes to plan, budget variances, and risks. </li></ul>
    17. 17. Project Methodology (cont.) <ul><li>It should tell who is responsible for various aspects of the project, and it should spell out the roles and responsibility of each member of the team and their accountability and also the limits of each stakeholder's authority, . </li></ul><ul><li>The project methodology spells out how a kick-off meeting is to be held, who should attend, what they are required to have ready for the meeting, and when it is to take place. The same is true for status, data model, business process model, and design review meetings. </li></ul><ul><li>The methodology documents the project requirements and also the entrance and exit criteria for each of the phases of project development life cycle. </li></ul>
    18. 18. Project Life Cycle <ul><li>Projects have a life cycle. A complete development process that takes each project from beginning to end. Life cycles are divided into phases to help structure and manage the project. </li></ul><ul><li>Different businesses may use different life cycles, with differing numbers of phases and differing phase names, but they are all similar and all contain the same essential activities. This training will use the following life cycle: </li></ul>
    19. 19. Project Life Cycle (cont)
    20. 20. Planning and Establishing the Project Baseline <ul><li>Before you can develop a project's baseline you must complete the following tasks involved in the Definition and Planning phases: </li></ul><ul><ul><li>Identify the major stakeholders </li></ul></ul><ul><ul><li>Establish feasibility based on priority and goals </li></ul></ul><ul><ul><li>Define the project’s performance, time, cost, scope constraints, and clear understandable requirements. </li></ul></ul><ul><ul><li>Develop a Risk Analysis </li></ul></ul><ul><ul><li>Identify an overall strategy for accomplishing the project results. </li></ul></ul>
    21. 21. Planning and Establishing the Project Baseline (cont) <ul><li>The first priority during implementation planning is to identify all of the tasks that have to be completed to meet the goals of the project and put it into a form that is easy to view and quickly understand. </li></ul><ul><li>The work breakdown structure ( WBS ) is a method of subdividing work into smaller and smaller increments to permit accurate estimates of durations, resource requirements, and costs. </li></ul>
    22. 22. Planning and Establishing the Project Baseline (cont) <ul><li>The WBS plays a big role during implementation planning because it is the foundation upon which other project elements are based. </li></ul><ul><li>As a detailed portrait of all the work involved in a project, a WBS also illustrates the scope (or magnitude) of a project. </li></ul><ul><li>This is important because stakeholders are sometimes surprised at the cost estimates, and the WBS helps to see why the project is going to cost as much as you have estimated. </li></ul>
    23. 23. Planning and Establishing the Project Baseline (cont) <ul><li>Because the WBS lists all project tasks, it also provides the basis upon which resource assignments and task durations can be made. The task duration estimates are used to calculate labor costs for all work so that a labor budget and schedule for the project is developed. </li></ul>
    24. 24. Planning and Establishing the Project Baseline (cont) <ul><li>A finished WBS looks similar to an organizational chart. </li></ul><ul><li>It is a graphical listing of the hierarchy of work to be accomplished. </li></ul><ul><li>A finished WBS, sequences the tasks using a technique called a network diagram, break identified tasks down into greater levels of detail . </li></ul>
    25. 25. Planning and Establishing the Project Baseline (cont) <ul><li>The final step in developing the WBS is to distribute the final draft to key stakeholders for review. </li></ul><ul><li>Using a ski trip as an example, you ask you develop and review the following WBS. </li></ul>
    26. 26. Planning and Establishing the Project Baseline (cont) <ul><li>Further a network diagram is developed </li></ul><ul><li>It represents project tasks in a logical order, going left to right and allow you to put the tasks (from the WBS) into a graphical representation that shows the work flow and the relationships between project tasks. </li></ul><ul><li>It is the roadmap for the project and identifies the critical path for the project. </li></ul><ul><ul><li>The critical path is the longest path it takes to complete the project, from start to finish. </li></ul></ul>
    27. 27. Planning and Establishing the Project Baseline (cont) <ul><li>The illustration pinpoints what tasks must precede others, those dependent on other tasks, which are parallel and also those tasks which can be completed at the same time. </li></ul>
    28. 28. Roles and Responsibilities <ul><li>Project Sponsor </li></ul><ul><li>Project Manager </li></ul><ul><li>Project Programming Team </li></ul><ul><li>Focus Group of Customers/Users </li></ul><ul><li>Stakeholders </li></ul>
    29. 29. Process Review <ul><li>The purpose of a process review is to learn from experience so that we can avoid those things that were not done well and continue doing those things that were done well. </li></ul><ul><li>It is not a witch-hunt. If we go about it in a &quot;blame and punishment&quot; way, people will hide their faults. If we go on a witch-hunt, we risk creating witches where none existed before. </li></ul>
    30. 30. Where do Projects Fail?
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×