Tag Archives: scrum

We said that the self-managed team chooses the way, to achieve the goals. But some set those goals. We are talking about business owners, customers, managers, etc. Scrum doesn’t deny their existence. But except for startups, these people are usually not directly part of the scrum team. Here it’s important not to get the concept […]

The last process left to consider is used only in exceptional cases (Sprint Cancellation). For example, during a sprint, it turns out that the requirements have changed so much that it makes no sense to implement the current stories. To avoid wasting resources, the product owner stops the sprint. All stories and tasks that pass […]

Agile Retrospective (Scrum) is not just about working on mistakes. It is a process aimed at continually improving the effectiveness of the team. Improvements can be about anything from workplace lighting to changes in team composition. It’s not a scrum invention. A continuous improvement cycle (called the Deming cycle) should work in any organization: Planning […]

Sprint Demo- is held on the last day of the sprint or the day after the end of the sprint. The first option is preferable. Don’t be afraid that you won’t have time to implement the entire backlog of the sprint because of meetings. After all, the team’s focus factor takes into account that some […]

A burndown chart is a sprint tool that is a metric for success. At the beginning of a sprint, you have a fixed amount of work in story points and a fixed number of days until the end of the sprint. Each day your team “burns through” some amount of work. If you graph this, […]

To visualize sprint progress in a scrum, a board is used that came from kanban. Kanban (kan-visual, ban-card, board) is a logistical tool of the Just In Time concept, which was introduced in the early 20th century in the Toyota concern and later in many other companies. Kanban is the cards that were in each […]

Daily Scrum. This process also called a scrum meeting, consists of getting the whole team together at a certain time each day and each taking turns to report back to the others. Daily Scrum. Entry: Report of each team member Output: An adjusted plan for achieving the script’s goals. Meeting for 15 minutes every day […]

Team velocity is a scrum metric that shows how much work a team does per sprint. The amount of work, as you remember, is measured in story points. Therefore, instead of the usual km/h, we will use SP/sprint as the unit of velocity. We need to predict the speed of the team to understand which […]

Estimate scrum planning process. To determine which stories a team will be able to accomplish in a sprint, you need to know how much work each story will require. Scrum uses a group tool called poker planning to estimate the amount of work. To do this, you don’t need a poker deck, as you might […]

Sprint planning – technical Stories. This is work to facilitate the creation and support of a product or service. Refactoring is the redesign of parts or even the entire product. It can be caused by errors in design, insufficient qualification of engineers, significant changes in requirements, lack of a unified development policy, accumulated “technical debt”, […]

  • 1
  • 2