CategoriesAgile Automated Testing build quality in checkstyle configuration continuous integration create knowledge defer commitment Definition of Done deliver fast development dynamic languages eliminate waste Functional Programming groovy hudson Lean Multi-Paradigm-Programming NoSQL optimize the whole pair programming programming style respect people Scala SCRUM Scrum master sprint planning tdd test-driven-development testing Uncategorized UnitTests User Story value stream welcome
Error: Twitter did not respond. Please wait a few minutes and refresh this page.
Daily Archives: December 16, 2011
Scrum is a Lean approach to Software development.
The term itself (“Scrum”) was introduced by Takeuchi and Nonaka (1986). The study was published in Harvard Business Review in 1986. They explain that projects using small, cross-functional teams historically produce the best results. They relate these high performance teams to “Scrum” formations in Rugby.
Scrum for software development was introduced in 1993 by Jeff Sutherland at Easel Corporation using the study by Takeuchi and Nonaka (1986) as a basis for by adopting their analogy as the name of the process as a whole for software development. The other name linked to Scrum is of course Ken Schwaber who formalized the process for the worldwide software industry in the first published paper on Scrum at OOPSLA (Schwaber, 1997).
Scrum is a simple “inspect and adapt” framework that has three roles, three ceremonies, and three artefacts designed to deliver working software in Sprints, usually 30-day iterations (Scotland, 2005).
- 3 Roles
Product Owner, Scrum Master, Development Team
- 3 Ceremonies
Sprint Planning, Spr Continue reading