EXECUTIVE UPDATE

<Client / Date>

Agenda

<Project / Program> Health Summary

Change Management
<Project / Program> Costs
Project Roadmap
Quality Reporting
Risk Assessment
Issues
Questions

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 2

Project Health Summary <If client only has one project, use this
slide.>
Area

Status

Overall
Status

Green

<This is the status of the overall delivery including all screens and all functionality
that is in the current scope for overall delivery>

Green

<Changes to scope should be included here and change controls included in a later
slide in detail>

Green

<Status for all screens/feature functionality delivered per the plan and any changes
to the schedule included here>

Scope
Schedule

Costs
Resources

Quality
Key Risks

Green

Amber
Green
Red

Trend

Comments

<Payments to date and upcoming payments including total spend to date against
the SOW amount, also include $ where change controls have been approved>
<Highlight any changes to staffing plan where there are changes from what was
included in the SOW or staffing constraints because of other priorities>
<Highlight key comments here. Quality dashboard are included in a later slide>
<Highlight key risks here that impact the overall delivery and details with
mitigation plan included in a later slide>

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 3

Program Health Summary

Project
Name

Project
A
Project
B
Project
C
Project
D
Project
E

<If client has more than one project, use this slide.>

Health
Schedul Scope
e
Green
Green
Green

Green
Red
Green

Resourc
e
Green
Green
Amber

Costs

Green
Green
Green

Qualit
y
Green
Green
Green

Overal Release
l
Date
Green

3/31/201
5

If status yellow or red

explain issue and steps
needed to get to green

Green

3/31/201
5

Scope red because.

Green

3/31/201
5

Resource amber
because

Green

Green

Green

Green

Green

Green

Green

Green

Green

Green

Green

Green

COMPANY CONFIDENTIAL

Comment(s)

3/31/201
5
3/31/201
5

All Rights Reserved 2015 iPipeline | 4

<Project

Name> Change Management

Impact
Description

ID

Priority

Phase

Sample 1 - Add new drop down

field to support x

<use JIRA id>

High

1
(Family Term,
Business Term,
CI)

Sample 2 - Add new value to an

existing drop down

<use JIRA id>

Low

2
(Whole Life,
Universal Life)

COMPANY CONFIDENTIAL

Status
Cost

Effort

Yes
$$$ CDN

Yes
# of days

Approved for delivery

etc

etc

Pending Approval from <Client

Name>

All Rights Reserved 2015 iPipeline | 5

<Project/Program

Name> Costs

Date

Sprint(s)

Amount

Paid

Invoice #

<Invoice MMYY>

$100,000

Paid

xxxxxx

2, 3

$80,000

Invoiced

xxxxxxx

Not Paid
4
X
X
X
X
X
X
X

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 6

<Project / Program> Roadmap

<Insert Project or Program Roadmap Diagram>

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 7

Quality Reporting

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 8

Quality Reporting

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 9

Quality Reporting

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 10

Quality Reporting

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 11

Risk Assessment
Risk

Details

Impact

Date

Risk Integration
points

Need WebService functionality

to be ready to go in designated
sprints

Could impact
October timeline

08/15/2015

Risk Translations

Could impact
ability to deliver
Foreign Language
version of iGO in
October

06/21/2015

Need full Language

translations in designated
sprints

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 12

Issues
Issue

Owner

Issue-

<Persons Name>

Issue-

<Persons Name>

Details

<Description of issue>

<Description of Issue>

COMPANY CONFIDENTIAL

Expected
Resolution
Date

<8/19/2015>

<10/10/2015>

All Rights Reserved 2015 iPipeline | 13

Questions

COMPANY CONFIDENTIAL

All Rights Reserved 2015 iPipeline | 14

Presentation Best Practices

Know the audience!

Check the slides for errors and/or changes prior to presentation.
If you dont plan on using a slide, take it out of the presentation.
Prior to presentation determine who will be presenting which slides.
Prior to presentation make sure all presenters are in agreement about the
course of the presentation.
Allow all presenters, who wish to speak, to do so.
Make sure the slides provide adequate detail, without large blocks of text.

All Rights Reserved 2015 iPipeline | 15