1. WEEK 3 Introduction to Project Management

2. Agenda Review – Any questions from last week Phase 2: Planning ◦ Project Plans & Deliverables

3. Planning Projects “Planning is laying out the project groundwork to ensure your goals are met“ Initiating Planning ExecutingControllingClosing

4. Purpose of Planning Process Answers:  How are we going to solve the problem  What resources are required  How much effort is required  What are the due dates

5. Project Plans ◦ Are Not a Microsoft Project File ◦ Are documents that  Define schedule  Define resources needed  Project deliverables

6. Project Deliverables ◦ Are measurable outcomes or specific items that must be produced to fulfill the outcomes of the project. ◦ All deliverables must be described in enough detail so that they can be differentiated from related deliverables. For example:  A twin engine plane vs a single engine plane  A daily report vs a weekly report

7. Project Planning Processes Scope Planning  Specifies the in-scope requirements for the project and facilitates the creation of the WBS Preparing a Work breakdown structure (WBS)  Specifies the breakdown of the project into tasks and sub tasks Communication Planning  Communication strategy with all project stakeholders

8. Project Planning Processes Cont. Project Schedule Development  Specifies the entire schedule of the activities detailing the sequence of execution Resource Planning  Specifies who will do the work  Any special equipment or skills required Risk Planning  Charts the risks, contingency plan and mitigation strategies

9. DEVELOPING SMART GOALS

10. Articulating Project Objectives Specific (get into the details). Measurable (use qualitative language so you know when you are finished). Achievable or Acceptable (to stakeholders). Relevant or Realistic (in terms of achievement). Time bound (deadlines not durations) http://www.youtube.com/watch?v=YmOS3dj9h0s

11. When Goals are Drafted Is this goals specific? Are the results easily measurable? Achievable? Realistic? Does my goal include a completion date?

12. SMART Goals Example GOAL = Write A Long Essay ◦ Specific: I will write my 15 page final paper for my Business class. ◦ Measurable: I will report my progress in terms of pages completed per week. ◦ Achievable or Attainable: By completing 2 pages a day for 8 days, I will be able to finish my paper. ◦ Realistic: I cannot write a lot at a time, so I am spreading it out over time. ◦ Timely: I will finish this paper in 8 days.

13. Develop SMART Goals Workshop1 3 minute activity by yourself

14. Develop SMART Goals Workshop 2 As a class, for our wedding

15. Develop SMART Goals Workshop 3 In teams, for your one day fundraising

16. PROJECT REQUIREMENT PLANNING

17. Project Requirements Requirements specify what the project deliverable should look like and what it should do. Divided into six basic categories: FunctionalRegulatory Non-FunctionalBusiness TechnicalUser

18. Functional Project Requirements Describe the characteristics of what you want your deliverable to be. Example: ◦ System shall provide users with the ability to select whether or not to produce a hardcopy transaction receipt before completing a transaction.

19. Non-Functional Requirements Describe criteria that can be judged Describe restrictions to be placed on the deliverable Example: ◦ All displays shall be in white 14 pt Arial text on black background.

20. Technical Requirements Emerge from functional requirements May include: ◦ Hardware details ◦ Telecommunication protocols

21. Regulatory Requirements Can be internal or external Usually non-negotiable Example: ◦ All ATMs shall connect to standard utility power sources within their civic jurisdiction, and be supplied with uninterruptible power source approved by said company.

22. Business Requirements Always from a management perspective States business rationale for the project Example: ◦ By providing superior service to our retail customers, ABC Bank’s ATM network will allow us to increase associated service fee revenue by 10% annually on an ongoing basis, using a baseline of December 2011.

23. User Requirements What users need to do with the system or product Example: ◦ The system shall complete a standard withdrawal from a personal account, from login to cash, in less than two minutes for a first time user.

24. WORK BREAKDOWN STRUCTURE (WBS)

25. Define WBS PMI describes WBS as “a deliverable- oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create required deliverables.” In our words: ◦ A structured method for defining the work of the project

26. Sample WBS WBS does not show the sequence When creating, start with the goal and then break it down into smaller and smaller deliverables (milestones) Deliverables ◦ define what you are going to do ◦ re nouns Activities ◦ define how you are going to accomplish it ◦ Activities are verbs GoalDeliverable Activity

27. Benefits of WBS Identifies all work necessary to meet the scope of the project Clarifies responsibilities Forces detailed planning and documentation Provides structure for measuring success Identifies milestones

28. Milestones Identifiable points that represents a requirement or completion of an important set of activities Why use milestones? ◦ Helps identify progress ◦ Helps define dependencies ◦ Provides visibility of major deliverable dates

29. Milestones vs Tasks Milestones are what management &/or clients really want to hear about Milestones are the large outcome of many little tasks. Tasks are activities that need to be completed in order to make the milestone happen.

30. WBS Comes from ◦ Past projects ◦ Templates and documents of procedures ◦ System tutorials ◦ Brainstorming ◦ Subject Matter Expert (SME)

31. WBS Exercise #1 Group Activity ◦ Using sticky notes create a WBS for your fundraising cupcake (refer to slide 25)

32. Hybrid / Homework Purchase eBook Read Chapter 1 Complete all activities required while reading chapter 1 Complete the Fill in the Blank for Chapter 1 Complete the T/F for Chapter 1

33. Quiz Time