RAD Scrum Glossary/Primer

From RAD Studio
Jump to: navigation, search

Go Up to Rapid Application Development (RAD) Concepts


Scrum is an iterative incremental model for rapid application development (RAD), sometimes also called agile software development.

In scrum, the product development schedule is divided into sprints or iterations (typically 30 days in length) during which the team strives to complete a set of prioritized goals established by the team. At the end of each iteration, the product is ideally in a working state, and the team reviews their successes/failures in a retrospective meeting and selects the goal for the next iteration in a planning meeting.

Contents

Team Roles

  • Team: These are the people who do the work. The team is part of the larger project community.
  • Product Owner: Represents the interests of all stake holders, and creates and maintains the Project Backlog, a key artifact of scrum.
  • Scrum Master: Manages the scrum process for the team. The scrum master needs to provide training when necessary and breaks up logjams when the team gets bogged down by problems.

Project Artifacts

  • Project Backlog: The high-level work items that define the project. Maintained by the Product Owner.
  • Sprint Backlog (Current Iteration): The detailed work items, owned by the team, that define the work to be accomplished during the sprint. A burndown graph can be used to convey progress during the sprint.

Process

  • Release: A defined interval of time used for high-level planning of product dliverables. Culminated by the delivery of the product.
  • Sprint: The iteration, the basic work unit of scrum.
  • Planning Meeting: A meeting to detail the tasks from the Project Backlog to be the planned work in the upcoming sprint.
  • Standup: A short daily meeting held by the team to aid coordination. The team checks for blocking issues, summarizes current tasks.
  • Demo: An open meeting held at the end of a sprint during which the team shows off the work accomplished during the sprint.
  • Retrospective Meeting: A meeting held by the team to reflect on the complete sprint activity with the intention of improving the team scrum process. Considerations are: What went well during the sprint, and what could be improved.

See Also

Personal tools
Newest Version: XE
In other languages