Top Banner
Project Management Project Management Fundamentals Fundamentals
62

Software Project Management

Nov 02, 2014

Download

Business

Samuel90

 
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Software Project Management

Project Management Project Management FundamentalsFundamentals

Page 2: Software Project Management

TodayToday

PMI FundamentalsProject OrganizationProject SelectionProject Portfolio ManagementProcurement ManagementStatement of Work (SOW)Project Charter

Page 3: Software Project Management

ReviewReview

Project and Program4 Project Dimensions

People, process, product, technology

Rapid Development StrategyAvoid classic mistakes, development fundamentals, risk management, schedule-oriented practices

Trade-off TriangleProcess. One size does not fit all.36 Classic Mistakes

Page 4: Software Project Management

TradeTrade--off Triangleoff Triangle

Know which of these are fixed & variable for every project

Page 5: Software Project Management

Project Phases A.K.A.Project Phases A.K.A.

Page 6: Software Project Management

Project Success RatesProject Success Rates

The 2001 Standish Group Report showed Decided Improvement in IT Project Success Rates from the 1995 report.– Time overruns: 63% compared to 222%– Cost overruns: 45% compared to 189%– Required features: 67% compared to 61%– 78,000 U.S. projects successful vs. 28,000– 28% of IT projects succeeded compared to 16%

Page 7: Software Project Management

Project Success Rates ..2Project Success Rates ..2

Why the Improvements?Average cost reduced by halfBetter tools for monitoring and controlMore skilled PM’s, more process, more user involvementAnd “The fact that there are processes is significant in itself.”

Page 8: Software Project Management

Why Do Projects Succeed?Why Do Projects Succeed?

How to identify a project’s success potential– What metrics could you look at?

Project sizeProject durationProject team sizePeople technical skillsPeople communication skills

Page 9: Software Project Management

Why Do Projects Succeed?Why Do Projects Succeed?– Executive support– User involvement– Experienced project manager– Clear business objectives– Focused scope– Standard software infrastructure– Firm basic requirements– Formal methodology– Reliable estimates

Standish Group “CHAOS 2001: A Recipe for Success”

Page 10: Software Project Management

Why Executive Support?Why Executive Support?

Top management can help to:– Secure adequate resources– Get approval for unique project needs in a

timely manner– Receive cooperation from people throughout

the organization– Provide leadership guidance

Page 11: Software Project Management

Stakeholder TriadStakeholder Triad

1. Function RepresentativeThe ‘business person’Or SME: Subject Matter Expert

2. Executive SponsorProject’s visionary & championAlso the ‘General’, ‘Fall Guy’, and ‘Minesweeper’Not the PM, ‘Santa Claus’, or the ‘Tech Guy’

3. Project ManagerThe ‘Linchpin’Must be ‘multi-lingual’

Page 12: Software Project Management

Define scope of projectIdentify stakeholders, decision-makers, and escalation proceduresDevelop detailed task list (work breakdown structures)Estimate time requirementsDevelop initial project management flow chartIdentify required resources and budget

Evaluate project requirementsIdentify and evaluate risks Prepare contingency planIdentify interdependenciesIdentify and track critical milestonesParticipate in project phase reviewSecure needed resourcesManage the change control processReport project status

15 PM Job Functions15 PM Job Functions

*Northwest Center for Emerging Technologies, "Building a Foundation for Tomorrow: Skills Standards for Information Technology,"Belleview, WA, 1999

Page 13: Software Project Management

PMBOKPMBOK

Structures PM by – A) Processes– B) Knowledge Areas

Processes. 2 types– 1. PM processes: describing and organizing the work of

the project– 2. Product-oriented processes: specifying and building

the project’s product

Page 14: Software Project Management

PMI FrameworkPMI Framework

Source: Project Management Institute

Page 15: Software Project Management

The 5 PMI Process GroupsThe 5 PMI Process Groups

1. Initiating2. Planning3. Executing4. Controlling5. ClosingNote: these can be repeated for each phaseEach process is described by:

InputsTools & TechniquesOutputs

Page 16: Software Project Management

PMI Process GroupsPMI Process Groups

Source: Project Management Institute

Page 17: Software Project Management

PMI: Process LinksPMI: Process Links

Page 18: Software Project Management

PMI Phase InteractionsPMI Phase Interactions

InitiatingProcesses

PlanningProcesses

ControllingProcesses

