1. WEEK 6 Introduction to Project Management

2. Wk 6 Agenda Verify Hybrid Wk 5 Review Wk 5 ◦ Compressing the Schedule ◦ Risk Identification Techniques ◦ Project Assignment Questions? Execution Phase Continued Phase 4: Controlling

3. Any Questions of what we have seen so far?

4. Review Wk 5 - Compression What is compressing the schedule? How can you compress the schedule? What is the important rule to remember regarding compression? Which one is better? ◦ Look at all potential choices and then select the choice or choices that have the least negative impact

5. Review Wk 5 - Risks Risk Identification Techniques Affinity Diagrams:

6. Affinity Diagrams – How To: Read all ideas Sort ideas (generally done IN SILENCE so that no one is influenced by anyone else’s comments) Sort into natural themes by asking: ◦ What ideas are similar? ◦ Is this idea connected to any of the others? Keep moving the cards around until consensus is reached Create total group consensus

7. Controlling Projects “keeping things in control and in order“ InitiatingPlanning Executing Controlling Closing

8. Controlling Phase Ensuring that the project objectives are met by monitoring and measuring progress and taking corrective action when needed.

9. Controlling Phase Focus Involves measuring progress toward project objectives, monitoring deviation from the plan, and taking correction actions Outputs include performance reports, requested changes, and updates to various plans

10. Triple Constraint You must work with your clients to determine what their definition of success is. Scope Time Quality Cost

11. Project Change Management Definition: “a general term describing the procedures used to ensure that changes are introduced in a controlled and coordinated manner.”

12. Change Management Processes Change Request ◦ Requests to expand or reduce the project scope, modify policies, processes, plans or procedures, modify costs or budgets, or revise schedules. Change Order ◦ Used in some companies to identify approved change requests (order once it has been approved)

13. Changes Most change requests are the result of:  An external event  An error or omission in defining the scope of the product or project  A value-adding change (e.g., new technology, new software version, etc.)

14. Scope Creep Changes to the project that result in additional work. If not properly identified and managed properly, your project may come in considerably over budget and/or behind in schedule.

15. Hybrid / Homework Chapter 4

16. Quiz Time