com
Application of methods
to project management
at Severnaya Kazna
insurance company.
An overview
Ekaterina Ekhlakova
Severnaya Kazna insurance company
Yekaterinburg, Russia
October 2013
Ekaterina Ekhlakova
CEO Advisor, Chief Project Management Officer
Insurance Company Severnaya Kazna
(Yekaterinburg, Russia).
Ekaterina possesses seven years of Project
Management experience.
Her portfolio includes implemented projects
in various areas: telecommunications, IT,
finance services and insurance.
phone: +7(800)700-13-30
mobile: +7(965)548-00-55
e-mail:
ekhlakovaes@kazna.com
facebook.com/ekaterina.yekhlakova
8 th International TOCPA Conference
Company Info
Insurance company of a federal level
80 cities of presence
1 850 employees and outsourced agents
Income:
2010: 768 million RUB
2011: 1 812 million RUB
2012: 2 582 million RUB
Project Management
before Introduction
66% of projects were test sales of new insurance
products
Projects either did not have plans at all,
or only final deadlines were planned
Project control was performed weekly
or at similar intervals
Company top managers were not provided
with structured information about running projects
In 2011 only 7 projects were started,
and just one in the first half of 2012
8 th International TOCPA Conference
Project Lifecycle
Initiation
Planning
Execution
Post-project
supervision
Project Initiation
Before TOC
A clear and unambiguous goal is not defined
for ~40% of projects
Project Initiation
Difficulties
People do not understand well the concept of project
People do not easily accept the throughput scheme
Emotions
Project Initiation
Achieved Improvements
Clear understanding of conditions for project initiation
Decision making is accelerated: from several days
to several hours
86% of projects have measurable goals defined
DO THEN THINK is NOT our motto anymore.
UDE, obstacles and revenues are calculated before startup
Some projects that had been deemed unprofitable
by traditional evaluation were revised and are in effect now
Projects lacking project features were downgraded
to routine activities
8 th International TOCPA Conference
Project Planning
Before TOC
A Plan is simply a task list constructed by a PM, or even just
jotted down ideas of a workgroup
No plan control system exists
Tasks of the plan are not linked by results, only by temporal
order
Several tasks of the same resource have the same finish term
Planned finish term is assigned based upon evaluation
of resource utilization
Maximum resource over-utilization reached is sevenfold
Project plans are prepared with no rules or standards
8 th International TOCPA Conference
Project Planning
What Was Implemented
Running projects are gradually replanned using CCPM
Planning Standard is introduced:
1) Project flowchart construction is mandatory
2) Project plans are to be created using CCPulse (MS Project)
3) All participants and PMO are involved in planning
Project Planning
Difficulties
People do not understand:
-
Project Planning
How We Managed To Deal With It
Separate time intervals are planned for people to evaluate
durations of tasks
Resource over-utilization in the case of task concurrency
is demonstrated
Several meetings were carried out in order to make managers
and participants understand backward planning concept and
task interference
Project Planning
Achieved Improvements
Quality of project plans increased dramatically
Time spent on planning increased threefold
The following needs are understood:
1) A thoroughly worked out plan is required for project startup
2) A project plan is a chain of interlinked tasks that leads to the goal
3) The plan is fixed after startup. If the correction is inevitable, the project
should be stopped, replanned and started over as a new one.
Project Execution
Before TOC
Project Manager chooses the means and schedule of project
control freely
Tasks are delayed with little reason. Project finish dates are
delayed repeatedly
What Was Implemented
Everybody must obey the rule:
Project control is performed daily
Project initiation directives define:
- PMO and project manager are in charge of daily buffer status
monitoring;
- Project participants are in charge of daily reporting on task progress.
8 th International TOCPA Conference
Project Execution
Difficulties
Evaluation of time required to finish a task
Getting feedback from participants
Project Execution
How We Managed To Deal With It
PMO requests PM reports daily (and were going to switch
to weekly reporting)
Project Management Guidelines are made effective that
define roles of participants, their rights and responsibilities
Personal interviews with every project and resource manager
were carried out in order to rationalize the rigidness of the
plan, and why project tasks are not overtime
PMO insists on daily reporting and rigidness of project plans
Task results can be controlled any time
Task status reports are collected via e-mail
Project Execution
Achieved Improvements
Project needs and problems surface early. Corrective actions
can be made in due time
Project delay reduced dramatically:
- Pre-PMO maximum delay was 18 weeks
- After creation of PMO and introduction of CCPM its 3 weeks
We now understand:
- Result AND term AND budget are all important for a task
- Task interconnection, and the common goal
Project Management
after TOC Introduction
Project hierarchy is maintained
Top managers are provided with project status information
weekly
Project activity is promoted to a higher priority:
- Projects are initiated to reach the most important goals
- Requests for new projects not only come from top managers, but also
from other employees
One of the Companys directors once sent me an e-mail:
its so cool you are controlling [me] and requesting [information]. Though I think I
am responsible, but the routine job [distracts me], and I feel uncomfortable when I do
not process [your requests], and the work thus progresses.