Software Project Management

(1)

Software Project Management

(2)

Objectives

z Introduce students to a variety of approaches and techniques in SPM z Use current SPM tools

z Develop new SPM ideas

z Document reading, experiences and ideas z Improve writing and presentation skills

(3)

Today

z Introduction to SE 362

z Fundamentals of Project Management

(4)

Course Outline

z Introduction to PM and SPM

z Software models and process improvement z Project planning, scheduling, estimation

z Personnel and project organization

z Change management, monitoring & control z Protocols and standards

(5)

Workload and Evaluation

z Six assignments (30%) z Midterm (20%)

z Final Exam (50%)

z In-class presentations, critiques, discussion z Groupwork for three of the assignments

(6)

Textbooks

z Recommended Text (Free, in the library!)

Quality Software Project Management, Futrell & Shafer

z Lots of Other Texts (Widely varying content)

Rapid Development, Steve McConnell

Information Technology Project Management, Kathy

Schwalbe

IT Project Management, Jack Marchewka

Software Engineering Project Management, edited by

Richard H. Thayer

(7)

Format

z Essentials of software project management z Research and textbook readings and writing z Real-world case studies

z Industry visitors z Highly interactive

(8)

My Background

z Civil Engineering

z Information Systems Management

z 15 years each in industry and academia z 1 year with KPMG, IT Consulting

z Projects of all shapes and sizes – health, construction, government

(9)

PM Profession

z Professional Organizations

– Project Management Institute (PMI) (pmi.org) – Software Engineering Institute (SEI)

– IEEE Software Engineering Group

z Certification

– PMI PMP

(10)

Project Management Skills

z Leadership

z Communications z Problem Solving z Negotiating

z Influencing the Organization z Mentoring

(11)

Software Project Management

Management Project Management Software Project Management

(12)

Some PM History

z 1970’s: Early PM ideas and software

– military, defense, construction industry – Fred Brooks, The Mythical Man-Month

z 1980’s: SPM, TQM

z 1990’s: Large shift to PM-based models

– 1990-93: Re-engineering, self-directed teams – 1996-99: Risk mgmt, project offices

(13)

Project Management

z What’s a project? z PMI definition

– A project is a temporary endeavor undertaken

to create a unique product or service

z Progressively elaborated

– With repetitive elements

z A project manager

(14)

Project vs. Program

Management

z What’s a ‘program’?

z Mostly differences of scale

z Often a number of related projects z Longer than projects

(15)

Interactions / Stakeholders

z As a PM, who do you interact with? z Project Stakeholders

– Project sponsor – Executives

– Team (developers and maybe others) – Customers

– Contractors (as needed) – Functional managers

(16)

PM Tools: Software

z Low-end

– Basic features, tasks management, charting

– MS Excel, Milestones Simplicity

z Mid-market

– Handle larger projects, multiple projects, analysis tools – MS Project (approx. 50% of market)

z High-end

– Very large projects, specialized needs, enterprise – AMS Realtime

(17)

Tools: Gantt Chart

(18)

Tools: Network Diagram

(19)

PMI’s 9 Knowledge Areas

1. Project integration management 2. Scope 3. Time 4. Cost 5. Quality 6. Human resource 7. Communications 8. Risk 9. Procurement

(20)

Strategy

z Classic Mistake Avoidance z Development Fundamentals z Risk Management

(21)

Four Project Dimensions

z People z Process z Product

(22)

Trade

-

_-

off Triangle

_{off Triangle}

(23)

Trade

-

_-

off Triangle

_{off Triangle}

z Know which of these are fixed & variable for every project

(24)

People

z “It’s always a people problem.”

Gerald Weinberg, The Secrets of Consulting

z Developer productivity: 10-to-1 range - Improvements:

- Team selection

- Team organization – Motivation

(25)

People …2

z Other success factors

– Matching people to tasks – Career development

– Balance: individual and team – Clear communication

(26)

Process

z Is process stifling?

z Two Types: Management & Technical z Development fundamentals

z Quality assurance z Risk management z Lifecycle planning

(27)

Process …2

z Customer orientation

z Process maturity improvement z Rework avoidance

(28)

Product

z The “tangible” dimension z Product size management

z Product characteristics and requirements z Feature creep management

(29)

Technology

z Often the least important dimension z Language and tool selection

(30)

Planning

z Determine requirements z Determine resources

z Select lifecycle model

(31)

Tracking

z Cost, effort, schedule z Planned vs. Actual

(32)

Measurements

z Actual (To date) and Projected

– Cost

– Schedule – Effort

(33)

Measurements …2

z Alternatives

– Earned value analysis – Defect rates

– Productivity (ex: SLOC)

(34)

Technical Fundamentals

z Requirements z Analysis z Design z Construction z Quality Assurance z Deployment

(35)

Project Phases

z All projects can be divided into phases z Project Life Cycle is all phases together z Each phase marked by Deliverables

(36)

Lifecycle Relationships

(37)

Software Project Management

z Key Issues: Cost, Quality, Time z Software Project Planning

(38)

_-

4 ₄

Incremental Release Process Model

1. Provide periodic demonstrations 2. Reach short-term goals

(42)

Software Project Control

Work Package Development

1. Work Breakdown Structures (WBS) 2. Work Package Specifications

4 ₄

Software Quality Assurance

1. Use a SQA process

2. Use engineering standards

Peer Reviews

1. Walkthroughs 2. Inspections

(46)

Software Project Control

-

_-

5 ₅

Verification and Validation

1. Quality 2. Quantity

Software Engineering Assessment

1. Validate organizational capability

(47)

Software Project Phases

(48)

Project Phases A.K.A.

(49)

Classic Mistakes

z Seductive Appeal z Types – People-Related – Process-Related – Product-Related – Technology-Related

(50)

People

-

_-

Related Mistakes

_{Related Mistakes}

z Undermined motivation z Weak personnel

z Requirements gold-plating

– Gilding the lily

z Feature creep

z Developer gold-plating

– Beware the pet project

z Push-me, pull-me negotiation z Research-oriented development

(57)

Technology

-

_-

Related Mistakes

_{Related Mistakes}

z Silver-bullet syndrome

z Overestimated savings from new tools and methods

– Fad warning

z Switching tools in mid-project

(58)

References

z ACM Conferences z ICSE

z SEI

z IEEE Computer Society Press z IEEE Computer

(59)

Standards

z IEEE 1058, Standards for SPM Planning z ACM

z CSA z ISO

z SEI’s CMM

(60)

Software

z PERT/Gantt/CPM Scheduling

z Work Breakdown Structure (WBS)

z COCOMO II Model Definition Manual z Sim SE

(61)

Homework

z Assignment 1

– Reading 56 pages – Thinking

– Writing one page

z Choose group partners