What is Scrum?
"The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them. The rules of Scrum are described throughout the body of this document."- Scrum Guide
ScrumDo provides a way to manage all of these things. Scrum is a framework used to implement Agile development. Any industry can benefit from it.
The heart: Transparency, Inspection, and Adaptation
"Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation." Guide
ScrumDo provides a way to iteratively, incrementally, predictably deliver and control risk. It's based on the values of inspection and adaptation. Transparency is a core value that is built into ScumDo.
Who Can Benefit From Scrum?
Scrum is used by software development teams, but the framework is not limited only to engineers or developers. It can be used for any sort of complex project and across all kinds of fields. If your team is producing some sort of product, Scrum can help you organize your team and get more work done in less time.
What enables us to do Scrum?
Let’s break down the pieces and parts that make Scrum happen
- Product Owner. This is someone who knows and understands the customer we are building the product for. That Product Owner is in charge of making the Product Backlog (Workspace backlog), a list of cards. The backlog of cards is prioritized by the Product Owner.
- The Team: "The Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint." - Scrum Guide. They are self-organizing.
- Scrum Master: "The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.
In ScrumDo All the members have access to a workspace. Each workspace has a team or many teams. Each workspace has team admins.
Product Owner and Scrum Master are typically set up as Team Admins to be able to help manage the workspace. Go here to see the various team role access types.
B. Artifacts. There are three important artifacts for a Scrum Team
- Product Backlog (Workspace backlog)
- Sprint Backlog (Cards on the Iteration board)
- Product Increment
- The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The ProductOwner is responsible for the Product Backlog, including its content, availability, and ordering.
The backlog is available as a list to import into and export out of.
The workspace backlog is also easily accessible from the board via the workspace backlog tab.
2. The Sprint log (Cards on the board)
The Sprint log is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint log is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment. See Sprint planning meeting.
Visualizing the work (Scrum (log) Board)
An important principle in Scrum is the idea of transparency. All team members involved should be aware of what everyone else is working on, progress being made, and what the team is trying to accomplish.
That’s why making things visible for all to see is so important.
The biggest piece of this is the Board. This is a place where you can organize your Backlog, as well as tasks that are being worked on in the current sprint and their progress.
Here is a simple example from ScrumDo:
The default board has the following columns
- To Do: When you plan your Sprint, you should pull tasks from the Backlog to this list. This is the current Sprint you are working on.
- Doing: When a task has been started, it gets moved here.
- For Review: As tasks are completed, they get moved to “For Review” before they are “done” or ready for release.
- Done: Passed quality check, ready to be shipped! No more edits or reviews necessary, it’s scheduled and ready for action. It means that it met the definition of done.
3. Product Increment
When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.
There are four important ceremonies in ScrumDo.
- Sprint Planning Meeting
- Sprint Review Meeting
- Daily Standup
- Sprint Retrospective
- The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. In this work is committed to a Sprint. The act of Dragging work from a backlog
Drag and Drop a card from the workspace backlog into the Sprint backlog in the Sprint Planning Meeting.
2. Sprint Review Meeting
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Workspace backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
ScrumDo encourages documentation of learnings and celeberation in the Notes Tab. Remember this informal.
3. Sprint Retrospective
The retrospective includes three main questions/points for discussion:
- What went well during the sprint cycle?
- What went wrong during the sprint cycle?
- What could we do differently to improve?
4. Daily Scrum
The daily scrum meeting is not used as a problem-solving or issue resolution meeting. Issues that are raised are taken offline and usually dealt with by the relevant subgroup immediately after the meeting. During the daily scrum, each team member answers the following three questions:
- What did you do yesterday?
- What will you do today?
- Are there any impediments in your way?