9. Conclusions Define scope in Agile way Clearly describe customer involvement Get understanding of Agile approach and practices Reach common understanding of resource limitations Implement functionality with highest priority first Reach common understanding of all items and their value Create common public project site where project status is displayed Reach agreement about support of software which is put into production
Rapid delivery High-quality software Maximize flexibility High added value
Late deadlinesLousy softwareOverspent budgetEndless discussions about scope
Describe scope in an agile firendly way, preferable user storiesClearly state customer involvement requirements and project acceptance criteria
EducateprojectteamonAgileapproachandpracticesReachcommonunderstandingofallresourcelimitations (financial, time limitations, human resources etc.) Agreeonfunctionalitywiththehighestpriorityandimplement it FIRST
Reachcommonunderstanding between client and supplier regarding all items and their valueCreatcommonpublic information space with up-to-date information onproject status