Backlog Management
The Backlog Management pattern creates two Kanban boards that can be used together as a workflow with two parts: a Backlog Board and a Development Board. Items can be added from the toolbox or the Project Browser and moved between lanes and between the two boards.

Figure 1: Part of the Backlog Board showing the three lanes that can be used to drag-and-drop items. They can also be moved to another Development Board with its own lanes.
Discussion
The goal is to allow items (Features, User Stories, Defects Changes and more) to be visualized as they move through a workflow from being considered as part of a Backlog through to being fully deployed. The elements that appear on the boards can be elaborated in other diagrams and connections can be made to a range of up-stream elements such as business requirements, business process and down-stream elements such as Components and Services.

This pattern is used when you want to manage the Backlog as a separate board. In contradistinction to a one stage workflow items in the backlog can be moved between the lanes on the backlog board to indicate priority. Once the items reach the critical lane they can be dropped on the Development Drop target which will place them into the first (Queue) lane of the development board - indicating they are ready for development work to begin.

The following is a list of some things you may want to do when working with this pattern.
·	Rename the items in the diagram to suit your initiative.
New items can be dragged onto the diagram from the Toolbox or the Project Browser.
Items can be moved between lanes on the Backlog Board to change their Priority.
Items can be moved from the Backlog Board to the Development Board by dropping on the Drop Target at the far right of the Backlog Board.
Items can be moved between lanes to indicate their position in the workflow.
Items can be moved from the Development Board back to the Backlog by dragging them to the Backlog Drop Target at the far right of the board.
One or more Resources can be allocated to an item on either board by Selecting Resource Allocation from the Task Management Panel of the Construct Ribbon.

The following is a list of some of the next steps available when applying the pattern.
·	Grooming Requirements and Defects -As the items move across the backlog board towards critical or are moved to the Queue lane of the Development Board they can be groomed for development work.
Resource Allocation - Resources can be added to items indicating who is doing the work and what stage of completion it is at, more details can be viewed in the resource allocation window.

·	Dashboards and Charts - Expressive visualizations can be achieved by creating Dash Boards and Charts that help to show the management of items in the Backlog.
Reference
The following help topics will assist you learn about how to work with this pattern.
Kanban Features
Allocating Resources to Work Items
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.
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.