Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment
•Télécharger en tant que PPTX, PDF•
0 j'aime•501 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (18)
Similaire à Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment
Similaire à Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment (20)
Plus de Agile Lietuva
Plus de Agile Lietuva (20)
Dernier
Dernier (20)
Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment
- 1. Tough Lessons in distributed-multinational environment Lukas Simokaitis
- 2. Content Background About the project Agile in the project Strengths Hot Issues Summary
- 3. My Agile Background VU MIF – Software Engineering (bachelor) Tieto (www.tieto.com) ERP (www.erp.eu)
- 4. About the project Government sector – eCustoms for Tajikistan People working – Over 50 Project lasted ~ 2 years Distributed over 5 countries and 6 cities
- 5. Architecture SOA based architecture ESB as integration platform Over 3 internal systems + 1 main business orchestration system Over 8 self-sufficient supplementary systems Over 5 external systems And many common services for all systems
- 6. Initial plans All teams will use Scrum Scrum of Scrums Iteration 2 weeks long Active and often communication with client One Backlog with priorities
- 7. What did we do? Scrum - step by step Workshops for all teams Presented our vision about the architecture
- 8. What did we do? Agile tools
- 9. What did we do? Backlog & priorities
- 10. What did we do? Progress Visualization
- 11. What did we do? Working Software
- 12. Communication TJ Business team AZ Hardware Team KZ dev team KZ dev team 2 systems LT lead team 6 systems + commons BY analytical team BY integration dev team 2 systems + integration platform LT dev team 1 system
- 13. Results Only 1 Team successfully using Scrum Collaboration between teams’ representatives Client communication from very poor to good Iterations for one Scrum team Milestones for others Backlog wasn’t for everyone Chaotic priorities From misbalanced to normal teams Successful project finish
- 14. Some didn’t make it
- 15. Some didn’t make it TJ Business team AZ Hardware Team KZ dev team KZ dev team LT lead team BY analytical team BY integration dev team LT dev team
- 16. Picture Strengths what we benefited from
- 17. Strengths Good communication in teams
- 18. Strengths Competent team representatives
- 19. Strengths Reusable solutions for the future
- 22. Strengths More fun, Happy Scrum Team, belief in success
- 23. Hot Issues what we frustrated from
- 24. Hot Issues Distributed teams
- 25. Hot Issues Cultural Aspects
- 26. Hot Issues Tight schedule
- 27. Hot Issues Too much time spent on One Vision propagation
- 28. Hot Issues Collaborative requirements engineering Rather light weight development standards, instructions and guidelines
- 29. Summary Focus on intensive communication Find the key persons for distributed-teams communication Prepare you knowledge bag (do homework) beforehand and share it with others Collaborate with your client You’ll eliminate waste Think about reusability, modularity and automation Get support and trust from all teams and their management
- 30. Thank You!
Notes de l'éditeur
- Lack of experience in distributed ScrumResistance with political flavorMisbalanced Team formationLack of communication with customerPressure on timeChaotic BackLog