Maksym Bardega Global Logic Being PM 2014

Зарегистрируйтесь, чтобы просмотреть полный документ!

Maksym Bardega. Global. Logic Being PM © 2014 Global. Logic Inc

Agenda 01 PM image 02 PM responsibilities (PMBOK meaning) 03 ‘Must have’ knowledge for PM 04 How to become PM 05 Some behavior paradigms 06 Difference between Team Lead and PM © 2014 Global. Logic Inc.

Being PM PM image • • • Diplomatic Expert ‘Fifth wheel’ Knows everything Knows nothing Always busy Does nothing Team player Persuades only his interests © 2014 Global. Logic Inc. • • • 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

Being PM PM responsibilities (PMBOK meaning) Responsibilities − − Initiating • define a new project 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. − − − © 2014 Global. Logic Inc. 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

Being PM ‘Must have’ knowledge for PM • SDLC • Management basics • Team management • Conflictology • Time management basics • Domain expertise • Risk management • Economics • At least one business process modeling notation (BPMN, UML etc. ) • English • Orator skills • Business etiquette © 2014 Global. Logic Inc. • 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

Being PM How to become PM Trainee Junior Developer Middle Developer Senior Developer Business

Being PM Some behavior paradigms Always ask ‘Why? ’ Plan and prioritize your tasks − − − Don’t start doing 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 − − Raise ‘red flag’ as soon as possible − − − 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. ) © 2014 Global. Logic Inc. 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 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

Being PM Difference between Lead and PM So what is 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 © 2014 Global. Logic Inc.

Thank you Maksym Bardega Project Manager 38. 050. 567. 3798 Skype: m. bardega maksym.

Скачать презентацию Maksym Bardega Global Logic Being PM 2014

3.Максим Бардега_Being PM.pptx

Количество слайдов: 9