Transparency Team Management
•Télécharger en tant que PPT, PDF•
0 j'aime•197 vues
Юрій Малий Прозорість в роботі команди для керівництва
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (20)
Similaire à Transparency Team Management
Similaire à Transparency Team Management (20)
Plus de Lviv Startup Club
Plus de Lviv Startup Club (20)
Dernier
Dernier (18)
Transparency Team Management
- 1. Lviv Project Management Day http://lv.pmday.org/ November 26, 2016. Lviv, Ukraine Yuriy Malyi COMODO. Odesa, Ukraine Transparency in team work for management
- 2. Transparency in team work for management Who Am I? Name: Yuriy Malyi Company: COMODO Position: QA manager Experience in IT: 11 years
- 3. Who are You? • How many developers are here? • How many QA engineers are here? • How many managers/team leaders? • How many HR? • Any other experts? Transparency in team work for management
- 4. Transparency - physical property of allowing the transmission of light through a material (с) Wiki What is Transparency? Transparency in team work for management
- 5. Transparency - physical property of allowing the transmission of light through a material (с) Wiki What is Transparency? Transparency in team work for management
- 6. Transparency is operating in such a way that it is easy for others to see what actions are performed. (с) Wiki What does it mean in management? Transparency in team work for management
- 7. Transparency is operating in such a way that it is easy for others to see what actions are performed. (с) Wiki What does it mean in management? Transparency in team work for management
- 8. Why do we need it, what’s the problem? Transparency in team work for management
- 9. Black Box – NO control Transparency in team work for management
- 10. Transparency – effective control! Transparency in team work for management
- 11. Problem in projects and teams Transparency in team work for management
- 12. Problem in projects and teams Transparency in team work for management
- 13. Problem in projects and teams Transparency in team work for management
- 14. Problem in projects and teams Transparency in team work for management
- 15. Problem in projects and teams Transparency in team work for management
- 16. Problem in projects and teams Transparency in team work for management
- 17. Prehistory • What are you doing right now? • Why it takes so much time? • There is nothing to do so long! • I can complete this task 10 times faster! • Why You missed those BUGs during testing? • What are your automation team is doing? • Convince me! • Bullshit! • Etс… Transparency in team work for management
- 18. Preconditions • Projects and teams ( ) • Tasks and BUGs tracker (~Jira) • Work time logging system (~Jira Tempo) • Wiki (~Confluence) • Calendar (~Confluence calendars) • Test Management System (~ TestRail) • Willing to see the real situation in the team Transparency in team work for management
- 19. Team current state Transparency in team work for management
- 20. Team current state Transparency in team work for management
- 21. Capacity and details in tempo Transparency in team work for management
- 22. Capacity and details in tempo Transparency in team work for management
- 23. Feature Readiness Page Transparency in team work for management
- 24. Feature Risks Statuses • Feature can’t be delivered in time • Developments and Testing at risk • Feature may be delivered in time • Dev and Testing at the low risk • Feature may be delivered in time • Dev done, Testing at the low risk • Feature will be delivered in time • Dev done, Testing done Transparency in team work for management
- 25. Feature Readiness - Risk Matrix Transparency in team work for management
- 26. BUG status for releases Transparency in team work for management
- 27. Live link to Jira Transparency in team work for management
- 28. BUG status for releases Transparency in team work for management
- 29. Bugs daily progress(goal is “0” BUG rate) Transparency in team work for management
- 30. Change Management Board Transparency in team work for management
- 31. Detailed current status of Automation Transparency in team work for management
- 32. Detailed plan to achieve a goal Test cases for automation 1144 Current automation percent 27% Goal for automation percent 80% Number of cases to achhive the goal 916 Already automated 311 Need to be automated 605 Team performance (test cases/week) 15 Number of weeks to achhive a goal 40.33 Transparency in team work for management
- 33. Detailed reporting every week Transparency in team work for management
- 34. Real reflection of automated test cases Transparency in team work for management
- 35. Minimize time for reports Transparency in team work for management
- 36. Time cost • QA Team current state ~10 min per day for TL • WorkLog in Jira ~5 min per day for engineer • Feature Readiness Page ~2 hours create by TL • Feature Readiness Page ~5 min day to support • BUG status for releases ~1-3 min create by TL • Bugs daily progress ~1-3 min create by TL • Change Management ~10 min for PM on request • Detailed status and plan of Automation ~1-3 days • Automation report ~10 min per week for TL Transparency in team work for management
- 37. Success Story • Half a year of transparency… • New urgent release required… • Request to complete in NOW! • And… • Just 2 emails in replay • Details of all previous efforts • And we protected estimates! • … • Profit! Transparency in team work for management
- 38. The last weapon Transparency in team work for management
- 39. If you're going through hell… Transparency in team work for management
- 40. https://www.facebook.com/yuriy.malyi/posts/1153307468059014 (UKR) keep going. - Winston Churchill
- 41. Email : yuriy.malyi@gmail.com Skype : yura_clasic Questions? Transparency in team work for management
Notes de l'éditeur
- Transparency - physical property of allowing the transmission of light through a material.
- Transparency - physical property of allowing the transmission of light through a material.
- Transparency is operating in such a way that it is easy for others to see what actions are performed.
- Transparency is operating in such a way that it is easy for others to see what actions are performed.
- Usually every fuckup will be treated as team fail because of no trust to the team
- Usually every fuckup will be treated as team fail because of no trust to the team
- Usually every fuckup will be treated as team fail because of no trust to the team
- How to improve transparency: Reporting Metrics Understanding of current situation
- How to improve transparency: Fit the dates Fit the commitments Successful releases
- During the time we’ll get such trust that it won’t be necessary to continue all the reporting
- The most danger situation is when You fail some big release. So management will ask you everything what was done in details. And if You don’t have all reports and metrics that moment – it’ll be very bad for you
- So the best approach is to move between top to states and keep all the reporting in place
- If You need to protect your teams and estimates You should try to understand what metrics and data will be most effective and only after it start gathering