The document discusses successful collaboration in agile projects based on a case study between eBIT and Tieto Latvia working with the Ministry of Education and Science Republic of Latvia. Key aspects of their cooperation included defining the scope through user stories, agreeing on customer involvement and acceptance criteria, and making the partnership seamless for the customer. The collaboration also focused on individuals and interactions, working software over documentation, and responding to changes by prioritizing work and maintaining a shared understanding of limitations.

1. Successful Collaboration in Agile Projects Based on True Story Armands Baranovskis, eBIT Vitālijs Jakovels, Tieto Latvia

2. Partners www.tieto.com www.ebit.lv

3. Project Customer: Ministry of Education and Science Republic of Latvia Scope: development of state education information system

4. Cooperation Structure eBIT Tieto & eBIT Tieto & eBIT Development/ Daily Standups Analysis/ Sprint Planning Demo/Retro Tieto

5. Must have Customer collaboration over contract negotiation Individuals and interactions over processes and tools Working software over comprehensive documentation Responding to change over following a plan (Agile Manifesto)

6. Customer Collaboration

7. Customer Collaboration Describe scope in an agile friendly way, preferablyuser stories Reach agreement on customer involvement and project acceptance criteria Make cooperation between partners seamless for the customer

8. Individuals and Interactions

9. Individuals and Interactions Create and maintain common public information space with up-to-date information on project status Educate people involved in project on Agile approach by using practices together Manage common understanding of all resource limitations (financial, time, human resources etc.)

10. Working Software

11. Working Software Implement development methods, not only Scrum rituals Refactor code developed in previous cycles with an aim to improve and simplify it Measure sprint results by working software

12. Responding to Change

13. Responding to Change Reach common understanding among parties regarding all scope items and their value Agree on scope items with the highest priority and implement them FIRST Reach agreement on support of software which is already in production

14. Conclusions Describe scope in an agile friendly way Reach agreement on customer involvement and project acceptance criteria Make cooperation between partners seamless for the customer Implement development methods, not only Scrum rituals Refactor code developed in previous cycles Measure sprint results by working software Create and maintain common public information space Educate people involved in project Manage common understanding of all resource limitations Reach common understanding of all scope items and their value Implement scope items with the highest priority FIRST Reach agreement on support of software which is already in production

15. Thank you!