Максим Почебут “Чи шкідливі Agile практики junior інженерам?” Lviv Project Management Day
•Download as PPTX, PDF•
1 like•118 views
The document discusses whether agile practices are harmful for junior engineers. It notes that juniors often receive theoretical training from non-experts, leading to a distorted understanding of project management. To address this, the document proposes an education service to give juniors real project experience using various tools and approaches like internships, trainings, and adapting them to projects. Both benefits and risks of the agile approach for juniors are presented, emphasizing the need to consider the full complexity of methods and carefully choose trainers.
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Максим Почебут “Чи шкідливі Agile практики junior інженерам?” Lviv Project Management Day
Similar to Максим Почебут “Чи шкідливі Agile практики junior інженерам?” Lviv Project Management Day (20)
More from Lviv Startup Club
More from Lviv Startup Club (20)
Recently uploaded
Recently uploaded (20)
Максим Почебут “Чи шкідливі Agile практики junior інженерам?” Lviv Project Management Day
- 1. ARE AGILE PRACTICES HARMFUL FOR JUNIOR ENGINEERS? Maxim Pochebut
- 2. UNIVERSITY & SCIENCE 12 years experience in High School Ph.D., Associate Professor EPAM Experience From 2013 Head of Education Programs in EPAM Ukraine PM Experience PMPCertified pochebutmaxim@gmail.com pochebut_maxim skype About me NGO Vice - President “IT Ukraine”
- 3. Question How we became a PM? Grow from technical specialist Special Schools and trainings Retraining
- 4. Question Where we heard about Project management in the first time? Trainer – non competency in real projects and tasks Course based on PMBoK pictures Copy - paste from blogs, bad translation from English resources I heard at the University lections
- 5. As a result Deformation of understanding PM role Rejection Boring, non interesting tasks I have got at the University …
- 6. Possible career path in IT
- 7. Possible career path in IT To hire
- 8. Juniors University Graduates Education Service Grow Juniors Improve technical background Project activities Real tasks Different tools University education No project experience Low level of knowledge Poor soft skills Improve soft skills Possible solutions – EDUCATION SERVICE
- 9. How IT COMPANY growS juniors Internships 2 1 University trainings 3 Project adaptation
- 10. University trainings Some numbers about basis knowledge 2000+ Internship750+ 70% 20% 10% Agile Another approaches Can give definition of project 100% 50% 10% Agile Another approaches Can give definition of project
- 11. What we need for this project adaptation ■ Theoretical basis ■ Understanding processes ■ Deeply involvement production mentors and experts ■ Environment ■ Project ideas
- 12. What approaches we need to choose for project education/adaptation? problem
- 15. Standish Group 2015 Chaos Report ■ https://www.infoq.com/articles/standish-chaos-2015 This table summarizes the outcomes of projects over the last five years using the new definition of success factors (on time, on budget with a satisfactory result)
- 16. Standish Group 2015 Chaos Report
- 17. Standish Group 2015 Chaos Report
- 18. Skilled staff are people who understand both the business and the technology. A skilled staff is highly proficient in the execution of the project’s requirements and deliver of the project or product. Agile proficiency means that the agile team and the product owner are skilled in the agile process. Agile proficiency is the difference between good agile outcomes and bad agile outcomes. Standish Group 2015 Chaos Report
- 19. Engineering Culture and Methods InfoQ Trends Report - January 2018
- 20. Project management modules (Agile focus) Agenda: ■ Agile philosophy. Introduction to Scrum framework. ■ Requirements in Scrum ■ Planning in Scrum.
- 21. ScrumFramework ScrumTeam • Product Owner • Development Team • Scrum Master Events • Sprint Planning • Sprint Review • Sprint Retrospective • Daily Standup • (Backlog Grooming) Artifacts • Product, release and sprint backlogs • Burndown charts • Scrum Board Agile philosophy. Introduction to Scrum framework. Roles in Scrum. Meetings in Scrum. Artifacts in Scrum.Why Scrum works?
- 22. Requirements in Scrum Requirements in Scrum: ProductVision, Backlog, Backlog Grooming, Themes, Epics, User Stories, Non-functional requirements. 3Cs, INVEST. Practice on user stories.
- 23. Planning and Estimation Planning in Scrum: Agile planning vs. traditional planning, Release Planning, User Story Mapping, Sprint Planning, Sprint Planning techniques, Sprint Size. Estimation in Scrum: Story Points, Planning Poker,Tasks, Ideal Hours, Velocity. Definition of Ready. Definition of Done. Practice on planning.
- 25. Barnaby James‘, Google. “Skills allow us to raise rates, but they do not guarantee success”. Survivorshipbias (систематическая ошибка выжившего)
- 26. Positive side ■ Fast track involvement in real projects ■ Creation cross functional team ■ Development of team players mindset ■ Basis for executor mindset ■ etc
- 27. Return to career path
- 28. And to PwC framework
- 29. Negative sides ■ Lost of “BIG picture” view ■ Don’t pay attention of work with stakeholders ■ Lack of solution creation mindset, lost innovators. ■ “Weak” sides of trainings type of Contracts work with stakeholders, budgeting, most of the trainers don’t pay attention of backlog creation ■ Don’t show unsuccessful projects
- 30. Another experience ■ Master program in Kyiv – MohylaAcademy ■ Course “Management of IT projects” ■ Audience – software engineers 1+ years of experience (5+ companies fromTOP 10 in UA) ■ Duration 1 semester, 4 hours 1 per week.
- 31. Typical portrait Scare of responsibility Difficulties of making decisions Don’t understanding of balance customer satisfaction & profitability
- 32. Approaches ■ Only real modeling tasks ■ Interactive ■ Tasks based on trainee’s personal experience ■ Conflict creation ■ Only truth ■ Creation own methodology based on tasks ■ Gamification
- 33. Agenda ■ Intro to PMBoK (group of processes etc.) ■ Training for SMART goals ■ Agile (Scrum, Kanban,TDD) ■ Negotiation ■ Team building training ■ “Lessons learned” focus
- 34. Agenda ■ Workshops and games examples – for 1-1 meetings – Negotiation with customer – Creation project documentation – Risk management – Working with diff types of stakeholders – Conflict solving – Types of contracts – Creation own methodology – Intro meeting – plan creation. – Etc…
- 35. You can ask, why we need to do all this things ■ This is promotion for engineering culture ■ It is basis for next step of management in IT – Delivery manager ■ We need to share this practices for creation and development strong technical and management community ■ Develop ecosystem
- 36. Return to question of topic ■ If we work with juniors we need to share full complex of methods ■ We should explain how we chose different methods ■ We should carefully choose the person who will trainer for juniors ■ We have lack numbers of PMs who involved in education, so we need to promote necessity of this.
- 37. Useful links ■ https://www.agiloft.com/how-to-ensure-success-it-projects.pdf ■ http://project-management.zis.by/statistika/statistika-uspeshnosti-itproektov.--.html ■ https://www.pwc.com/gx/en/actuarial-insurance-services/assets/agile-project- delivery-confidence.pdf ■ https://www.projectsmart.co.uk/white-papers/chaos-report.pdf ■ https://www.infoq.com/articles/standish-chaos-2015
- 38. Q & A Thank you for attention ! pochebutmaxim@gmail.com pochebut_maxim skype https://www.facebook.com/pochebut
Editor's Notes
- The concepts of Scrum can be explained by explaining recommended roles, meetings and artifacts (documentation) in Scrum. Let’s cover them deeply in the next slides.
- Let’s start with agreeing on terms. What is a requirement? In engineering, a requirement is a singular documented physical and functional need that a particular product or service must be or perform.