Chapter 3 Project Management Power Point Presentation for

Objectives Become familiar with estimation. Be able to create a project workplan. Understand why

Project Management • The discipline of planning, organizing, and managing resources to bring about

IDENTIFYING PROJECT SIZE Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and

Cost Schedule Performance Trade-offs Cost Project management involves balancing trade-offs among the three key

Estimating Project Timeframes Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and

Function Point Approach Estimate System Size (function points and lines of code) Estimate Effort

CREATING AND MANAGING THE WORKPLAN Power. Point Presentation for Dennis, Wixom, & Tegarden Systems

Developing Work Plans • A work plan, is a dynamic schedule that records and

Sample Task name: Perform economic feasibility Start date: Jan 5, 2010 Completion date: Jan

Identifying Tasks • Top-down approach – Identify highest level tasks – Break them into

Work Breakdown Structure Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and

Gantt Chart Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design

Pert Chart • Used to communicate task dependencies • Allows easier visualization of tasks

Scope Management • Scope creep happens when new requirements are added to the project

Timeboxing Steps 1. Set the date for system delivery 2. Prioritize the functionality that

STAFFING THE PROJECT Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and

Staffing the Project • Determine average number of people needed – Divide total person-months

Reporting Structures Project Manager Functional Lead Analyst Technical Lead Analyst Programmer Power. Point Presentation

Motivation • Use monetary rewards cautiously • Use intrinsic rewards – Recognition – Achievement

Motivational Don’ts Assign unrealistic deadlines Ignore good efforts Create a low-quality product Give everyone

Conflict Avoidance Strategies • Clearly define roles and project plans • Make sure the

COORDINATING PROJECT ACTIVITIES Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and

CASE Tools • Computer-Aided Software Engineering (CASE) tools automate some or all of the

Standards Types of Standards Example Documentation standards The date and project name should appear

Documentation • Good documentation happens up front – Documentation that occurs only at the

Managing Risk Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design

Summary • • • Project Management Identifying Project Size Creating And Managing the Workplan

Slides: 28

Download presentation

Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing. Become familiar with how to staff a project. Understand how computer-aided software engineering, standards, and documentation improve the efficiency of a project. • Understand how to reduce risk on a project. • • • Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Project Management • The discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives – Cost – Schedule – Performance Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Cost Schedule Performance Trade-offs Cost Project management involves balancing trade-offs among the three key project parameters Project Schedule Performance Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Function Point Approach Estimate System Size (function points and lines of code) Estimate Effort Required (person-months) Estimate Time Required (months) Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

CREATING AND MANAGING THE WORKPLAN Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Developing Work Plans • A work plan, is a dynamic schedule that records and keeps track of all tasks to be accomplished over the course of the project • Created after a project manager has a general idea of the project’s size and rough schedule • The work plan is usually the main item in a project management software application Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Sample Task name: Perform economic feasibility Start date: Jan 5, 2010 Completion date: Jan 19, 2010 Person assigned to the task: Mary Smith (project sponsor) Deliverable(s): Cost-benefit analysis Completion status: Complete Priority: High Resources needed: Spreadsheet software Estimated time: 16 hours Actual time: 14. 5 hours Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Identifying Tasks • Top-down approach – Identify highest level tasks – Break them into increasingly smaller units • Methodology – Using standard list of tasks Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Pert Chart • Used to communicate task dependencies • Allows easier visualization of tasks on a critical path Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Scope Management • Scope creep happens when new requirements are added to the project after the original project scope was defined and “frozen. ” Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Timeboxing Steps 1. Set the date for system delivery 2. Prioritize the functionality that needs to be included in the system 3. Build the core of the system (the functionality ranked as most important) 4. Postpone functionality that cannot be provided within the time frame 5. Deliver the system with core functionality 6. Repeat steps 3 through 5 to add refinements and enhancements Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Staffing the Project • Determine average number of people needed – Divide total person-months of effort by the optimal schedule – Adding more people will not reduce schedule • Create a staffing plan – Roles required for the project – Reporting structure Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Reporting Structures Project Manager Functional Lead Analyst Technical Lead Analyst Programmer Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved. Programmer

Motivation • Use monetary rewards cautiously • Use intrinsic rewards – Recognition – Achievement – The work itself – Responsibility – Advancement – Chance to learn new skills Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Motivational Don’ts Assign unrealistic deadlines Ignore good efforts Create a low-quality product Give everyone on the project a raise Make an important decision without the team’s input • Maintain poor working conditions • • • Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Conflict Avoidance Strategies • Clearly define roles and project plans • Make sure the team understands how the project is important to the organization • Develop detailed operating procedures and communicate these to the team members • Develop a project charter • Develop schedule commitments ahead of time • Forecast other priorities and their possible impact on project Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

CASE Tools • Computer-Aided Software Engineering (CASE) tools automate some or all of the development process • Not a silver bullet, but advantages include: – Reduced maintenance costs – Improve software quality – Enforce discipline – Some project teams even use CASE to assess the magnitude of changes to the project Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Standards Types of Standards Example Documentation standards The date and project name should appear as a header on all documentation. Coding standards All modules of code should include a header that lists the programmer, last date of update, and a short description of the purpose of the code. Procedural standards Report to project update meeting on Fridays at 3: 30 PM. All changes to a requirements document must be approved by the project manager. Specification requirement standards Name of program to be created Description of the program’s purpose User interface design standards The tab order of the screen will move from top left to bottom right. Accelerator keys will be provided for all updatable fields. Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Documentation • Good documentation happens up front – Documentation that occurs only at the tail end of a project/phase is not very useful • Project binder(s) are best practices containing – All internal communications (e. g. minutes from status meetings) – Written standards – Letters to and from the business users – Deliverables from each task Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.

Summary • • • Project Management Identifying Project Size Creating And Managing the Workplan Staffing the Project Coordinating Project Activities Power. Point Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3 rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights reserved.