Scrum is a "lean" approach to software development. The term Scrum comes from a 1986 study [1] by Takeuchi and Nonaka that was published in the Harvard Business Review. In that study, Takeuchi and Nonaka note that projects using small, cross-functional teams historically produce the best results.
Scrum is a simple "inspect and adapt" framework that has three roles, three ceremonies, and three artifacts [1] designed to deliver working software in Sprints, usually 30-day iterations.
- Roles: Product Owner, ScrumMaster, Team;
- Ceremonies: Sprint Planning, Sprint Review, and Daily Scrum Meeting;
- Artifacts: Product Backlog, Sprint Backlog, and Burndown Chart
No comments:
Post a Comment