ExecutingProcesses

ClosingProcesses

Design Phase

InitiatingProcesses

PlanningProcesses

ControllingProcesses

ExecutingProcesses

ClosingProcesses

Implementation Phase

Page 19: Software Project Management

PMI: Initiating ProcessPMI: Initiating Process

Inputs– Product Description– Strategic plan– Project Selection

Criteria– Historical Information

Outputs– Project charter– Project Manager

assigned– Constraints– Assumptions

Page 20: Software Project Management

Devising and maintaining a workable scheme to accomplish the business need that the project was undertaken to address

PMI: Planning ProcessPMI: Planning Process

Scope PlanningScope DefinitionActivity DefinitionActivity SequencingActivity Duration EstimatingResource PlanningCost EstimatingCost Budgeting

Risk PlanningSchedule DevelopmentQuality PlanningCommunications PlanningOrganization PlanningStaff AcquisitionProcurement PlanningProject Plan Development

Page 21: Software Project Management

PMI: Executing ProcessPMI: Executing ProcessCoordinating people and other resources to carry out the plan

Project Plan ExecutionScope VerificationQuality AssuranceTeam Development

Information DistributionSolicitationSource SelectionContract Administration

Page 22: Software Project Management

PMI: Controlling ProcessPMI: Controlling ProcessEnsuring that project objectives are met by monitoring and measuring progress and taking corrective measures when necessary

Overall Change ControlScope Change ControlSchedule ControlCost ControlQuality Control

Performance ReportingRisk Response Control

Page 23: Software Project Management

PMI: Closing ProcessPMI: Closing ProcessFormalizing acceptance of the project or phase and bringing it to an orderly end

Administrative ClosureContract Close-out

Page 24: Software Project Management

PMI Knowledge AreasPMI Knowledge Areas

Page 25: Software Project Management

Importance of PhasesImportance of Phases

Define your management review points– “Phase exits” or “kill points”– Ensure continued alignment with goals– Form of Validation & Verification (V&V)

Page 26: Software Project Management

Understanding OrganizationsUnderstanding OrganizationsStructural frame:Focuses on roles and responsibilities, coordination and control. Organization charts help define this frame.

Human resources frame:Focuses on providing harmony between needs of the organization and needs of people.

Political frame:Assumes organizations are coalitions composed of varied individuals and interest groups. Conflict and power are key issues.

Symbolic frame: Focuses on symbols and meanings related to events. Culture is important.

Page 27: Software Project Management

Organizational StructuresOrganizational Structures

Functional– Engineering, Marketing, Design, and so on– Profit and Loss (P&L) from production

Project– Project A, Project B– Income from projects– PM has P&L responsibility

Page 28: Software Project Management

Organizational Structures ..2Organizational Structures ..2

Matrix– Functional and Project based– Program Management Model– Shorter cycles, need for rapid development

process

Page 29: Software Project Management

Functional OrganizationFunctional Organization

• Cons– “Walls”: can lack customer orientation– “Silos” create longer decisions cycles– Conflicts across functional areas– Project leaders have little power

• Pros– Clear definition of authority– Eliminates duplication– Encourages specialization– Clear career paths

Page 30: Software Project Management

Project OrganizationProject Organization

• Pros– Unity of command– Effective inter-project communication

• Cons– Duplication of facilities– Career path

• Examples: defense avionics, construction

Page 31: Software Project Management

Matrix OrganizationMatrix Organization

• Pros– Project integration across functional lines–Efficient use of resources–Retains functional teams

• Cons– Two bosses for personnel– Complexity– Resource & priority conflicts

Page 32: Software Project Management

Matrix FormsMatrix Forms

Weak, Strong, BalancedDegree of relative powerWeak: functional-centricStrong: project-centric

Page 33: Software Project Management

Organizational Structure Influences Organizational Structure Influences on Projectson Projects

Matrix Organization TypeProjectCharacteristics

Functional Weak Matrix BalancedMatrix

Strong Matrix Projectized

Project Manager'sAuthority

Little orNone

Limited Low toModerate

ModerateTo High

High toAlmost Total

Percent of PerformingOrganization'sPersonnel Assigned Full-time to Project Work

VirtuallyNone

0-25% 15-60% 50-95% 85-100%

Project Manager's Role Part-time Part-time Full-time Full-time Full-timeCommon Title forProject Manager's Role

ProjectCoordinator/Project Leader

