Motivation:<\/strong> We will use this pattern when we want to detail the tasks to be done to make up a process. With this pattern we want to focus on the task list, not in the state of each task at each moment (as in a Kanban). One of the most frequent uses of this pattern is enumerating all the steps (tasks) that we have to do for make up a step of a project, represented in the lists. When we complete all tasks of all lists, we would have completed the project.<\/p>\n\n\n\n Solution and graphic representation:<\/strong>\u202f Each list represents a phase of the process that we are representing with the whole board. Cards are the tasks of each phase. In this way, we will provide the user a sequenced guide for completing the process, as the steps of a recipe.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to “Kanban<\/a>“, but in this pattern the cards don\u2019t flow between lists. We will choose “Kanban<\/a>” if we want to focus on the evolution of each card, while we will choose \u201cProcess Task\u201d if we want to have \u201cto-do\u201d lists of tasks for each phase of the project, following a determined order, but without managing its evolution with the time.<\/p>\n\n\n\n \u201cProcess Tasks\u201d is also similar to \u201cCategorized Tasks<\/a>\u201d, with the difference that in the first pattern the lists follow an established order (in the two examples showed above, this precedence is temporal), while in the second one, they generally represent independent topics, without relationship or precedence between them.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we are representing the six phases in which the project is divided. In each list we have all the task that we have to do for completing the phase. Phases are ordered, in this case, temporarily, by the time in real life that each phase occurs and their precedences (Pre-Sprint Prep is before Understand, Understand is before Diverge…)<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problem:<\/strong>\u202f Situations or projects in which we have to provide a sequenced tasks guide, divided and ordered according to the different stages that make up the process.<\/p>\n\n\n\n Motivation:<\/strong> We will use this pattern when we want to detail the tasks to be done to make up a process. With this pattern we want to focus on the task list, not in the state of each task at each moment (as in a Kanban). One of the most frequent uses of this pattern is enumerating all the steps (tasks) that we have to do for make up a step of a project, represented in the lists. When we complete all tasks of all lists, we would have completed the project.<\/p>\n\n\n\n Solution and graphic representation:<\/strong>\u202f Each list represents a phase of the process that we are representing with the whole board. Cards are the tasks of each phase. In this way, we will provide the user a sequenced guide for completing the process, as the steps of a recipe.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to \"Kanban<\/a>\", but in this pattern the cards don\u2019t flow between lists. We will choose \"Kanban<\/a>\" if we want to focus on the evolution of each card, while we will choose \u201cProcess Task\u201d if we want to have \u201cto-do\u201d lists of tasks for each phase of the project, following a determined order, but without managing its evolution with the time.<\/p>\n\n\n\n \u201cProcess Tasks\u201d is also similar to \u201cCategorized Tasks<\/a>\u201d, with the difference that in the first pattern the lists follow an established order (in the two examples showed above, this precedence is temporal), while in the second one, they generally represent independent topics, without relationship or precedence between them.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we are representing the six phases in which the project is divided. In each list we have all the task that we have to do for completing the phase. Phases are ordered, in this case, temporarily, by the time in real life that each phase occurs and their precedences (Pre-Sprint Prep is before Understand, Understand is before Diverge...)<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problema<\/strong>: Situaciones o proyectos en los que necesitamos una gu\u00eda de tareas secuenciadas, divididas y ordenadas seg\u00fan las diferentes etapas que componen el proceso.<\/p>\n\n\n\n Motivaci\u00f3n<\/strong>: Usaremos este patr\u00f3n cuando queramos detallar las tareas a realizar para llevar a cabo un proceso. Con este patr\u00f3n nos centraremos en la lista de tareas, no en el estado de cada tarea en cada momento (como en Kanban<\/a>). Uno de los usos m\u00e1s frecuentes de este patr\u00f3n es enumerar todos los pasos (tareas) que tenemos que realizar para completar un paso de un proyecto, representados en las listas. Cuando completemos todas las tareas de todas las listas, habremos completado el proyecto.<\/p>\n\n\n\n Soluci\u00f3n y representaci\u00f3n gr\u00e1fica<\/strong>: Cada lista representa una fase del proceso que estamos representando en el tablero. Las cartas son las tareas de cada fase o etapa. De esta forma, proporcionaremos al usuario una gu\u00eda secuenciada para completar el proceso, como si fueran los pasos de una receta.<\/p>\n\n\n\n Patrones Relacionados:<\/strong><\/p>\n\n\n\n Este patr\u00f3n es bastante similar a \"Kanban<\/a>\", pero en \"Process Tasks\" las cartas no fluyen entre listas. Elegiremos \"Kanban<\/a>\" si queremos centrarnos en la evoluci\u00f3n de cada tarea, mientras que elegiremos \"Process Tasks\" si queremos tener listas de tareas \"por hacer\" para cada fase del proyecto, siguiendo un orden determinado , pero sin gestionar su evoluci\u00f3n con el paso del tiempo en la vida real.<\/p>\n\n\n\n \u201cProcess Tasks\u201d tambi\u00e9n es similar a \u201cCategorized Tasks<\/a>\u201d, con la diferencia de que en el primer patr\u00f3n, las listas siguen un orden establecido, mientras que en \"Categorized Tasks<\/a>\", generalmente representan temas independientes, sin relaci\u00f3n, ni orden, ni precedencia entre ellos.<\/p>\n\n\n\n Ejemplo:<\/strong><\/p>\n\n\n\n En esta plantilla representamos las seis fases en las que se divide el proyeceto. En cada lista tenemos todas las tareas que debemos realizar para completar dicha fase. Las fases (listas) est\u00e1n ordenadas, en este caso, temporalmente, siguiento el orden en que se realizar\u00edan en la vida real y sus respectivas precedencias (\"Pre-Sprint va antes que \"Understand\", \"Understand\" antes que \"Diverge\"...).<\/p>\n\n\n\n Ejemplos de Plantillas de Trello:<\/strong><\/p>\n\n\n\n Problem:<\/strong>\u202f Situations or projects in which we have to provide a sequenced tasks guide, divided and ordered according to the different stages that make up the process.<\/p>\n\n\n\n Motivation:<\/strong> We will use this pattern when we want to detail the tasks to be done to make up a process. With this pattern we want to focus on the task list, not in the state of each task at each moment (as in a Kanban). One of the most frequent uses of this pattern is enumerating all the steps (tasks) that we have to do for make up a step of a project, represented in the lists. When we complete all tasks of all lists, we would have completed the project.<\/p>\n\n\n\n Solution and graphic representation:<\/strong>\u202f Each list represents a phase of the process that we are representing with the whole board. Cards are the tasks of each phase. In this way, we will provide the user a sequenced guide for completing the process, as the steps of a recipe.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to \"Kanban<\/a>\", but in this pattern the cards don\u2019t flow between lists. We will choose \"Kanban<\/a>\" if we want to focus on the evolution of each card, while we will choose \u201cProcess Task\u201d if we want to have \u201cto-do\u201d lists of tasks for each phase of the project, following a determined order, but without managing its evolution with the time.<\/p>\n\n\n\n \u201cProcess Tasks\u201d is also similar to \u201cCategorized Tasks<\/a>\u201d, with the difference that in the first pattern the lists follow an established order (in the two examples showed above, this precedence is temporal), while in the second one, they generally represent independent topics, without relationship or precedence between them.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we are representing the six phases in which the project is divided. In each list we have all the task that we have to do for completing the phase. Phases are ordered, in this case, temporarily, by the time in real life that each phase occurs and their precedences (Pre-Sprint Prep is before Understand, Understand is before Diverge...)<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n![\"process](\"https:\/\/user-images.githubusercontent.com\/47741431\/110808758-96122e80-8284-11eb-9d0b-9b7a12452d2c.png\")
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPattern:\u202fPROCESS TASKS<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPatr\u00f3n:\u202fPROCESS TASKS<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPattern:\u202fPROCESS TASKS<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\n