1. Vadym Radchenko September, 2014 WANT TO BE A PROJECT MANAGER? ASK ME HOW! * Badge and slogan could be similar to Herbalife International, Inc. It is used just for educational purposes. No commercial goals are aimed. If you believe it violates any copyrights, please let me know immediately, and it will be removed.

2. Agenda ▪ How I selected the subject… ▪ F.A.Q. ▪ Popular myths ▪ Technical PM vs. non-technical ▪ Examples & Tips ▪ Conclusion

3. How I selected the subject…

4. Frequently Asked Questions I’m an IT Engineer (TL, Architect, QA, etc.) and want to be a PM. What should I do? Does it worth to change a direction?

5. Frequently Asked Questions I’m a non-IT manager, but IT is cool. I want to join it and manage IT Team.

6. Frequently Asked Questions I work in IT but not involved into the project activities directly: System Administrator, Recruiter, HR, Office Manager, Security, etc. I want to be a PM!

7. Myth - PM has bigger salary Yes, it is bigger: ▪ Yes: Senior PM > TL ▪ Yes: PM > HR No, it is lower: ▪ No: PM < TL ▪ No: IT PM ≤ non-IT PM

8. Myth - PM has nothing to do ▪ Doesn’t produce code ▪ Doesn’t answer immediately ▪ Doesn’t sit all time in the room ▪ Just talks a lot via phone ▪ Etc.

9. Myth - PM has a lot of free time

10. Myth - PM always has an interesting job which is not boring and monotonous

11. Myth - PMs are not needed at all

12. Types of PMs - Examples ▪ PM – as Proxy. Translates client needs to the team and vice versa ▪ PM – as People manager for the team ▪ PM – as a Scrum Master ▪ PM – Manages the project itself – (Budget, Scope, Schedule) * Items above could be combined in different variations

13. Technical PM vs. Non-Technical ▪ Has technical background ▪ Tends to micromanage ▪ Likes to say “I’d do it faster” ▪ Has to do a big effort to start trust the team. ▪ When receiving requirements looks at them from technological point of view ▪ Has managerial background ▪ Manages on high level ▪ Doesn’t say anything or look at TL/Architect ▪ Has to believe TL/Architect or involve 3 rd party ▪ When receiving requirements looks at them from business perspective

14. How to become a PM? – PM should bite you* * Kostyantyn Derets

15. How to become a PM? – Know Theory

16. How to become a PM? – Technical Person ▪ Develop your soft skills ▪ Substitute your PM ▪ Work with juniors ▪ Be even more proactive ▪ Improve your language

17. How to become a PM? – Non-technical Person ▪ Obtain basic technical skills ▪ Visit IT events ▪ Trust your team ▪ Consult with your team ▪ Imagine IT specialists are children ▪ Be honest!

18. 22 The End Ideas and implementationVadym Radchenko Produced by Vadym Radchenko © Email Twitter niceshaman@gmail.com @VadymR 2B || !2B