Download Project Risk Management

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Earned value management wikipedia , lookup

PRINCE2 wikipedia , lookup

Construction management wikipedia , lookup

Transcript
Chapter 11
• Intro



What is Project Management?
Project Manager
Project Failures & Successes
• Managing Projects


PMBOK
SDLC
• Core Process 1 – Project Initiation
• Core Process 2 - Planning
Organizing and directing other people
to achieve a planned result
within a predetermined schedule & budget
3
• 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
4
• 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.
5
• Response to an opportunity
• Resolve a problem
• Response to an external directive
•
•
•
•
•
•
Fit for Intended Purpose
Usability
Robustness
Reliable
Secure
Maintainable
8
• System Vision Document
Problem Description
 System Capabilities
 Business Benefits

• Determine the following:

Estimated Time to Completion

Estimated Cost
• One time vs. Recurring Costs
• Tangible vs. Intangible Costs

Anticipated Benefits
• Risk Management Plan

Risk, Probability, Impact, and Plan
• Feasibility Study






Economic
Operational
Organizational/Political
Technological
Resource
Schedule
• Executive committee
• Organization made aware of the project & its importance
13
• 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
14
• 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
15

A hierarchical list
of activities of a project
 Used to create the work schedule
 Not an exhaustive to-do list
▪ Specifies "what" not "how"
16

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
It shows:
 Start & end dates
 Duration
 Predecessors
▪ sequence
 Resources assignments
 Critical path
 Slack
18

2c: Staff &Allocate Resources
▪
▪
▪
▪

2d: Evaluate Work Processes
▪
▪
▪
▪
Resource plan
Technical & user staff
Form smaller work groups
Training, team-building exercises

Communication, relationships
Deadlines
Issues, bottlenecks, or problems
Lessons learned
2e: Monitor progress
& make corrections
▪ Issues Tracking Log
20
PMBOK
- a global standard for project management
Project Scope
Management
•
Project Time
Management
•
Project Cost
Management
•
•
Project Quality
Management
•
•
•
Defining, verifying, & controlling scope
 Agile Project: Scope is not well understood, but needs to be
controlled
Scheduling & monitoring milestones
 Agile Project: Schedule must be flexible due to changes
Calculating cost/benefit analysis
Monitoring expenditures
 Agile Project: Costs are more difficult to estimate
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
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