Successful Collaboration in Agile Projects<br />Based on True Story<br />Armands Baranovskis, eBIT<br />Vitālijs Jakovels,...
Partners<br />www.tieto.com<br />www.ebit.lv<br />
Project<br />Customer: Ministry of Education and Science Republic of Latvia <br />Scope: development of state education in...
Cooperation Structure<br />eBIT<br />Tieto & eBIT<br />Tieto & eBIT<br />Development/<br />Daily Standups<br />Analysis/<b...
Must have<br />Customer collaboration over contract negotiation<br />Individuals and interactions over processes and tools...
Customer Collaboration<br />
Customer Collaboration<br />Describe scope in an agile friendly way, preferablyuser stories<br />Reach agreement on custom...
Individuals and Interactions<br />
Individuals and Interactions<br />Create and maintain common public information space with up-to-date information on proje...
Working Software<br />
Working Software<br />Implement development methods, not only Scrum rituals<br />Refactor code developed in previous cycle...
Responding to Change<br />
Responding to Change<br />Reach common understanding among parties regarding all scope items and their value<br />Agree on...
Conclusions<br />Describe scope in an agile friendly way<br />Reach agreement on customer involvement and project acceptan...
Thank you!<br />
Upcoming SlideShare
Loading in …5
×

Vitālijs Jakovels and Armands Baranovskis: Successful Collaboration in Agile Projects. Practical Issues and Cooperation Experience Between eBIT and Tieto

1,443 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
1,443
On SlideShare
0
From Embeds
0
Number of Embeds
413
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Vitālijs Jakovels and Armands Baranovskis: Successful Collaboration in Agile Projects. Practical Issues and Cooperation Experience Between eBIT and Tieto

  1. 1. Successful Collaboration in Agile Projects<br />Based on True Story<br />Armands Baranovskis, eBIT<br />Vitālijs Jakovels, Tieto Latvia<br />
  2. 2. Partners<br />www.tieto.com<br />www.ebit.lv<br />
  3. 3. Project<br />Customer: Ministry of Education and Science Republic of Latvia <br />Scope: development of state education information system<br />
  4. 4. Cooperation Structure<br />eBIT<br />Tieto & eBIT<br />Tieto & eBIT<br />Development/<br />Daily Standups<br />Analysis/<br />Sprint Planning<br />Demo/Retro<br />Tieto<br />
  5. 5. Must have<br />Customer collaboration over contract negotiation<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Responding to change over following a plan <br /> (Agile Manifesto)<br />
  6. 6. Customer Collaboration<br />
  7. 7. Customer Collaboration<br />Describe scope in an agile friendly way, preferablyuser stories<br />Reach agreement on customer involvement and project acceptance criteria<br />Make cooperation between partners seamless for the customer<br />
  8. 8. Individuals and Interactions<br />
  9. 9. Individuals and Interactions<br />Create and maintain common public information space with up-to-date information on project status<br />Educate people involved in project on Agile approach by using practices together<br />Manage common understanding of all resource limitations (financial, time, human resources etc.) <br />
  10. 10. Working Software<br />
  11. 11. Working Software<br />Implement development methods, not only Scrum rituals<br />Refactor code developed in previous cycles with an aim to improve and simplify it<br />Measure sprint results by working software<br />
  12. 12. Responding to Change<br />
  13. 13. Responding to Change<br />Reach common understanding among parties regarding all scope items and their value<br />Agree on scope items with the highest priority and implement them FIRST<br />Reach agreement on support of software which is already in production<br />
  14. 14. Conclusions<br />Describe scope in an agile friendly way<br />Reach agreement on customer involvement and project acceptance criteria<br />Make cooperation between partners seamless for the customer<br />Implement development methods, not only Scrum rituals<br />Refactor code developed in previous cycles<br />Measure sprint results by working software<br />Create and maintain common public information space<br />Educate people involved in project<br />Manage common understanding of all resource limitations<br />Reach common understanding of all scope items and their value<br />Implement scope items with the highest priority FIRST<br />Reach agreement on support of software which is already in production<br />
  15. 15. Thank you!<br />

×