A philosophy which provides an excellent baseline by the understanding of being iterative and incremental through collaboration between self-organizing, value-driven teams and adaptive to changes
Scrum is a formal process framework for developing and sustaining complex products. It has been invented by Jeff Sutherland and Ken Schwaber.
It is the single source of the new features, changes to existing features, bug fixes, infrastructure changes and everything that might be needed in the product.
The Sprint Backlog is timeboxed plan consisting of the product backlog subset that a team targets to deliver during a given period in order to meet the sprint goal.
Backlog refinement is a regular pre-planning session for keeping the backlog updated and ensuring that the items at the top are at the right granularity for the next few sprints.
The Story Mapping invented by Jeff Patton is a way to envisage the entire product or service backlog as a series of user activities in rough order of priority. ScrumDesk is one of few tools supporting this method in STORY MAP module.
The User story has two meanings in agile comapnies. Originally it is a format of requirements thatIt answers the questions What? For Who? And Why? It is also the smallest unit of the requirement delivering a business value in an agile framework.
The sprint planning is a regular start point session in order to clarify the backlog items and identify the impediments and dependencies. The result of this session is the sprint kanban board that contains selected backlog items (the sprint backlog) typically broken into subtasks which might be assigned and estimated. The team should always check their capacity and velocities prior the commitment.
The Sprint Retrospective is a regular feedback session of the scrum team at the end of the current sprint in order to improve continuously. It is lead by ScrumMaster and the whole team, including the product owner, participates. ScrumDesk supports retrospectives by 14 retrospective techniques.
During the Sprint Review, an informal session, the team and stakeholders collaborate about what was done in the sprint in order to improve the product. With ScrumDesk users can easily generate the final sprint report that can be used in the Sprint Review session.
The Task board is used by individuals or teams to track the work path toward completion. It contains backlog items and usually subtasks necessary to complete to deliver backlog items. There might be more types of backlog items and subtasks. The task board represents the sprint backlog in Scrum.
The Burn Down chart is a graphic representation of the rate at which work is completed and how much work remains to be done. It is the primary Scrum agile metrics used for prediction of commitment delivery. Some teams use burndown chart to measure even mid-term plans realization via release (program increment) burndown charts.
The Definition of Done is criteria for accepting user story as completed. It is an agreement between the team, the product owner and stakeholders. ScrumDesk supports the Definition of Done via story templates that speed-up the process of planning and make DoD consistent.
The sprint in Scrum is a period (mostly not longer than 3 weeks) during which the team produces an increment towards the product completion. The sprint backlog is completed.
The sprint goal is a sprint objective met through the implementation of Sprint Backlog. It is defined by the product owner but focused on the iteration. It should be the business-oriented sentence.
The INVEST principle is a simple abbreviation created to remember an accepted set of criteria to assess the quality of a user story, which should be Independent, Negotiable, Valuable, Estimable, Small and Testable. This principle helps product owners to properly specify requirements, user stories.
MVP is the product, which has enough core features to be effectively deployed as soon as possible.
There are multiple meanings of the word Kanban. Originally it means “a card”. To understand the process deeply, visualization and transparency are necessary. That’s the reason for having everything that needs to be done place on the card. Kanban card.
In the software industry, Kanban is an agile framework for continuous development and delivery, moving a small number of tasks fluidly to completion.