Choosing which agile methodology to use is a very common question. There is vast content available showing how to implement application experiences and support materials. Approaches of joining methodologies exist, such as ScrumBan, but I have always felt a lack of open mindedness to use a mix of two or more methodologies/methods.
Don't grab onto some methodology as if it were an idol. Putting the manual under your arm can make you inflexible and miss the opportunity to try other methods.
Therefore, I believe that being open to adopting part of one or another technique/methodology, even if adapting it, can bring many benefits. There is no correct answer to questions like “which is better, SCRUM or Kanban or another?”
About the Author
João Muniz is passionate about technology and innovation. He believes that adaptability is the key word these days.
Professional with more than 15 years of experience in IT as a software developer, system analyst and, for a few years now, as a Scrum Master.
With an academic background in IT, specialization in Software Engineering and an MBA in Business Process Management. In recent years, João has dedicated himself to deepening his knowledge of Agile. Getting certifications like Professional Scrum Master I (PSM I) from Scrum.org, Kanban System Design (KMP I) from Kanban University and SAFe Agilist from Scale Agile. It has been experiencing and contributing to the digital transformation movement of a large organization in Latin America. Opportunity that became a school in learning and practice in the use of methodologies, techniques and tools.