{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

ISOM221+Lecture+22+-+Project+Management

ISOM221+Lecture+22+-+Project+Management - Agenda ISOM221...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 22: Project Management 1 Agenda Understand key concepts of project management Become familiar with estimation Be able to create a project workplan Understand how to coordinate project activities 2 Project Management The discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives The art of project management is in making trade-offs among three key concepts Scope / Quality (what the system does) Schedule (when the project will be finished) Cost (how many people are needed) 3 Trade-offs Cost Project management involves balancing trade-offs among the three key project Schedule Scope / Quality parameters Project 4
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Expectations Management Expectations management matrix –a tool used to understand the dynamics and impact of changing the parameters of a project The most important The second most important The least important Can have only one X in each row and each column 5 Lunar Project Expectations Management 6 Typical, Initial Expectations for a Project 7 Adjusting Expectations 8
Background image of page 2
Changing Priorities 9 Agenda Understand key concepts of project management Become familiar with estimation Be able to create a project workplan Understand how to coordinate project activities 10 Industry Standards for Business Applications System Development Life Cycle Planning 15% Analysis 20% Design 35% Implementation 30% 11 Function Point Approach 12
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Step 1: Estimate System Size A function point is a measure of program size based on the system’s number and complexity of inputs, outputs, queries, files, and program interfaces Examples: Inputs: forms Outputs: reports Queries: database queries Files: database records Program interfaces: data entry screens 13 14 Converting from Function Points to Lines of Code 15 Step 2: Estimate Required Effort Effort is a function of the system size combined with production rates (how much work someone can complete in a given time) For small-to moderate-sized business software projects (i.e., 100,000 lines of code and <10 programmers), a simple model is: Effort (in person-months) = 1.4 * thousands of lines of code
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}