Tough Lessons in distributed-multinational environment<br />Lukas Simokaitis<br />
Content<br />Background<br />About the project<br />Agile in the project<br />Strengths<br />Hot Issues <br />Summary<br />
My Agile Background<br />VU MIF – Software Engineering (bachelor)<br />Tieto (www.tieto.com)<br />ERP (www.erp.eu)<br />
About the project<br />Government sector – eCustoms for Tajikistan<br />People working – Over 50<br />Project lasted ~ 2 y...
Architecture<br />SOA based architecture<br />ESB as integration platform<br />Over 3 internal systems + 1 main business o...
Initial plans<br />All teams will use Scrum<br />Scrum of Scrums<br />Iteration 2 weeks long<br />Active and often communi...
What did we do?<br />Scrum - step by step<br />Workshops for all teams<br />Presented our vision about the architecture<br />
What did we do?<br />Agile tools<br />
What did we do?<br />Backlog & priorities<br />
What did we do?<br />Progress Visualization<br />
What did we do?<br />Working Software<br />
Communication<br />TJ Business team<br />AZ Hardware Team<br />KZ dev team<br />KZ dev team<br />2 systems<br />LT lead te...
Results<br />Only 1 Team successfully using Scrum<br />Collaboration between teams’ representatives<br />Client communicat...
Some didn’t make it<br />
Some didn’t make it<br />TJ Business team<br />AZ Hardware Team<br />KZ dev team<br />KZ dev team<br />LT lead team<br />B...
Picture<br />Strengths<br />what we <br />benefited <br />from<br />
Strengths<br />Good communication in teams<br />
Strengths<br />Competent team representatives<br />
Strengths<br />Reusable solutions for the future<br />
Strengths<br />Minimized waste<br />
Strengths<br />Right tools<br />
Strengths<br />More fun, Happy Scrum Team, belief in success<br />
Hot Issues<br />what we frustrated from<br />
Hot Issues <br />Distributed teams<br />
Hot Issues <br />Cultural Aspects<br />
Hot Issues <br />Tight schedule<br />
Hot Issues <br />Too much time spent on One Vision propagation<br />
Hot Issues <br />Collaborative requirements engineering<br />Rather light weight development standards, instructions and g...
Summary<br />Focus on intensive communication<br />Find the key persons for distributed-teams communication<br />Prepare y...
Thank You!<br />
Upcoming SlideShare
Loading in …5
×

Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment

808 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
808
On SlideShare
0
From Embeds
0
Number of Embeds
239
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Lack of experience in distributed ScrumResistance with political flavorMisbalanced Team formationLack of communication with customerPressure on timeChaotic BackLog
  • Lukas Simokaitis: Tough Lessons in Distributed-Multinational Environment

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

    ×