PMBOK® Extension

for Software projects

Danil Dintsis

25 years experience in IT & consulting services

Ph. D. in System Analysis, PMP, ITIL, OSA, MOF, Cloud Computing certified specialist

consult@dintsis.org

Sources

• PMBOK® Guide 5 Edition

• ISO/IEC/IEEE Standards 12207, 15288, 16326

• IEEE Standards (SWEBOK® v. 2-3, Templates for Management Plans)

• ITIL®

• COBIT®

PMBOK® Extension for Software Projects. Sources

Target audience

• Business leaders

• Business managers

• Operation and functional managers

• PMO

• Development team members

• Support team members (ITIL)

Software projects «species»

Team Management

• Dedicated resources

• Multi-skilled teams

• Colocation (war room)

• Generalists and Specialists

• Stable Work Environment

Types of Teams

• Combined virtual and localized teams

• Combined teams with both expensive experts and «generalists»

• Balance between dedicated and functional team mambers

PM roles and responsibilities

Leadership

Control

Building partnership

Team building

Additional team management tools

• Pair programming

• Test-driven programming

• Colocation

Project stages (phases)

• Analyze (requirements)

• Architect

• Design

• Construct

• Integrate

• Test

Common to Agile approach

Business demands

Analyze

Architect

Develop • Code

Document

Test

Sustain

© PMBOK® Extension for Software Projects

WBS additional tools

Additional Inputs, Tools, and Outputs

• SLA

• Release and Deployment Plans

• Security Constraints

• Architectural and other

• Non-functional dependencies

• Retrospective analyze

• Use cases

Adaptive models

• Increment planning wit a period from 1 day to 1 month

• Customer and users involvement on a regular basis

• Small, self-organized teams up to 10 members.

• Large projects may include small adaptive teams

• Each team member works in the single project only durint current iteration

• Each team includes both generalists and specialists.

© PMBOK® Extension for Software Projects

Adaptive cycles

Time Management Tools

• Structured schedule

• Schedule as an independent variable

• Iterative schedule with come backs

• Schedule on demand

• Portfolio based schedule

Additional inputs, tools, and outputs for Time Management

• Release and Iteration plans

• Information radiators

• Current productivity

• Historical productivity

• On-line collaboration tools

Cumulative (CFD) Diagrams

© PMBOK® Extension for Software Projects

Scrum board as an information radiator

Quality Assurance – based on the IEEE standards

• 929 Software and System Test Documentation

• 1008- Unit Testing

• 1012- System and Software Validation and Verification

Quality metrics for customers and users

• Availability

• Productivity

• Security

• Scalability

• Simple to learn

• Simple to use

• Agility

Quality metrics for development and operation staff

• Availability

• Productivity

• Security

• Scalability

• Double code use

• Serviceability

• Deployment and portability

• Extensibility

Agile Risk Management Cycle

© PMBOK® Extension for Software Projects

SummarySoftware extension:

• Is more detailed and practical oriented

• Extends by Adaptive/Agile/Scrum approaches

• Implements ITIL based IT service lifecycle, tools, and techniques

• Imlements IEEE® SWEBOK standard

My Services

• PM consulting

• ITSM – ITIL – MOF consulting

• IT processes and staff audit

• Designing policies, procedures, templates

Q&As

Contacts

• consult@dintsis.org

• www.ddintsis.com (Russian)

• https://www.facebook.com/IPDanilDintsis

• http://www.linkedin.com/in/dintsis (English)