Sprint 3: More Agile and Lean
Table of Contents
1 About this Sprint
This sprint presents more agile and lean frameworks.
2 Sprint Goals
Agile: The student will be familiar with common Agile Frameworks.
Lean: The student will gain further insight into Lean Software Engineering tools and methods.
3 Readings
3.1 Book Chapters
- M. Cohn “Succeeding with Agile”, chapters 10-13
- J. Rasmusson “The Agile Samurai”, chapters 3-5
3.2 Screencasts
3.3 Articles
Agile Transitioning, developers’ opinions [Laanti et al. 2011] Maarit Laanti, Outi Salo, Pekka Abrahamsson: Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation. Information \& Software Technology 53(3): 276-290 (2011).
Agile Transitioning, success and failure factors [Chow \& Cao 2008] T. Chow, DB Cao, A survey study of critical success factors in agile software projects, Journal of Systems and Software 81 (2008) 961–971.
3.4 Further Reading Optional
Pair Programming, Evidence on [diBella et al. 2013] Enrico di Bella, Ilenia Fronza, Nattakarn Phaphoom, Alberto Sillitti, Giancarlo Succi, Jelena Vlasenko: Pair Programming and Software Defects-A Large, Industrial Case Study. IEEE Trans. Software Eng. 39(7): 930-953 (2013).
Stress and Wellbeing [Laanti 2013] M. Laanti, 2013 Agile and Wellbeing — Stress, Empowerment, and Performance in Scrum and Kanban Teams in Proceedings of the 46th Hawaii International Conference on System Sciences, 2013.
4 Experiential Learning
4.1 TODO Update Backlog
Based on what you have learnt in this sprint, update your Agile/Lean backlog accordingly. Specifically;
- Revisit the order of the course sprints. Are there any sprints you would like to do sooner or later?
- What can you take with you from this sprint into your own organisation?
- What do you need to learn more about?
Add and move items in your Agile/Lean backlog according to your needs and priorities.
5 Sprint Acceptance Tests
5.1 More Agile and Lean
You have completed this learning outcome when you have:
- Gained a deeper understaning Lean Software Development and of some of the tools and techniques available.
Review Questions
- Why use “User stories” instead of a traditional requirement set up ?
- Are you using “User stories” in your operation ?
- In what way are you using them today ?
- How would you say that “User stories” help your operation ?
- Lean has some principles, how do your operation comply to these ?
- Both Agile & Lean have high priority on the “Value” delivered, how would you say that your operation comply to this ?
- Can you see what gives most value for your operation today ?
- What would it mean if you took another method and used that instead of what you are using today ?
- How will the waste change ?
- How will the value change ?
- How would the efficiency change ?