„Į komandos sėkmę galima žvelgti kaip į dėlionę, susidedančią iš įvairių praktikų, procesų ir, be abejo, bendro komandos gerbuvio. Reguliarios refleksijos mums padeda įsivertinti šios dėlionės sudaromą paveikslą ir suprasti, kad mus stabdo bei kas padeda judėti pirmyn“ ,- sako Ugnė. Pranešėja pasidalino „hands on“ patirtimi apie komandos retrospektyvas: jų pokyčius, klaidas, pamokas ir kokių iššūkių įprastoms praktikoms įnešė netikėtai pakitusios darbo sąlygos. Ugnė eina Frontend programuotojos pareigas Vinted. Pranešėjos kelią į programavimą lydėjo nuolatinės refleksijos, reikšmingai prisidėjusios prie profesinio augimo ir karjeros pokyčio. Metų pradžioje susikūrus naujai komandai, Ugnė savo jėgas nusprendė išbandyti vesdama komandos retrospektyvų susitikimus, prisidėdama prie komandos savirefleksijos ir tobulėjimo. Ugnės pranešimo vaizdo įrašas: https://bit.ly/Ugnės_pranešimas

1. Reflections and Lessons -
not only about processes
Ugnė Kryževičiūtė
Frontend developer @ Vinted

2. Diving-in solo:
😱 Chaotic learning
🐑 Vulnerability in not knowing
🤷 Lack of self awareness on
where to improve
Self learning through self reflection
Guidance and self improvement:
📂 Regular reviews and feedback
👩🔧 Self reflection
💃 Behaviour adjustment

3. ① What was learnt?
② What were the obstacles?
③ What was done well?
④ What would we do differently?
⑤ What’s next?
A retro for internship

5. TL;DRRetros ≠ Debugging

6. The Staircase of Reflective Learning
Starting
point
Retro #1
Retro #2
Retro #N
Target

7. Purpose - team growth facilitation:
🏁 Organized after every sprint
🧬 Each team defines its retro format
🤹 Problems discussed depend on the
dynamics of each team
🙋 Becoming a retro facilitator
Retrospectives at Vinted

8. 🙂 🙂 🙂
Rediscovering retrospectives:
📵 No distractions in the meeting
✨ Making it engaging
🎨 Experimenting with formats
Making everyone present
😷 😷 😷
Reconnecting in remote retros:
🏖 Convenience and inclusion
🐈 More distractions
🗃 Less flexibility and variation

9. Sharing as
learning

10. Enabling to speak up
Trust and safety:
👌 Mistakes are OK
🐼 You can be yourself
No fear of conflict:
✌ Comfort in disagreement
⚙ Productive discussions
Methods and approaches:
📝 Sticky notes 🦸 Anonymity
🥇 Lead by example & share first

11. Overcoming the empty mind
Guidance and framing:
🔍 Overviewing the sprint
📝 Regular notes throughout the sprint
❓ Guiding questions
🎭 Themed retros

12. Dealing with a jigsaw of topics:
📦 Timeboxing (?)
🤿 Diving deep into key topics
👉 Postponing or shifting
discussions to Slack
Trying to cover all topics

13. ⚖ Retrospectives shouldn’t give
a feeling of constant failure
🎉 Spend time on celebrating
🦄 Discuss what makes the team
unique
Retrospectives ≠ Failure reviews

14. 😡 Ranting and blaming is a wrong output
of a retrospective
🔎 Vague and obscure action items
🚫 No owner and/or deadline
😩 Too many action items
⏳ Is it a one time thing or it repeats/can
occur in the future?
Action items or it didn’t happen

15. Action item review and tracking
🧐 Regularly reviewing action items
♾ Setting continuous action items
💾 Where to store them?

16. Identify
Opportunities in the
process workflow
Plan
How can the current
process be improved?
Execute
Implement changes and
track improvements
Review
How are changes
working for the team?
The
Continuous
Improvement
Cycle

17. TL;DRRetros = Learning

18. Thank YouThank You