Project Management Chapter 11

Outline Project Management - defined Project Failures & Successes PMI & PMBOK SDLC – 1st two phases Project Initiation Planning

Project Management Organizing and directing other people to achieve a planned result within a predetermined schedule & budget

Project Manager Internal Responsibilities External Responsibilities Schedule Recruit & train Assign work Manage risk Monitor & control project deliverables External Responsibilities Communicate with the client, users, oversight committee Report status & progress Identify resource needs & obtaining resources

Project Success Categories of Project Success Successful projects – on time, within budget, on scope Challenged projects – failure in one area Failed projects – cancelled or not used Reasons for Project Failure Inadequate executive support for the project Inexperienced project managers Undefined project management practices Poor IT management & IT procedures Unclear business needs and project objectives Inadequate user involvement Project management knowledge & skills are valued & needed to improve this record.

PMI – Project Management Institute PMI – a professional organization focused on project management www.pmi.org PMBOK – Project Management Body of Knowledge Standards and guidelines for project management FYI: for info on sub-processes for each knowledge area, see Table 11-3 on pg 33 Certification exams www.pmi.org/certifications Certified Associate in Project Management (CAPM) – entry-level certification Project Management Professional (PMP) – gold standard

PMBOK – 10 Knowledge Areas Project Integration Management Integrating all the other knowledge areas into one seamless whole including developing and executing the project plan. Project Scope Management Defining, verifying, & controlling scope Agile Project: Scope is not well understood, but needs to be controlled Project Time Management Scheduling & monitoring milestones Agile Project: Schedule must be flexible due to changes Project Cost Management Calculating cost/benefit analysis Monitoring expenditures Agile Project: Costs are more difficult to estimate Project Quality Management Comprehensive plan for ensuring quality QC for every phase Agile Project: Quality assessed after each iteration Competing Goals Deliver Features: ____ Cost: ____ Time: ____ Quality: ____ Characteristics of Quality Systems Fit for Intended Purpose Usability Robustness Reliable Secure Maintainable

PMBOK – 10 Knowledge Areas Project Human Resource Management Recruiting, hiring, training, motivating, & team building Project Communications Management Identifying all stakeholders Establishing communication mechanisms & schedules Project Risk Management Identifying and reviewing all potential risks Developing plans to reduce these risks Risk Management Plan Project Procurement Management Developing RFP, evaluating bids, writing contracts, & monitoring vendor performance Project Stakeholder Management Identification of & communication with stakeholders

SDLC Project Initiation Core Process 1: Identify the problem and Obtain approval

Project Initiation Identify the problem Document the objective Preliminary investigation System Vision Document Problem Description System Capabilities Business Benefits Project Initiation Identify the problem and Obtain approval

Project Initiation Quantity project approval factors Estimated Time to Completion Estimated Cost One time vs. Recurring Costs Tangible vs. Intangible Costs Anticipated Benefits Project Initiation Identify the problem and Obtain approval

Project Initiation Perform Risk & Feasibility Assessments Risk Management Plan Risk, Probability, Impact, and Plan Feasibility Study Economic Operational Organizational/Political Technological Resource Schedule Project Initiation Identify the problem and Obtain approval

Project Initiation Review with Client & Obtain Approval Executive committee Organization made aware of the project & its importance Project Initiation Identify the problem and Obtain approval

SDLC Planning Core Process 1: Plan and Monitor the Project

Planning Establish the project environment Communication Internal & External Work environment Hardware, software, workspace, staff Processes & procedures followed Reporting, Documentation Programming approach, testing, Deliverables Code and version control Planning Plan and Monitor the Project

Planning Schedule the work Overall Iteration Schedule Detailed Work Schedules List tasks to be completed  Work breakdown structure Estimate effort and identify dependencies Create a Schedule Gantt Chart Dependencies, Time estimates, Critical Path Planning Plan and Monitor the Project

Work Breakdown Structure (in MS Project) A hierarchical list of activities of a project Used to create the work schedule Not an exhaustive to-do list Specifies "what" not "how" Summary Tasks Details Tasks Produce a measureable deliverable Fit "80-hour" rule no activity > 80 hrs. (2 wks) Assigned to only 1 person accountability adequate tracking

Gantt Chart It shows: Start & end dates Duration Predecessors sequence Resources assignments Critical path Slack

Planning Staff & Allocate Resources Evaluate Work Processes Resource plan Technical & user staff Form smaller work groups Training, team-building exercises Evaluate Work Processes Communication, relationships Deadlines Issues, bottlenecks, or problems Lessons learned Planning Plan and Monitor the Project

Planning Monitor progress & make corrections Issues Tracking Log Plan and Monitor the Project