Popis metodiky ScrumBan a její zavedení v praxi

The goal of this diploma thesis was to describe the ScrumBan methodology, including its characteristics, as well as roles used during its implementation. The problem of this methodology lies in the lack of sources of relevant information, which are available on the subject in 2019, which could be the reason, why most companies which are considering a change in methodology, primarily chose Scrum or Kanban, which are significantly better described. When trying to understand the complex characteristics specific for this methodology, or practical guidance when deploying ScrumBan in real-life, there is currently no source of information which would provide guidance in all the areas mentioned. In actual fact the ScrumBan methodology is highly suitable for projects where in addition to software development, the target is also subsequent software maintenance, which could have a positive effect in that it motivates team members to write source code which is maintainable in the long-term and suitably efficient. I selected this topic because I implement agile methodologies as part of my job. The first chapter is dedicated to an analysis of the Scrum and Kanban methodologies on which ScrumBan is based. Next, the ScrumBan methodology itself is explained, including its specifics and advantages. This is followed by an analysis of the ScrumBan methodology using METES (a system used to support methodology selection based on how a company operates). Subsequently, the company Neoris is introduced, including an analysis of its internal operations. Next, the parameters (criteria) of Neoris are defined in the METES system. This is followed by a proposal of the methodology selection using METES (which is expanded to include the ScrumBan methodology). Based on the output from this model a transition from Scrum to ScrumBan in Neoris is performed.