Agile Development is a general term that includes a number of software development methodologies, including Extreme Programming, Scrum, Crystal, Lean Development, Dynamic Systems Development Method (DSDM) And Feature-Driven Development (FDD). Kanban is often referred to as Agile methodology, as it was often used together with Scrum principles, but it was actually developed by Toyota back in the 1950s. Til trods for at hver metodologi har en unik tilnærming og bestemte prinsipper, har alle lignende egenskaper som fleksibilitet, lyshet, fokus på konstant utvikling og målretning. Today we would like to cover Scrum and also Scrum hybrid with Kanban.
In these latter days, Scrum is one of the most popular frameworks and it is widely used by IT companies all over the world. Talking about "Agile" people often mean Scrum, but what is Scrum in practice?
Scrum is widely applied by software development teams and according to "The 9th Annual State of Agile Report" 72% of software teams use Scrum Or Scrum's hybrid. Talking about hybrids companies often combine it with Kanban or Lean practices.
How can Scrum be distinguished from Agile? – Scrum is een subgroep of Agile en Agile Development is een set van begeleidende concepten, 12 principes, en waarden voor implementatie van agile projecten, Scrum loopt deze waarden en principes van Agile en bovendien is het mogelijk om verschillende technieken en processen binnen dit
The significant components of Scrum Development: Role, Events, Artifacts, and Rules.
Scrum key roles are:
· Development Team is een zelf-georganiseerde cross-functional groep van professionals die typisch bestaat uit 7 -9 members and whose work consists in delivering suitable for release increments.
· ScrumMaster as a servant leader and facilitator for the Development Team, Product Owner, and Organization, who coaches the Scrum Team, ensu Scrum events include:
· The Sprint is a time-box limited to one.
· Sprint Planning is a time-boxed meeting of the entire Scrum Team which results in the work agenda for the oncoming Sprint.
· The Daily Stand-Up is a 15-minute event for the Development Team, which is held at the same place and time every day and during which team aligns activities and draws up a plan for the next 24-hours.
· The Sprint Review is a time-boxed meeting at the end of the Sprint within which the Scrum Team and stakeholders review the Increment and customize the Product Backlog if necessary.
· The Sprint Retrospective takes place After the Sprint Review and before the next Sprint Planning And during this time the Scrum Team should inspect itself and make a plan for improvements to be implemented within the upcoming Sprint.
· Product Backlog is a Runtime ordered list of all that might be needed in the product and it is a sole source of requirements for any changes to be applied to the product.
· Sprint Backlog is a set of items from Product Backlog selected for the Sprint with a plan. The Sprint Backlog is a set of items from Product Backlog selected for the Sprint with a plan. Voor het creëren van het product Increment and implementing the Sprint Goal. In deze manier, de ontwikkelingsgroep maakt een voorspelling over welke functionele mogelijkheden zullen worden opgenomen in de opkomende increment.
· Increment is het totaal van alle items van Product Backlog die werden geleverd binnen de Sprint en de som van All the preceding Sprints' Increments.
In comparison with Scrum, Kanban is much more flexible and less structured; Besides its principles, it can be easily combined with any actual practice that you already adhere to, even Scrum. For this and other reason Kanban is often mixed with Scrum and usually applied by larger teams. Initially, Kanban dropped out of Lean Manufacturing Techniques in the 1950s, but somewhere in 2007, it was adapted for knowledge work, like software development, DevOps, etc.
Kanban is introduced to match the amount of work in progress with Team's capacity, which provides more flexibility, faster delivery, better visibility and clear goal orientation. All the work is organized on Kanban board with usually five states (columns): product backlog (to-do), in progress, testing, ready to release and released. Den største betingelsen er Limit of Work in Progress (WIP Limit), og det bør være forudindstillet for hver kolonne på tavlen. It is important to note that if one of the columns is full, then new items can not be added to the state. In addition, the whole team should work on clearing up the impediment.
In Base, Kanban is built on 4 main principles:
· Visualization of the workflow – allows to observe the flow and all stages of an item in Kanban system, from request to completion.
· Begrensningen av arbeidet i gang (WIP) – hjelper til med å balansere arbeidsflyten på hver stat, fordi nye elementer blir rullet inn bare når den bestemte WIP limit is with. Limiting WIP is the heart of Kanban methodology.
· Focus, manage and improve the flow – adherence to the foregoing principles helps to follow the system, analyze, optimize and improve it. This process is never complete.
· Continuous improvement – Kanban methodology requires constant analysis, monitoring and measurement of productivity by tracking efficiency, quality, flow, etc.
The main distinguishing Features or Kanban are:
· No role, like Product Owner or Scrum Master
· Continuous delivery without time-boxed sprints
· Flexibility and ability to make Changes at any stage
Application of Kanban can bring such benefits as:
· Features are delivered faster due to shorter work cycles
· Decreases the amount of waste and removes those events that do not deliver value to organization or team
Both Scrum and Kanban proved themselves to Be efficient and mature framewo Rks that can help companies to develop and succeed in their industries. Different approaches can work in a worthwhile manner at different times, so while making a decision, ask what aspects and principles of Scrum and Kanban can be applied with your teams to effectively deliver products and services.
Source by Eugeniya Korotya