Page History

* we just capture info and we do not share it

 
* no review process

* we do n ot have a one stop shopping place

* no standarzed place to store

* no common practices, or standardized processes or procedures

* Agile... no formal LL

** "How can we do it better"

  interative
** @ end of project we do LL for Project 
** sprint review ( should we capture the information ) 
** process capture and std meeting at same time during day
* we need to capture project independent processes that are "Best Practices" 
* technical vs. people problems or practices
* PM lessons learned vs Technical 
* LL can be for everybody and the container should be coming from Developer and PM 
* Sharing the outcome need to be done , the mechanism and the place needs to be disseminated

h3. Possible ways to approach the problems
* must be categorized and search and find 
* tracker in SF and groups and , you can monitor it 
* we say let anybody enter LL and we may need to "cull" the LL if we get to many IS wide 
* LL by project , but we do not want to just limit it to project function
* possibly create a SF project that is called "LL Knowledge Base" and exploit the Tracker to capture the the info
** advantages , email to create LL 
** email notification of new entries

h3. Tool must haves
* flexabiliy
* SF tracker 
* simple , easy to create the documents and 
* show the value by use 
* email notification (subscription capabilities) 
* Elements of the actual document to capture LL
** categorization (up to 3) 
** full texted indexed
** containerize for documents, spreadsheet,s
** free form text field

h3. care and feeding and promotion
* will need to have a LL adminitrator to manage the tool & data
* communication of tool needs to be done
**  @ meetings
** word of mouth 

h3. next steps