\nWorkflow has various meanings, but one idea is that it’s a series of states a job or artifact passes through in order to be transformed to a finished product.<\/p>\n
\nA classic workflow might include three states: To Do, In Progress, and Done. Kanban and Scrum are two different workflows that can be modeled that way. In that case, what’s their difference?<\/p>\n
\nA Scrum workflow has a definite start and end date. Philosophically, it begins with all the To Dos it will have; subsequent To Dos will be taken up in a different Scrum.<\/p>\n
\nA Kanban workflow is open-ended, timewise. Philosophically, Kanban tries to minimize the number of tasks in play at any instant. However, new To Dos can be added to replace tasks that are Done.<\/p>\n
\nSource:<\/p>\n
\natlassian.com<\/a><\/p>\n atlassian.com<\/a><\/p>\n YouTube: Simon Sez It: Jira Tutorial for Beginners: Jira Project Management<\/a><\/p>\nJack of Oracle Tutoring by Jack and Diane,<\/a> Campbell River, BC. \n","protected":false},"excerpt":{"rendered":" Self-tutoring about modern business and comp sci terms: the tutor mentions Kanban and Scrum. Workflow has various meanings, but one idea is that it’s a series of states a job or artifact passes through in order to be transformed to …<\/p>\n