vitālijs jakovels and armands baranovskis: successful collaboration in agile projects. practical...
DESCRIPTION
TRANSCRIPT
Successful Collaboration in Agile Projects
Based on True Story
Armands Baranovskis, eBITVitālijs Jakovels, Tieto Latvia
Partners
www.ebit.lv www.tieto.com
ProjectCustomer: Ministry of Education and Science Republic of Latvia
Scope: development of state education information system
Cooperation Structure
Tieto & eBIT Tieto & eBIT
Analysis/
Sprint PlanningDemo/Retro
Development/
Daily Standups
eBIT
Tieto
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)
Customer Collaboration
Customer Collaboration
• Describe scope in an agile friendly way, preferably user stories
• Reach agreement on customer involvement and project acceptance criteria
• Make cooperation between partners seamless for the customer
Individuals and Interactions
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.)
Working Software
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
Responding to Change
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
ConclusionsDescribe 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
Thank you!