SOFTWARE PROJECT MANAGEMENT

RUSTOM D. CLEMENTE

TO THINK ABOUT....

Why are checklists important?

MANAGING THE SOFTWARE PROJECT

The Team Managing the team Managing the client-consultant relationship Communicating with the team and the client: the PSD

ROLES

MANAGING A SOFTWARE PROJECT

Basic Concepts:

Process: A methodological series of steps taken to

achieve a goal.

Roles: The responsibilities of each member of a project

team, and the interfaces between these team members

Critical roles must be filled at all times to ensure project progresses successfully

Role of Project Manager is probably the most crucial one, but all roles are important in terms of achieving delivery

MANAGING A SOFTWARE PROJECT

Team and skills:

A number of people work together on a typical Software Project

A broad set of skills required relative to traditional software projects, eg:

Graphic Design (Images, interactive elements) Web Development (HTML, jscript , PHP , etc) Software Development (eg Java, Perl) Business Analysis (Requirements) Training

Client/Account Management

MANAGING A SOFTWARE PROJECT

Team:

A Software Project Manager must:

Follow a process Innovate Empower a team Communicate

Development teams should:

Be as small as possible (to get the job done!)

TO THINK ABOUT...

What types of differences would you expect between a graphic designer and a programmer?

Between a programmer and a manager?

WHAT DOES THE CLIENT WANT?

Suddenly, a heated exchange took place between the king and the moat contractor

MANAGING AN SOFTWARE PROJECT

The Client-Consultant Relationship:

The dynamics of interpersonal interaction

Phases in the C-C Relationship:

Approaching the client

EOI or RFT Capability Statement or Company Overview Building networks, contacts and case studies

MANAGING SOFTWARE PROJECT

The Client-Consultant Relationship (contd): Phases (contd) Building the client-consultant relationship
Discovery Requirements

Analysis Solution Definition Project Proposal

MANAGING A SOFTWARE PROJECT

The Client-Consultant Relationship (contd): CCR Success Factors: Commitment (to journey, to project) Trust Inspiration Responsibility Education Working Practices And I would add one more: Proven ability to deliver!

MANAGING SOFTWARE PROJECT

Requirements Analysis:

Business requirements Technical requirements User requirements

MANAGING SOFTWARE PROJECT

Defining the Solution:

Involves input from;

Strategists: market research, customer needs analysis, risk/SWOT analysis, ROI and economic analysis Creatives: branding, look and feel, usability, editorial style Engineers/Technologists: hosting solution, technical architecture, software platform, implementation plan; and security, backup and scalability analysis. Project Manager: how, when, where etc, QA plan.

SELLING THE SOLUTION

PROJECT SPECIFICATION DOCUMENT

Often the PSD includes: 1. Version control 2. Introduction and Project Objectives 3. Project Description 4. Total Cost of Ownership for Infrastructure 5. Actors and Use Case 6. Site Map. Content Plan 7. Testing Plan, site updates and maintenance 8. Budget 9. Appendices

PROJECT RISKS
Privacy Copyright Infringement Licensing changes Legal liabilities (project dependent) Lack of human resources - skills Lack of funding

Changes in the marketplace Entry barriers for competitors Changes in prices...