ProjectCoordinator/Project Leader

ProjectManager/Project Officer

ProjectManager/Program Manager

ProjectManager/Program Manager

Project ManagementAdministrative Staff Part-time Part-time Part-time Full-time Full-time

PMBOK Guide, 2000, p. 19

Page 34: Software Project Management

Organizational ImpactOrganizational Impact

Form can greatly impact your roleDetermine what skills you’ll need from which functionsThe new “Project Office”– A) As centralized project management– B) As coach and info. office to project teams

The “Enterprise PMO” (EMPO)

Page 35: Software Project Management

Why Firms Invest in ITWhy Firms Invest in IT

Page 36: Software Project Management

IT Planning ProcessIT Planning Process

Page 37: Software Project Management

Methods for Selecting ProjectsMethods for Selecting ProjectsThere are usually (always?) more projects than available time and resources to implement them

Therefore: It is important to follow a logical process for selecting IT projects to work on

Methods include– Focusing on broad needs– Categorizing projects– Financial methods– Weighted scoring models

Page 38: Software Project Management

Broad Organizational NeedsBroad Organizational Needs

It is often difficult to provide strong justification for many IT projects, but everyone agrees they have a high value

“It is better to measure gold roughly than to count pennies precisely”

Three important criteria for projects:– There is a need for the project– There are funds available– There’s a strong will to make the project succeed

Page 39: Software Project Management

Categorizing IT ProjectsCategorizing IT ProjectsOne categorization: whether project addresses– a problem– an opportunity– a directive

Another: how long it will take & when it is neededAnother: overall priority of the project

Page 40: Software Project Management

Project Portfolio ManagementProject Portfolio ManagementPortfolio: a group of IT projects under a coordinated management structureDifferent ‘portfolio models’ are available:– Economic return model

– NPV, IRR, ROI

– Cost-benefit model– Can include less tangible factors

– Market research model– For new products

Each considers relative value and resource/budget interactions

Page 41: Software Project Management

Portfolio ManagementPortfolio Management

A 5 level approach (from CIO magazine)1. Create a Portfolio Database

Project names & descriptionsEstimated costs, timeframes, staffing

– BenefitsSpotting redundanciesCommunication across organizations & teamsHolistic view

Page 42: Software Project Management

Portfolio ManagementPortfolio Management

2. Prioritize Projects – Try quantifiable rankings

Risk and return

– Still subjectivity and disagreements3. Divide into budgets based on type– To align with business needs– Ex: utilities (‘keeping the lights on’),

incremental upgrades, strategic investments

Page 43: Software Project Management

Portfolio ManagementPortfolio Management

4. Automate the repository– Input of new data (new projects)– Automated tracking (PM software integration)

5. Apply modern portfolio theory– Ex: www.modporttheory.com– More advanced than most of us need

Page 44: Software Project Management

Procurement ManagementProcurement Management

Procurement means acquiring goods and/or services from an outside source– a.k.a. purchasing or outsourcing

Know how your project fits into this model– Are you building “in-house”? “for hire”?

Thus are you the ‘outside source’?

– As a startup? (thus in-house but as basis for the business itself)

Page 45: Software Project Management

Why Outsource?Why Outsource?

To reduce both fixed and recurrent costsTo allow the client organization to focus on its core businessTo access skills and technologiesTo provide flexibilityTo increase accountability

Page 46: Software Project Management

Procurement ManagementProcurement Management

Procurement planning: determining what to procure and whenSolicitation planning: documenting product requirements and identifying potential sourcesSolicitation: obtaining quotations, bids, offers, or proposals as appropriate

Page 47: Software Project Management

Procurement ManagementProcurement Management

Source selection: choosing from among potential vendorsContract administration: managing the relationship with the vendorContract close-out: completion and settlement of the contract

Page 48: Software Project Management

Project Procurement Management Project Procurement Management Processes and Key OutputsProcesses and Key Outputs

Page 49: Software Project Management

Procurement Tools & Procurement Tools & TechniquesTechniques

Make-or-buy analysis (build vs. buy)Determining whether a particular product or service should be made or performed inside the organization or purchased from someone else. Often involves financial analysis

ExpertsBoth internal and external, can provide valuable inputs in procurement decisions

Page 50: Software Project Management

