If you’re new to Scrum, it's easy to become a little overwhelmed by some of the new terms and concepts. To help ease your orientation, here's a short list of what we believe are some of the more important Scrum elements to initially wrap your head around.
A unit of work that, when complete, produces useful value to your end user / customer in language they would understand. A User Story is typically the basic unit of work in Scrum, and should represent most of your cards in ScrumDo.
A relative measure of effort of User Stories (or larger chunks of work that can carry labels like Capabilities, Epics, and Features). Usually arrived at through a consensus planning method in conjunction with a mechanic like Planning Poker. ScrumDo has built-in Planning Poker capabilities.
Ideally, delivery / development teams are made up of individuals bringing multiple skill sets and capabilities to the team. In a software development context, this typically means team members possess engineering, qa, and design expertise. The ideal size of a Scrum team is between 4-10 people.
A special role in the Scrum framework. This person guides the team on what capabilities should be produced, and the priority in which they should be produced.
Another special role in the Scrum framework. This person helps to remove obstacles that may prevent the team from successfully meeting its commitment to deliver work, guides the team in Lean-Agile principles, and shields the team from unnecessary distractions so they can concentrate on what they do best.
The remaining members of the Scrum team. These are the people doing the actual work of creating and implementing the work described in the User Stories.
Potentially Shippable Product (or Potentially Shippable Increment)
Work that is ready for end-users to use. It may not be complete from a market perspective, and it may not actually ship, but it should function without serious defects and be usable.
Sprint / Iteration
A time-boxed period of time (typically 2-weeks) that starts with an Sprint Planning meeting and ends with successful delivery of a Potentially Shippable Increment.
Sprint / Iteration Planning Meeting
Meeting at the start of a Sprint / Iteration where the delivery / development team agrees upon what work they commit to delivering by the end of the Sprint. Typically, these meetings involve discussions with the Product Owner, team estimates of individual User Stories, then arrival at a team consensus as to which combination of User Stories will satisfy the Product Owner's objective for this Sprint / Iteration and which the team can commit to delivering by the end of the Sprint / Iteration.
Sprint / Iteration Review
Meeting at the end of the Sprint / Iteration where completed work is reviewed with the Product Owner and other stakeholders.
Definition of Done
An explicit (and continuously updated) statement of what conditions all work must satisfy to be considered “done." Not to be confused with Acceptance Criteria, which is a list of specific criteria a specific User Story must satisfy to be considered done.
A short daily meeting where team members answer three questions: What did you do yesterday? What will you do today? Are there any impediments in your way?
A list of work items for which work is not yet scheduled to start.
A visual measure of progress. The chart begins with a plotting of a given scope of work (often depicted in Story Points). As work is completed, the chart is adjusted downward by the number of Story Points of that completed work.