Галина Шакірова "Performance Review Process Development at Dev-Pro." Lviv Project Management Day 2017
1. Galina Shakirova
6+ years experience in IT
Experience in Recruitment, HR, Operations, Training and Process
Management
SPEAKER:
Performance Review Process Development
at Dev-Pro.net
(Chief Process Officer)
3. jobs@dev-pro.net
Dnipro
October 2017,
up to 20 people.
«Towers»,
Dzherzhynskogo 35B
Kyiv
November 2017,
up to 37 people.
«MERKS-2»,
Lejptsygskaya 15
Lviv
December 2017,
up to 50 people.
«Optima Plaza»,
Naukova 7D
4. 1
less than 20-30 people
Stage 1
No formal procedure. Small family company.
Immediate feedback sharing.
5. less than 20-30 people
July 2011
Stage 2
Less direct communication. Not regular
feedback.
The first formal performance review meetings
(Top Managers involved, no HR, standard
feedback form for contractor).
2
8. 50-70 people
2012
Stage 3
Need to offload routine tasks from top
management (summary, coordination of action
steps after PR).
Adding HR (one person) to handle PRs to
offload Top Management's time.
3
10. 70-150 people
August 2013
Stage 4
Several HRs involved. Top Management can't
attend all the PRs. Subjective feedbacks.
Written policy. Introduction of summary
templates. Organized data storage.
4
15. ~200 people
2014
Stage 6
Client has no formal influence on the
performance review and seniority raises.
Feedback from client introduced (simplified
evaluation form).
6
18. ~200 people
Beginning of 2015
7
2016
8
Stage 7
No formal feedback from the team to PM.
270 degree Performance Review Process for
PMs.
Stage 8
Still no need in 270 degree evaluation for
everyone. Need a way to take BA and QA
feedback on Devs into account.
Adding sections to developers evaluation from
BAs and QAs part.
20. 220 people
Beginning of 2017
Stage 9
Contractor's English is evaluated by Recruiter/
PM at the interview. Subjective results.
English testing by 3rd party provider before
performance review.
9
22. 300+
now
Stage 10
New challange: 4 development centers instead
of one, distributed teams
* Process adaptation to the reality of
distributed teams
* Formal career paths introduction
10