Scrumban methodology

    Scrumban was originally intended to be used for transitioning from Scrum to Kanban. Nowadays, it is used as a standalone framework in Agile management sets of methodologies, being successfully used by the IT teams.

        According to Wikipedia, Scrumban is distinct from Scrum by:

• recognizing the important role of organizational management (self-organization remains an objective, but within the context of specific boundaries)
• allowing for specialized teams and functions
• applying explicit policies around ways of working
• applying the laws of flow and queuing theory
• deliberate economic prioritization

and it is distinct from Kanban in that it:

• prescribes an underlying software development process framework (Scrum) as its core
• is organized around teams
• recognizes the value of time-boxed iterations when appropriate
• formalizes continuous improvement techniques within specific ceremonies

    Its main principles and terminology are as follows:

• Iterations
• On-demand planning
• Prioritization
• Bucket size planning
• The board
• WIP limits
• To Do limits
• The team
• Pull principle
• Feature freeze
• Triage

    If you need details on these and even more, you can read these articles:

• Scrum vs. Kanban vs. Scrumban
• Scrumban - The best of Kanban and Scrum
• Scrumban Core Principles - Cards, Cells & Workflows
• Where Scrum Falls Short, Scrumban Comes To Rescue