Prioritization
The Prioritization pattern creates elements and a Kanban diagram allowing items that appear in the Kanban board to be prioritized. Elements can be dragged and dropped to new locations in the board including from lane to lane and within a lane. A Kanban board can be connected to other boards creating a powerful and flexible workflow.

Figure 1. Shows a Kanban diagram with a Backlog lane that can be used to prioritize any number of different types of items including Features, User Stories, Requirements and more.
Discussion
The purpose of the pattern is to allow elements to be prioritized and tracked during the execution of an initiative. The Kanban board allows element priorities and progress through a process to be visualized by all team members. Resource allocation and progress to completion can be made visible with the presence of progress bars at the bottom of each element.

The Kanban boards are used extensively throughout an initiative and can be used in a true Kanban style process or an iterative and incremental process such as Scrum or Scrumban with time boxed iterations such as Sprints.

The following is a list of some things you may want to do when working with this pattern.
·	Rename the diagram to suit the initiative.
Rename the Features to suit the initiative including adding notes and other properties.
Add other element types to the Kanban Board including User Stories, Requirements, Defects, Issues and other elements.
The following is a list of some of the next steps available when applying the pattern.
·	Adjust the names of the lanes in the Kanban board.
Add additional boards to create a more elaborate workflow.
Change the Work in Progress limits to reflect the capacity of the teams.
Create documentation automatically from the repository using built-in or user defined templates.
Reference
The following help topics will assist you learn about how to work with this pattern.
Prioritization
Kanban
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

The following are some of the tools that will be helpful when working with this pattern.
Kanban
Kanban diagrams can be used to manage a wide range of items in Enterprise Architect including User Stories, Requirements, Defects, Issues, Risks and more. The facility provides one or more Kanban boards that can be related to each other in a visually compelling and easy to work with tool. Workflows can be created that allow the management of items by different groups including product managers managing backlogs and implementation teams managing development teams. For more details see the Kanban help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.