1. Project Management Basics

2. 5 Phases Initiating Planning Executing Controlling Closing

3. Initiating Recognizing that a project is worth doing – It is easier to complete projects if we are enthusiastic about them and if they match our personal values Values Balancing – A job not worth doing is not worth doing well – What is the feasibility? – What is the risk?

4. Values Identification: Values tell us why we do what we do-they are the underlying motivators What are the qualities that make your life better? What helps you survive, thrive and prosper? What would you like to have more of in your life? What would you miss if it was eliminated from your life? What qualities define the person you want to be?

5. The Value Wheel Determine your current ideal performance for each value listed Rate your current actual performance and place a dot by the appropriate number Connect the dots

6. Initiating (cont.) Defining the overall project goal – Vision – Must be clearly defined Determining what the project should accomplish – The importance of creativity in PM Mindmapping

7. Vision Purpose pulls us in the direction we want to go Exercise – Write a one-sentence vision statement for your life, based upon the values identified previously

8. Key Criteria for Setting Goals Be specific Be realistic Have a time component Be measurable Be agreed upon Identify responsibility for achieving

9. Mindmapping 2 Rules: 1. There are no bad ideas 2. There are no wrong mindmaps Uses include to do lists, brainstorming, task analysis, vacation planning, decision making, etc.

10. Mindmap Steps 1. Lighten up—brain dump 2. Think fast-capture ideas quickly 3. Judge not-write down everything that comes to mind 4. Break Boundaries-don’t write neatly on paper 5. Center first-don’t use just one side of your brain 6. Free associate-branch off of other ideas 7. Keep moving-the bigger the paper the more ideas 8. Allow organization-later

11. Mindmap Exercise How can we make the education system work better?

12. INITIATING(cont.) Defining general expectations of stakeholders Defining the general project scope – Productivity pyramid Selecting the initial members of the project team

13. Scope The size of the project Key is balancing scope versus complexity Tends to creep

14. Productivity Pyramid Values – The why Long range goals – The what Intermediate Steps – The how Daily tasks – The now BOEING 777 Example – Surface problems – Trust – No limitations Video

15. Selecting the Team Planning team – Prepare the project plan – Supervisory and technical subject matter experts – Define resource and technical requirements Core team – Specific functional areas – Stakeholder analysis

16. PLANNING Refining the project scope – Balancing time, resources, results Time Management-Ch. 4 Day planners/consistency of purpose Listing tasks and activities that lead to achieving project goals – VPIC Visualize/Plan/Implement/Close “You can’t prioritize a stack”

17. Planning (cont.) Sequencing activities in the most efficient manner possible – What needs to be done – When it needs to be done – Hunks chunks and bites-break it into manageable pieces – Where the information is stored – Who is responsible for each phase – Identify possible hot spots – Failsafe retrieval

18. Planning-Same time, same place Work breakdown structure (WBS) – Defines the project work in specific tasks Responsibility matrix – Defines organization, key individuals and their responsibilities Events and Milestones – Identifies critical points and major occurences on the project schedule Gantt charts – Display the MPS and detailled task schedules

19. PLANNING (cont.) Developing a workable schedule and budget – Backward and forward scheduling Getting the plan approved by appropriate stakeholders Organizational inertia – CQ quotient (collaborative/not) p. 224

20. IMPLEMENTATION “Clutter sucks creativity and energy from your brain!” Leadership – Kick off meeting Meeting with team members – delegation Communications – Trash/information/action item

21. Delegation A. Authority-the person doing the task must have the authority to accomplish it B. Responsibility- shared by both parties C. Commitment- to achieving the end result in the agreed upon time frame

22. “Success is the ability to go from failure to failure without losing your enthusiasm.” Projects are long-term important but not short-term urgent.

23. IMPLEMENTATION(cont.) Installation/training/repair Preventative maintenance systems Back up systems/disaster and recovery Fire fighting Securing necessary resources – Authority – Responsibility – Commitment

24. Interuptions Prioritize the interuption Swap offices Work in a conference room Leave the office Work at home Put up a ‘do not disturb’ sign Work in 20-30 minute chunks

25. CONTROLLING Monitoring deviation from plan – Critical path – Reliability-if after repeated samplings, you achieve results that are close to each other – Validity- are we really measuring what we think we are? Project review meetings Corrective action – Crashing Cost Risk Evaluating change requests

26. Project Review Meeting What has happened so far? What still needs to happen? What problems, if any, are we having?

27. CONTROLLING(cont.) Rescheduling Adapting resource levels Changing scope Readjustment of goals if necessary

28. CLOSING Disbanding the team Learning post-mortem Review of outcomes Final report Celebrate!!!