# Presentation: 702132

## EOS Pilot for Lessons LearnedWorking sub-GroupMeeting #12

**Paul Brandinger:  301-286-4571; Paul.Brandinger@gsfc.nasa.gov**

**EOS Pilot for Lessons Learned****Working sub-Group****Meeting #12**

## EOS Lessons Learned Working Group Agenda

- 0900 – 0915	Activities since last Working Group Meeting	P. Brandinger
- 0915 – 0930	Library Resource Support			G. Hodge
- 0930 - 0945	Draft GPG for Lessons Learned		P. Brandinger
- 0945 – 1000	Web Site and Portal Development		S. Naus
- 1000 – 1005	Lessons Learned TV			P. Brandinger
- 1005 – 1020	What is Needed from GSFC		P. Brandinger
- 1020 – 1025	Discussion and Plan for Next Month		Working Group
- 1025 – 1030	Action Items				P. Brandinger

## Progress to Date

- 	_Topic_			  _Metric_			_Schedule_
- Mini-Course #7; Mark Steiner	  Brown-Bag Lunch	13 June
- Video Content Organization	  Transfers to Library	Ongoing
- Library Data Organization	  Discussions		Ongoing
- Portal Development		  Discussions		Ongoing
- EOS Pilot Home Page Updates	  Ongoing		Weekly
- Lessons Learned TV Schedule	  Ongoing		Weekly
- GPG Draft for Review		  Document		End-July

## Where is Weather Forecasting Headed in the Future? 

**EOS-Sponsored **
**Brown-Bag Lunch Mini-Course**
**Mark Steiner/Code 592**
- Systems Engineering Services and Advanced Concepts Branch
**June 13, 2003**** **

## Library Resource Support

- Identifying resources of interest and relevance to the EOS Projects per the Project category structure
- Electronic journals
- Library catalog
- NASA and external databases
- Links to standards and handbooks
- Video content
- EOS Lessons Learned TV Webcasting provided for three months
- Common metadata structure being defined for common link between GSFC resources

## Draft GPG for Lessons Learned

- Initial view is that this should be a Code 400 document
- Code 400 needs to develop and maintain consistency among Projects
- Implementation of lessons learned activities is directly tied to Code 400 Program and Project Management functions
- Projects need a documented process for lessons learned
- Capture, organization and application of lessons learned takes place within Projects
- Projects and Program Offices are best able to tailor and organize their efforts
- This will be part of broader Center knowledge management activities
- Policies, processes and procedures for knowledge management come from Code 300
- Infrastructure and support services will be provided by other Center organizations

## EOS Lessons Learned Portal

- Ability to enter and search for lessons – 5 May
- Upload spreadsheet for limited users
- Make results page sortable on each column
- Add Library search channel
- Aggregation of search results
- Reactive license
- Vivisimo taxonomy tailoring feature
- Funding for purchasing license
- Expert identification of EOS staff – 12 May
- Import EOS spreadsheet into myExpert
- Impact to user account in myGoddard
- Staff profile for email push of content – 1 Jun
- Autonomy’s Knowledge Update feature
- Generic email push
- EOS Project library integration – 19 May
- Continue mining of system
- Passworded system mining

- Chat capability – mid Jun
- Investigate Sun’s integrated IM tool
- Integrate Jabber tool into portal
- Survey feature – 1 Jun
- Integrate survey tool into portal
- News – 15 May
- Add News channel
- Content channel creation for EOS staff
- Establish development box
- Train EOS staff
- Integration of other GSFC systems
- SOARS, NCR, FARS, HSTARS, etc.
- Create methodology/agreements

## Slide 8

## LLTV Schedule

## What Have we Learned so Far

- One size does not fit all; multiple processes and techniques are required
- Databases do not solve problems for Projects and people
- Staff interest alone cannot support active involvement
- Value-adds to existing work processes will drive participation
- Project, staff and organization needs, interests and perspectives result in different priorities for the same lessons learned activities

## What is Needed from GSFCfor Lessons Learned to Succeed

- Project Manager endorsement is essential
- Center, Directorate and Program Office must establish capture and sharing of knowledge across Projects as a priority
- Projects require infrastructure to be provided by the Center
- Tools and resources from other Directorates are part of this process
- Center guidelines for Project management need to be aligned with Agency process standards
- The review process should reinforce sharing of lessons learned
- Cultural change cannot be motivated from the grass-roots and it takes time
- Center leadership is necessary to encourage staff involvement

## Activities in the Coming Month

- Obtain feedback from HR on matching funds for rewards
- Rollout Portal with; LL access; search tools; surveys; profiles; Library access
- Projects to actively support capture processes
- Expand in-reach communications efforts
- Kick-off people-to-people facilitation process; mentoring, experts & retirees
- Apply metrics to the process
- Conduct interviews using video capture

## Backup

## TOP 10 LESSONS LEARNED
 The Best Plans Have Clear Visions, Goals, and Action Items 
 Good Leaders are Committed and Empower Others 
 Having a Coordinator at the Working Level is Desirable 
 Environmental, Economic, and Social Values are Compatible 
 Plans Only Succeed if Implemented 
 Partnerships Equal Power 
 Good Tools Are Available 
 Measure, Communicate, and Account for Progress 
 Education and Involvement Drive Action
 Build on Small Successes
                                                                                    - EPA Watershed Study

*** ******The Best Plans Have Clear Visions, Goals, and Action Items ***
*** ******Good Leaders are Committed and Empower Others ***
*** ******Having a Coordinator at the Working Level is Desirable ***
*** ******Environmental, Economic, and Social Values are Compatible ***
*** ******Plans Only Succeed if Implemented ***
*** ******Partnerships Equal Power ***
*** ******Good Tools Are Available ***
*** ******Measure, Communicate, and Account for Progress ***
*** ******Education and Involvement Drive Action***
*** ******Build on Small Successes***
**                                                                                    ****- EPA Watershed Study**