Lessons Learned
The Lessons Learned pattern creates a diagram with a link to the Team Library facility which allow you to store lessons learnt information inside the repository in the form of a Document Artifact or by linking to external resources.

Figure 1. Shows a diagram that contains a link to the Team Library window. Double-clicking the link will open the Team Library window where you can define Lessons Learnt in a document based facility.

Figure 1.Show a screen shot of an Example Team Library window. You will need to add Categories and Topics to suite the initiative.
Discussion
The purpose of the pattern is to allow Project Managers Scrum Master and other stakeholders to create and view a document that records the lessons learnt.

It is typically used at a project milestone which could be the completion of the project itself or one of its iterations such as a Sprint or it could be conducted at some other significant milestone. It can include the following:
·	Successes that have been achieved.
Failures that have been detected.
Recommendations for improvement.
Opportunities that exist.

The following is a list of some things you may want to do when working with this pattern.
·	Create your own Categories in the Team LIbrary window.
Create any number of topics under the Category heading.
Create documents that describe the lessons learnt.

The following is a list of some of the next steps available when applying the pattern.
·	Add links to model Packages, Diagrams and Elements by dragging element from the Project Browser onto a Topic.
Share the document with users of other repositories.
Change the status of the topics.
Bind a Topic to a Project Browser Package.
Reference
The following help topics will assist you learn about how to work with this pattern.
Lessons Learned
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.