Tiago Palhoto European Commission

Tiago.palhoto@ext.ec.europa.eu

Agile PM² Connecting Agile Practices

to PM² projects

First things first…

Tiago Palhoto 2

Thank you!!

Tiago Palhoto 3

Alexandra Michotte Anita Varotto Nicos Kourounakis

Agenda

Tiago Palhoto 4

• Overview

• Values and Principles

• Agile PM² within the Organisation

• Project Lifecycle

• Project organisation – Governance Model

• Roles and Responsibilities

• Artefacts

Overview

Tiago Palhoto 5

Overview

Tiago Palhoto 6

• Agile PM² enables and supports the use of Agile practices in projects of the European Commission;

• Complies with the various IT Governance, Enterprise Architecture and Interoperability requirements.

Values & Principles

Roles & Responsabilities

Guidelines

Tools & Techniques Artefacts

Themes Agile PM²

Model

Values and Principles

Tiago Palhoto 7

Values

Tiago Palhoto 8

The Agile Manifesto provides a foundation for Agile PM², which is adapted to reflect the EC values and the experience from the past years of experience.

• Individuals and interactions over processes and tools;

• Working over comprehensive documentation;

• collaboration over contract negotiation;

• Responding to change over following a plan

solutions

Stakeholder

Principles

Tiago Palhoto 9

Just like for the Values, the Principles supporting Agile PM² have been adapted from the ones described in the Agile Manifesto:

• Deliver Value frequently through working ;

Solutions

• The primary measure of progress is the usefulness of what has been delivered;

Agile PM² within EC

Tiago Palhoto 10

Open PM² with an Agile approach

Agile and PM²

Tiago Palhoto 11

Values & Principles

Roles & Responsibilities

Guidelines

Tools & Techniques Artefacts

Themes Agile PM² Model

Artefacts (IT Governance)

Roles & Responsibilities (IT Governance)

IT G

ove

rnan

ce

Decisions Communications Policies Audits

SW ENGINEERING

PRACTICES

Delivery and Engineering Practices

Agile Management Practices

Project Management Practices

Positioning of Agile PM²

Tiago Palhoto 12

ENTERPRISE PRACTICES

Enterprise (and other) Practices

Project Lifecycle

Tiago Palhoto 13

Project Phases

Tiago Palhoto 14

Time

Effo

rt

Initiating Planning Executing Closing

Monitor & Control

From Project phases to Daily Cycles

Tiago Palhoto 15

Implement

Review

Coordinate

Daily Cycles

Iterations

Releases

Project Phases

Tiago Palhoto 16

Time

Effo

rt

Initiating Planning Executing Closing

Monitor & Control

Time

Effo

rt

Initiating Planning Executing Closing

Monitor & Control

Exposing and Delivering Work

Tiago Palhoto 17

ATeM

Exposure of Work Items

ATeM

Product Owner

Stakeholders

Exposure end of Iteration

Release Users / Customers

Product Owner

Project Organisation

Tiago Palhoto 18

Governance Model Business Governing Layer

Steering Layer

Directing Layer

Managing Layer

Performing Layer

Requestor side Provider side

Appropriate Governance Body (AGB)

Project Steering Committee (PSC)

(PO, SP, BM, PM)

Business Manager (BM)

Project Owner (PO)

Solution Provider (SP)

Project Manager (PM)

Collaboration &

Communication

Business Implementation Group (BIG)

(User & Business Representatives)

Project Core Team (PCT)

Pro

ject

Su

pp

ort

Team

(P

ST

)

Agile PCT (A-PCT)

Architecture Owner (ArOw)

Agile Team Member (ATeM)

Team Coordinator (TeCo)

Product Owner (PrOw)

Governance

Advises & Decides

Operational

Supports (optional)

Some decision power

Acts

Project Team

Agile PM² Roles

Tiago Palhoto 20

• PrOw – The ‘single voice of the stakeholders’ within the Agile Project Core Team. Should work, if possible, within the physical space of the team;

• TeCo - Facilitator and team coach whose main purpose is to allow the team to focus on achieving specific objectives and being successful. Synchronises with the PM;

• ArOw - Responsible for the architecture decisions for the Agile Project Core Team (A-PCT). Leads the initial architecture envisioning effort at the beginning of the project and ensures alignment with the guidelines and recommendations of the Architecture Office (AO);

• ATeM – Implements the solution. Has a set of skills that, put together with all the other ATeM, allows the team to deliver a solution.

Artefacts

Tiago Palhoto 21

Artefacts

Tiago Palhoto 22

Agile PM² groups the relevant artefacts in three different groups: • IT Governance – These artefacts provide information

requested by the Organisation IT Governance; • Agile Specific – Capture information regarding the

planning of specific processes, activities, releases, iterations and other milestones;

• Coordination & Reporting – Capture information needed to coordinate the overall project activities with those undertaken by the A-PCT.

Artefacts Landscape

Tiago Palhoto 23

Project-End

Report

Project Initiation

Request

Business Case

Project Charter

Closing Initiating

Business

Implementation

Plan

Transition Plan

Project

Handbook

Project

Stakeholder Matrix

P r o je c t

W or kP la n

MANAGEMENT

PLANS PROJECT REPORTS

Quality Review

Report

Project Status

Report

Project Progress

Report

CHECKLISTS

Change

Request Form

MoMs

Meetings

Agendas

Planning Executing

Monitor & Control

MEETING DOCS

Architecture

Overview

PROJECT LOGS

Operational

Model

Development

Work Plan Development

Status Report

AGILE PM² LOGS

Acceptance

Plan

Testing Log

Retrospectives Log

Test Plan

Deployment

Plan

Development

Handbook

Project Handbook Project Work Plan

Transition Plan Acceptance Plan

Project Status Report IT Governance

Re so u r ce

P l a n

Thank you!

Tiago Palhoto 24