PPM & Projects

Portfolio Management

Managing the portfolio of IT projects.

Example: Conducting a portfolio review to prioritize projects.
Risk: Poor portfolio management can lead to resource misallocation.
Opportunity: Optimize project selection and prioritization.
Benefit: Ensures resources are focused on high-value projects.

Project Management

Classic (or Waterfall) project management is a linear and sequential approach where each phase must be completed before the next begins.
Example: Developing a software application where requirements are fully defined before any coding begins.
Risk: Inflexibility to changes can lead to project delays and increased costs.
Opportunity: Clear structure and documentation can improve project tracking and accountability.
Benefit: Clear milestones; predictable scope & timelines for resourcing plan.

Agile Project Management

An iterative approach to managing software development projects that focuses on continuous releases and incorporating customer feedback with every iteration.
Example: Using Scrum methodology to manage software development sprints.
Risk: High number of policy questions and fast-changing technology space can lead to project resourcing fluctuations.
Opportunity: Agile allows for rapid adaptation to changing requirements and market conditions.
Benefit: Improved project flexibility and faster delivery of value to customers.

Requirements Gathering

Collecting and documenting project requirements.
Example: Conducting stakeholder workshops to gather requirements.
Risk: Inadequate requirements can lead to project scope issues.
Opportunity: Ensure clear and accurate project requirements.
Benefit: Improves project outcomes and stakeholder satisfaction.

QA Testing

QA Testing (Quality Assurance Testing) involves the systematic process of ensuring that software meets specified requirements and is free of defects.
Example: Conducting automated regression tests to ensure new code changes do not introduce bugs.
Risk: Inadequate testing can lead to undetected defects and system failures.
Opportunity: Comprehensive QA testing can improve software reliability and user satisfaction.
Benefit: Higher quality software products that meet user expectations and reduce maintenance costs.

Org Change Management

Managing the impact of IT projects on the organization.
Example: Developing a change management plan for a major IT project.
Risk: Poor change management can lead to resistance and project failure.
Opportunity: Manage the impact of changes on the organization effectively.
Benefit: Ensures smooth transitions and user adoption.

PM Methodology

The structured approach and set of practices used to guide the planning, execution, and completion of projects.
Example: Using the Waterfall methodology for a construction project.
Risk: Rigid methodologies may not adapt well to changes, leading to project delays.
Opportunity: Methodologies provide a clear framework and guidelines, improving project consistency.
Benefit: Enhanced project control and predictability.