Skip to main content

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.

Comments

Post a Comment

Popular posts from this blog

Copy Jira dashboards to Confluence pages

 New feature On June 4th, Atlassian announced new feature which is Jira dashboard smart links. How does it work? You create a dashboard (previously you define who can view it and edit it), you click on the attachment icon by the star, paste it to your Confluence page and your dashboard appears there. You cannot edit the content from Confluence page, as it is read only. This feature adds more efficiency and overview for the stakeholders who like to see more documented format of the reports.  Everything is centralized, so there is no need to jump between these two products, because time is valuable. Or should I say, time is money.  Source: https://community.atlassian.com/t5/Jira-articles/Share-reports-and-project-updates-with-Jira-dashboard-Smart/ba-p/2717627 With just few clicks, add your Jira dashboards to your Confluence page with ease.
Post a Comment
Read more

Company vs team managed projects in Jira

 What are those? Company managed projects No, these projects are not created by the company. These projects can ONLY be created by Jira admins. Who is a Jira admin? Jira admin is a power user who has permissions with higher privilege. They can see every single project, board, dashboard on your Jira site. Let us now mention some perks of company managed projects: You can have multiple boards from different projects - these boards include both Kanban and Scrum boards There are more report options especially for Epics and Versions They can share the configurations with other projects - careful though! If you change configuration on one project, it may change the configuration with other projects as well Screens, fields, workflows, notifications are managed through schemes Company managed Kanban boards have sub-filters, releases, option to hide the issues after 2,3 or custom weeks Project administrators are only allowed to change the issue layout in company managed projects   Team managed
Post a Comment
Read more

Filters in Jira

 What the f are filters in Jira? Lets say that you would like to adopt a cat (sorry dog lovers!). You go to the cat shelter. You look around and see lots of different breeds of cats: siamese, blue russian cat, short hair british, and etc. You are looking for a specific cat that is not older than a year, that is calmer than the other cats (trust me, there are no calm cats - especially if they sleep all day, brace yourself - they will awake you at 3 am), an orange cat (like a garfield almost), not really heavy (because there are heavy cats).  All of this from above is almost the same thing when developers are filtering the issues in Jira. Each board in Jira is based on a specific JQL filter. Also, these filters can be controlled in a way, you can select (if you are the board administrator) who will be able to view and who will be able to edit the filter. In order to keep the developers focused (they are the coding folks without whom we wouldn't have anything really), quick filters ca
Post a Comment
Read more