![Page 1: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/1.jpg)
XP@Scrum modelAuthor: Alejandro Lopez
Supervisors: Ana M. Moreno, Shingo Takada
![Page 2: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/2.jpg)
Index of contents
● Model diagrams● Connecting, enriching and simplifying the
models● Defining the XP@Scrum model● Final considerations
![Page 3: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/3.jpg)
Model diagrams
![Page 4: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/4.jpg)
Scrum model images
![Page 5: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/5.jpg)
XP model images
![Page 6: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/6.jpg)
XP model images
![Page 7: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/7.jpg)
Connecting, enriching and simplifying the models
![Page 8: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/8.jpg)
Connecting the XP model (I)
![Page 9: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/9.jpg)
Connecting the XP model (II)
![Page 10: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/10.jpg)
Connecting the XP model modified (I)
![Page 11: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/11.jpg)
Connecting the XP model modified (II)
![Page 12: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/12.jpg)
Scru
m m
odel im
age im
proved
![Page 14: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/14.jpg)
Terminology changes
● Development → Daily Scrum● Iteration → Sprint● Release planning → Delivery meeting
– Release plan → Delivery plan
● Iteration planning → Sprint meeting– Iteration plan → Sprint plan
● Latest Version → Product increment● Stand Up meeting → Daily meeting
![Page 15: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/15.jpg)
Comparison summary (I)
Flexible production? More or less More or lessLean/JIT production? Yes Yes
Process improvement? Yes Yes
Workforce? Yes Yes
Leadership? -Decision making? Yes Yes Shared responsability (Scrum XP)
Worklife quality? No overworkSystem metaphor? No* Yes *But Sprint zero in Scrum
? Yes
Yes NoAcceptance criterias? No YesInteration? 1 month 2 weeks
Yes No
None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective ownership. (XP)
People are encouraged to develop their own practicesMove people around, pair programming (XP) members selected depending on expertise (Scrum)
Scrum master is a coach
Motivated individuals, with good environment and trusted. Shared responsability for efficience (XP and Scrum)
Insulated project from external pressure
High level discipline is neccessary?Introduction in an organization?
Non-functional requirements
Not clear distinction between non-functional and functional (XP)
We can include XP way of life without problems
![Page 16: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/16.jpg)
Flexible production? More or less More or lessLean/JIT production? Yes Yes
Process improvement? Yes Yes
Workforce? Yes Yes
Leadership? -Decision making? Yes Yes Shared responsability (Scrum XP)
Worklife quality? No overworkSystem metaphor? No* Yes *But Sprint zero in Scrum
? Yes
Yes NoAcceptance criterias? No YesInteration? 1 month 2 weeks
Yes No
None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective ownership. (XP)
People are encouraged to develop their own practicesMove people around, pair programming (XP) members selected depending on expertise (Scrum)
Scrum master is a coach
Motivated individuals, with good environment and trusted. Shared responsability for efficience (XP and Scrum)
Insulated project from external pressure
High level discipline is neccessary?Introduction in an organization?
Non-functional requirements
Not clear distinction between non-functional and functional (XP)
Comparison summary (II)
![Page 17: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/17.jpg)
XP
@S
crum
![Page 18: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/18.jpg)
Changes
● Included Architectural Spike in Sprint Zero– And produces a system metaphor
● Test scenarios have to be included in the product backlog and used in the Sprint review
● We include the “Spike” in the delivering planning meeting
● Suggested 4 months for releases
![Page 19: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/19.jpg)
Changes
● Demo and releases creates a conflict– Let's call demo what we present before being
customer accepted
– Let's call small release a customer approved demo
– Let's call release to a sum of small releases well prepared and packaged for production environment
● Failed acceptance tests and bugs are included in the process
![Page 20: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/20.jpg)
XP
@S
crum
![Page 21: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/21.jpg)
Final considerations
● Incidents, errors, problems are considered as a new User Story with special priority
– Idea took from Scrum from the trenches book
● I didn't connect Project Velocity to the delivery meeting but I think they should be connected
● Sprint Zero looks widely used but not official Scrum
– Do I keep it, or directly change to Architectural Spike?
● I didn't show in the presentation the engineering and management practices but they are all included
– Scrum management practices and XP engineering practices
– The report will have them explained and connected
![Page 22: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/22.jpg)
For this week
● Correcting issues, solving doubts and improving if possible the model
● Formal report about this light systematic review and the results
![Page 23: XP@Scrum model - WordPress.com · 2014. 2. 18. · None of them use high level portfolio. Evaluation of results and plannification depending on it (Scrum) Move people around. Collective](https://reader035.vdocuments.site/reader035/viewer/2022071013/5fcb88492168e056be14d048/html5/thumbnails/23.jpg)
Ojo
● Test scenario vs Acceptance criteria?● Incluir test scenarios dentro de un product
backlog?● Dentro del concepto de delivery meeting, o
entrega release o ve los cambios● Sprint velocity que unidades tiene