Motivation:<\/strong> We will use this pattern for having a quick view of how the information is structured, focusing on the categories in which it is clasified. One of the most frequent uses of this pattern is the storage of static information without any type of order, as for example, indexing it by its topic. In this way, we will use the board as a notebook where an alumn writes notes of each subject, organizing it by course, for example.<\/p>\n\n\n\n Solution and graphic representation:<\/strong>\u202fEach list represent a different topic where we will store the information, represented in the cards. Lists and topics must be independent, isolated and without order between them (sequenced steps, for example). Information will be stored in one list, only one, and always the same. This pattern will provide the user a topic-structured template to organize its information.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is similar to \u201cCategorized Tasks<\/a>\u201d as they differ from each other in which they represent: information and tasks respectively. Both are a similar way of showing relevant things about a project. With the first one we will emphasize in the information or notes of each phase, while with the second one we will see which tasks do we have to do for completing each step.<\/p>\n\n\n\n The main difference between this pattern and \u201cOrdered Information<\/a>\u201d is the presence or abscence of order between the lists of the board. Both represent static information, but we will choose one or another depending on whether the resources are prioritized or hierarchical in some way.<\/p>\n\n\n\n Regarding to \u201cAssigned information<\/a>\u201d pattern, we will choose one or another depending on wheter the information changes with the time or not. \u201cCategorized information\u201d is usually used to store information by a phase of the project or a topic, because this feature will not change its value (card will be stored always in the same list), while in \u201cAssigned information<\/a>\u201d it is more frequent to represent people as lists, allowing the user to move cards from one person to another.<\/p>\n\n\n\n As commented in “Kanban<\/a>” description, both patterns are frequently used combined with each other. In the \u201cpart\u201d of \u201cCategorized information\u201d we will represent useful information for understanding the process, while in the \u201cKanban<\/a> part\u201d of the board we will have the tasks needed to complete the process, improving the utilities of both patterns separately.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we have five lists, where the first one contains the explanation of use of the board and the other four lists. In these other four lists we will information divided by topic, using the lists \u201cProduct & Report\u201d and \u201cPayment & Delivery\u201d as two FAQs sections. \u201cDiseases\u201d list contains a large number of illness explained, while in \u201cRequests” we will seek an answer for customer requests and add new articles\/cards for future.<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problem: <\/strong>Situations or projects in which we need to categorize information by any criteria, when information does not change its category over time.<\/p>\n\n\n\n Motivation:<\/strong> We will use this pattern for having a quick view of how the information is structured, focusing on the categories in which it is clasified. One of the most frequent uses of this pattern is the storage of static information without any type of order, as for example, indexing it by its topic. In this way, we will use the board as a notebook where an alumn writes notes of each subject, organizing it by course, for example.<\/p>\n\n\n\n Solution and graphic representation:<\/strong>\u202fEach list represent a different topic where we will store the information, represented in the cards. Lists and topics must be independent, isolated and without order between them (sequenced steps, for example). Information will be stored in one list, only one, and always the same. This pattern will provide the user a topic-structured template to organize its information.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is similar to \u201cCategorized Tasks<\/a>\u201d as they differ from each other in which they represent: information and tasks respectively. Both are a similar way of showing relevant things about a project. With the first one we will emphasize in the information or notes of each phase, while with the second one we will see which tasks do we have to do for completing each step.<\/p>\n\n\n\n The main difference between this pattern and \u201cOrdered Information<\/a>\u201d is the presence or abscence of order between the lists of the board. Both represent static information, but we will choose one or another depending on whether the resources are prioritized or hierarchical in some way.<\/p>\n\n\n\n Regarding to \u201cAssigned information<\/a>\u201d pattern, we will choose one or another depending on wheter the information changes with the time or not. \u201cCategorized information\u201d is usually used to store information by a phase of the project or a topic, because this feature will not change its value (card will be stored always in the same list), while in \u201cAssigned information<\/a>\u201d it is more frequent to represent people as lists, allowing the user to move cards from one person to another.<\/p>\n\n\n\n As commented in \"Kanban<\/a>\" description, both patterns are frequently used combined with each other. In the \u201cpart\u201d of \u201cCategorized information\u201d we will represent useful information for understanding the process, while in the \u201cKanban<\/a> part\u201d of the board we will have the tasks needed to complete the process, improving the utilities of both patterns separately.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we have five lists, where the first one contains the explanation of use of the board and the other four lists. In these other four lists we will information divided by topic, using the lists \u201cProduct & Report\u201d and \u201cPayment & Delivery\u201d as two FAQs sections. \u201cDiseases\u201d list contains a large number of illness explained, while in \u201cRequests\" we will seek an answer for customer requests and add new articles\/cards for future.<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problema<\/strong>: Situaciones o proyectos en los que necesitamos categorizar o clasificar la informaci\u00f3n por cualquier criterio, cuando la informaci\u00f3n no cambia su categor\u00eda con el paso del tiempo.<\/p>\n\n\n\n Motivaci\u00f3n<\/strong>: Utilizaremos este patr\u00f3n para tener una visi\u00f3n r\u00e1pida de c\u00f3mo est\u00e1 estructurada la informaci\u00f3n que deseemos manejar, centr\u00e1ndonos en las categor\u00edas en las que esta se clasifica. Uno de los usos m\u00e1s frecuentes de este patr\u00f3n es el almacenamiento de informaci\u00f3n est\u00e1tica, sin ning\u00fan tipo de orden, como por ejemplo, clasific\u00e1ndola por su tem\u00e1tica. De esta forma, usaremos el tablero como un cuaderno en el que un alumno escribe los apuntes de cada asignatura, organiz\u00e1ndola por cursos, o materias disjuntas entre s\u00ed, por ejemplo.<\/p>\n\n\n\n Soluci\u00f3n y representaci\u00f3n gr\u00e1fica<\/strong>: Cada lista representa un tema diferente, donde almacenaremos la informaci\u00f3n, representada en las tarjetas. Las listas y temas deben ser independientes, aislados y sin orden preestablecido entre ellos (etapas secuenciadas, por ejemplo). La informaci\u00f3n se almacenar\u00e1 en una lista, solo una y siempre la misma. Este patr\u00f3n proporcionar\u00e1 al usuario una plantilla estructurada por temas para organizar y almacenar su informaci\u00f3n.<\/p>\n\n\n\n Patrones relacionados:<\/strong><\/p>\n\n\n\n Este patr\u00f3n es similar a \u201cCategorized Tasks<\/a>\u201d ya que se diferencian entre s\u00ed \u00fanicamente en lo que representan: informaci\u00f3n y tareas respectivamente. Ambos son una forma similar de mostrar cosas relevantes sobre un proyecto. Con el primero destacaremos la informaci\u00f3n o anotaciones de cada fase, mientras que con el segundo veremos qu\u00e9 tareas tenemos que hacer para completar cada etapa.<\/p>\n\n\n\n The main difference between this pattern and \u201cOrdered Information<\/a>\u201d is the presence or abscence of order between the lists of the board. Both represent static information, but we will choose one or another depending on whether the resources are prioritized or hierarchical in some way. En cuanto al patr\u00f3n de \u201cAssigned information<\/a>\u201d, elegiremos uno u otro en funci\u00f3n de si la informaci\u00f3n cambia con el paso del tiempo o no. \u201cCategorized Information\u201d se suele utilizar para almacenar informaci\u00f3n clasificada por su tema, porque esta caracter\u00edstica no cambiar\u00e1 su valor (la carta se almacenar\u00e1 siempre en la misma lista), mientras que \u201cAssigned information<\/a>\u201d es m\u00e1s frecuente para representar personas como listas, lo que permite al usuario mover las tarjetas de una persona a otra tal y como cambie su asignaci\u00f3n en la vida real.<\/p>\n\n\n\n Como se comenta en la descripci\u00f3n de \"Kanban<\/a>\", ambos patrones se utilizan frecuentemente combinados entre s\u00ed. En la \u201cparte\u201d de \u201cCategorized Information\u201d representaremos informaci\u00f3n \u00fatil para entender el proceso o los recursos asociados al mismo, mientras que en la \u201cParte Kanban<\/a>\u201d del tablero tendremos las tareas necesarias para completar dicho proceso, mejorando las utilidades de ambos patrones por separado.<\/p>\n\n\n\n Ejemplo:<\/strong><\/p>\n\n\n\n En esta plantilla tenemos cinco listas, de las que la primera de ellas contiene la explicaci\u00f3n textual del uso del tablero. En las otras cuatro listas tenemos informaci\u00f3n dividida por tema, donde \"Product & Report\" y \"Payment & Delivery\" son dos listas con respuestas a preguntas frecuentes (FAQs). La lista \"Diseases\" contiene un gran numero de enfermedades con sus correspondientes explicaciones, mientras que en la lista \"Requests\" podremos buscar respuestas a las peticiones de los clientes y a\u00f1adir nuevos art\u00edculos\/cartas de cara al futuro.<\/p>\n\n\n\n Ejemplos de Plantillas de Trello:<\/strong><\/p>\n\n\n\n![\"categorized](\"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:\u202fCATEGORIZED INFORMATION<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPatr\u00f3n:\u202fCATEGORIZED INFORMATION<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n
La principal diferencia entre este patr\u00f3n y \u201cOrdered Information<\/a>\u201d es la presencia o ausencia de orden entre las listas del tablero. Ambos patrones representan informaci\u00f3n est\u00e1tica, pero elegiremos uno u otro en funci\u00f3n de si los recursos est\u00e1n priorizados, ordenados o jerarquizados de alguna forma.<\/p>\n\n\n\n<\/figure><\/div>\n\n\n\n