Types of ContractsTypes of ContractsFixed price or lump sum: involve a fixed total price for a well-defined product or serviceCost reimbursable: involve payment to the seller for direct and indirect costsTime and material contracts: hybrid of both fixed price and cost reimbursable, often used by consultantsUnit price contracts: require the buyer to pay the seller a predetermined amount per unit of service

Page 51: Software Project Management

Cost Reimbursable ContractsCost Reimbursable ContractsCost plus incentive fee (CPIF)– Buyer pays seller for allowable performance costs plus a

predetermined fee and an incentive bonusCost plus fixed fee (CPFF)– Buyer pays seller for allowable performance costs plus a

fixed fee payment usually based on a percentage of estimated costs

Cost plus percentage of costs (CPPC)– Buyer pays seller for allowable performance costs plus a

predetermined percentage based on total costs

Page 52: Software Project Management

Contract Types Versus RiskContract Types Versus Risk

Page 53: Software Project Management

Statement of Work (SOW)Statement of Work (SOW)A description of the work required for the projectSets the “boundary conditions”SOW vs. CSOW (Contract SOW)– Latter: uses legal language as part of a

competitive bidding scenarioCan be used in the final contract – be careful, be specific, be clear

Page 54: Software Project Management

SOW ContinuedSOW Continued

Typically done after approval (after “Go”)Can be multiple versions– 1. List of deliverables for an RFP– 2. More detailed within final RFP– 3. Binding version from contract

Page 55: Software Project Management

SOW TemplateSOW TemplateI. Scope of Work: Describe the work to be done to detail. Specify the hardware and

software involved and the exact nature of the work.

II. Location of Work: Describe where the work must be performed. Specify the location of hardware and software and where the people must perform the work

III. Period of Performance: Specify when the work is expected to start and end, working hours, number of hours that can be billed per week, where the work must be performed, and related schedule information. Optional “Compensation” section.

IV. Deliverables Schedule: List specific deliverables, describe them in detail, and specify when they are due.

V. Applicable Standards: Specify any company or industry-specific standards that are relevant to performing the work. Often an Assumptions section as well.

VI. Acceptance Criteria: Describe how the buyer organization will determine if the work is acceptable.

VII. Special Requirements: Specify any special requirements such as hardware or software certifications, minimum degree or experience level of personnel, travel requirements, documentation, testing, support, and so on.

Page 56: Software Project Management

Project CharterProject Charter

A high-level project description:– Business need, product, assumptions

Often precedes SOWOften 2-4 pages (can be longer)

Page 57: Software Project Management

Project Charter OutlineProject Charter Outline

Overview– Business need– Objectives– Method or approach

General scope of workRough schedule & budgetRoles & responsibilitiesAssumptions

Page 58: Software Project Management

Project Charter ExamplesProject Charter ExamplesAssumptions– We will reuse architecture from the old ordering system– Customer will provide business experts as needed– System will use existing networking resources – Customer will sign-off on interim deliverables within

one week of each delivery– All import data will be available in XML format– This will be a web-based application– We will partner with an overseas development firm to

create the security systems

Page 59: Software Project Management

Project Charter Examples ..2Project Charter Examples ..2

Primary Stakeholders (from various projects)– Sponsor: VP of Marketing– Sponsor: Five Star Brokerage Consortium– Sponsor: Bill Smith, CEO– Users: Call center operators– Users: Our partner banks– Customers: Attorneys from small-to-mid size law firms– Customers: Males 30-45 earning $75K or more

Page 60: Software Project Management

Project Charter Examples ..3Project Charter Examples ..3Deliverables– Retail Web Site

– Full catalog– Shopping-cart system– Search engine– User registration system

– Trading System– Equities order entry system– Portfolio management– Order execution engine– Integration with X legacy systems– Security infrastructure

Page 61: Software Project Management

Project Charter Examples ..4Project Charter Examples ..4

Deliverables– Corporate Application

Network and hardwareWeb-based HR portalConnectivity for VPN“Asset Management Viewport” applicationCustomized Reporting Engine

– Allowing users to Perseus data mart– Delivery into HTML and Excel

User manuals

Page 62: Software Project Management

Project Charter Examples ..5Project Charter Examples ..5Out of Scope– News feeds - Dynamic pricing– Auction engine - EDI support– Legacy integration - Help system

Schedule– We anticipate a 12-14 month development timeframe– The project is expected to start in Q1 2004 and

complete in Q3 2005– The initial release is expect within 10 months with the

follow-on delivery within 4-6 months