Archives for

Top 10 Questions About Scrum and Their Answers

Scrum-FAQ

Undoubtedly, there is no lack of information about Scrum and how it should be used. Articles, to do lists, mistakes, user cases and anything else you might think of can be reached in minutes. However, when you are just coming into a new approach and learning its ways, you will most likely have certain questions and struggle to find the answers.

To help you out in this situation, here are the most common questions new users have about Scrum and their answers.

Is Scrum Agile?

This is one of the most frequent questions from new practitioners and one that cannot be answered with a single yes or no. Scrum is part of the Agile family, as it is one of the frameworks used to realize Agile rules and principles in real life projects. Other Agile applications, such as Kanban, XP and others are simply other frameworks used to bring Agile values to life. So yes, Scrum is Agile but Agile is not just Scrum, it is much more.

Should I choose Scrum?

Read More

Top 5 Most Interesting Scrum Boards

Scrum board is one of the most essential tools to ensure a smooth project and while most choose the traditional scrum boards for their teams, there are a few that decide to innovate and improve the traditions to fit their needs. Therefore this week we gathered up the 5 most interesting (at least to us) boards and present them to you!

The wall

The first example comes from Agile but Pragmatic. Instead of dealing with a traditional scrum board, they suggest to expand it into a whole wall. This allows the team to put additional information such as results of retrospective – decisions and actions to take in the current sprint, parking for not active tasks, the sprint calendar and other things. By dedicating the whole wall to the scrum board, the team expands their ability to have all the information in one place.

Scrum board wall

Source: Agile but Pragmatic.

Read More

Scrum vs. Kanban vs. Scrumban: Boards, Rules, and Who Should Use It

In the previous blog posts we discussed the team members, roles, work routines, planning, estimation, scope, and other aspects of Scrum, Kanban, and Scrumban.

There are a few other differences between the methodologies, which do not necessarily fall into one of the categories above. In this blog post we review the boards used in each case, prioritization, rules – and, most importantly – who should use which methodology.

Boards

The Scrum task board is defined and reset each sprint. As the backlog items move from backlog to completion during a sprint, and are planned separately for each sprint, the board is reset after the sprint is over.

Kanban and Scrumban boards remain persistent and are not reset, as there are no pre-set periods for backlog item completion.

Prioritization

Prioritization in Scrum is done through backlog. Therefore, the Scrum backlog is ordered and the most important items therefore end up being done first.

In Kanban, prioritization is optional. In Scrumban, prioritization is recommended during each planning.

Rules

Scrum is generally a constrained process, where the tasks are assigned to team members and bounded by deadlines. Therefore, Scrum is the most restrictive process of the three.

Kanban, on the other hand, has only a few constraints is a fairly flexible process.

Scrumban has a slightly constrained process and falls in between the two.

Who should use it?

While all three methodologies can be used in a variety of settings, there are a few aspects to take into account when considering whether to adopt different methodologies.

Scrum works well for large projects, and especially for projects with long-term maturity of more than a year. Therefore, Scrum is often chosen by enterprise teams seeking to make their process more effective.

Kanban has the unique ability to handle constant flow of incoming tasks, therefore it is often chosen by support and maintenance teams, or continuous product manufacturing – among other applications.

Finally, Scrumban is often used by fast-paced projects, as it combines the flexibility of Kanban with the basic features of Scrum. Therefore, it is often used in startups or, similarly to Kanban, where continuous product manufacturing is required.

It is however important to choose the process that works for you and customize it to fit your own requirements. Scrum, Kanban, and Scrumban are just tools to make you and your team more productive – and therefore use them the way it works for you and your team, not necessarily following every rule to the T. Good luck!

 

Read More