1. Chapter 11
Project Management

2. Outline Intro Managing Projects What is Project Management?
Project Manager
Project Failures & Successes
Managing Projects
PMBOK
SDLC
Core Process 1 – Project Initiation
Core Process 2 - Planning

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

4. Project Manager A systems analyst with a diverse set of skills
management
leadership
technical
conflict management
customer relationship
Responsibilities
Internal: Schedule, recruit & train, Assign work, Manage risk, Monitor & control project deliverables
External: Communicate with Client, Oversight Committee , Users, Report status & progress, Identify resource needs & obtaining resources

5. Project Success vs. Failures
Categories of project success
Successful projects – on time, within budget, on scope
Challenged projects – failure in one area
Failed projects – cancelled or not used
1/3 to 1/2 of projects are challenged or fail
Reasons for 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.

6. Where do IS Development Projects come from?
Response to an opportunity
Resolve a problem
Response to an external directive

7. Quality Software Fit for Intended Purpose Usability Robustness
Reliable
Secure
Maintainable

8. Core Process 1: Identify problem/need & obtain approval

9. Core Process 1a: Identify the Problem cont.
System Vision Document
Problem Description
System Capabilities
Business Benefits

10. Core Process 1b: Quantify approval factors
Determine the following:
Estimated Time to Completion
Estimated Cost
One time vs. Recurring Costs
Tangible vs. Intangible Costs
Anticipated Benefits

11. Core Process 1c: Perform Risk & Feasibility Study
Risk Management Plan
Risk, Probability, Impact, and Plan
Feasibility Study
Economic
Operational
Organizational/Political
Technological
Resource
Schedule

12. Core Process 1d: Review w/Client & Obtain Approval
Executive committee
Organization made aware of the project & its importance

13. Core Process 2: Plan and Monitor the Project

14. Core Process 2a: Establish the project environment
Communication
internal and external; 3Ws+H
Work environment
HW, SW, workspace, staff
Processes & procedures followed
Reporting, Documentation
Programming approach, testing, Deliverables
Code and version control

15. Core Process 2b: 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

16. Work Breakdown Structure (WBS)
A hierarchical list of activities of a project
Used to create the work schedule
Not an exhaustive to-do list
Specifies "what" not "how"

17. WBS (in MS Project) 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

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

19. Core Process 2c, 2d, 2e 2c: Staff &Allocate Resources
Resource plan
Technical & user staff
Form smaller work groups
Training, team-building exercises
2d: Evaluate Work Processes
Communication, relationships
Deadlines
Issues, bottlenecks, or problems
Lessons learned
2e: Monitor progress & make corrections
Issues Tracking Log

20. Issues-Tracking Log

21. Project Management Body of Knowledge
PMBOK - a global standard for project management
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
Characteristics:
Fit for Intended Purpose, Usability, Robustness, Reliable, Secure, Maintainable
Agile Project: Quality assessed after each iteration

22. Project Management Body of Knowledge
PMBOK
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 Integration Management
Integrating all the other knowledge areas into one seamless whole
Project Stakeholder Management
Identification of & communication with stakeholders