Scrum vs Kanban

 Scrum

Agile framework where everyone is working as a team. The team does the estimations on the tasks and also distinguish the work. Work that is being distinguished and worked on within a specific time frame that shouldn't be longer than 2 weeks is called sprint. Time that is needed for a time to complete their work is called sprints. Don't get confused on this (sorry). Scrum has its artifacts (you've guessed that those are the ancient artifacts in the museum, not a bad idea). Instead, these artifacts include:

• Product backlog - the list of tasks that team is working on
• Sprint backlog - the list of tasks that team is working on within a current sprint (there is no limitation on number of sprints)
• Sprint planning - meeting where Scrum master and the team is gathering to determine which issues will go to which sprint 
• Daily stand up - each day (except weekends of course), team is gathering to answer 4 questions: what have you done yesterday? what you will do today? are there any blockers?
• Sprint review - the whole team including the stakeholders are presenting their craft where stakeholders are giving the feedback
• Sprint retrospective - scrum team gathers to discuss the good and the bad and how the team can improve

Kanban

Much more lightweight than Scrum. Kanban is all about flexibility and continuous delivery. It also is focused on improving the flow. It's all about limiting WIP (work in progress). Team is representing their work using the Kanban board (nowadays people use Jira, and you should too, its easy!).Kanban aims to reduce the time that is needed to finish the project from start to finish.Full transparency of work is something that describes this framework perfectly.

 

#scrum #kanban #agile