Maksym Bardega. GlobalLogic Being PM © 2014 GlobalLogic Inc

become PM
Some behavior paradigms
Difference between Team Lead and PM

01
02
03
04
05
06



©2014 GlobalLogic

Inc.

Agenda

player
Persuades only his interests
Man with 100 new e-mails a day
Always

absent on his workplace
Master of salaries
Has a huge salary
Mommy of the team
Highly organized
Persuades to do unnecessary work
Communicative
Rational

or a new phase of an existing project by obtaining

authorization to start the project or phase
Planning
create project plan
define scope of the project
Estimate resources
Estimate costs
Plan communications
Identify risks
Analyze risks
Plan purchases
Etc.

Responsibilities

Executing
Controlling and managing project
Providing acceptable quality
Staffing
Team development
Etc.
Monitoring and controlling
Scope management
Time management
Quality control
Team management
Reporting
Risk management
Etc.
Closing
Formal closing of the project

management basics
Domain expertise
Risk management
Economics
At least one business process

modeling notation (BPMN, UML etc.)
English
Orator skills
Business etiquette

PMBOK basics
Motivation basics
How to delegate
Courage to make complex decisions
How to conduct interview
How to evaluate subordinates
Ability to provide information in short and clear manner
Soft skills

anything before asking ‘Why?’
Try to understand route cause of client’s

or team member’s demand
Don’t hesitate to ask ‘Why should we do this?’
Don’t try to imagine route cause by yourself – this may lead to unnecessary/wrong actions from you

Don’t run away from problems

Problem won’t be solved by magic
Small problem without solution will lead to a bigger one
Earlier you start working on problem, less efforts you need to solve it

Plan and prioritize your tasks

Don’t try to remember everything – just schedule a task in your calendar
Prioritization will save you a lot of time
Learn how to work with your e-mail effectively

Don’t write – have a call

Save your time
Voice communication is much more effective than e-mail
Write after the call (meeting minutes, action items list etc.)

Raise ‘red flag’ as soon as possible

Identify severity and priority of the problem
Try to solve problem by yourself
If you understand that you can’t solve problem by yourself or you need a lot of time to do this, immediately inform your ED/SPM
Inform client about problem as soon as possible
Don’t hesitate to ask for assistance from anyone who can help you
Provide regular updates to all participants of problem
Motivate your team to do the same in similar situations

the difference?
PM should have more strategic level of thinking
PM has

to take care of all project areas (not just quality of delivery)
PM is completely responsible for the whole account (not just a single delivery project)
Price of the PM’s mistake is higher
PM has to make more complex decisions
PM acts as a ‘face’ of Company before client
PM codes less but manages more
PM has to manage ‘team’s mood’ (conflicts, motivation, stimulation etc.)
PM has a lot of new responsibilities compare to TL
PM has to do more communications
PM has more unexpected tasks
PM is ‘outside’ the development/QA team
PM has to make ‘unpopular’ decisions