Reply from DaveG253 on Jan 3 at 1:51 PM Ashish,
This discussion
<http://www.gantthead.com/discussions/discussionsTo picContainer.cfm?ID=1554>
has some interesting approaches to a Lessons Learned Repository
<http://www.gantthead.com/discussions/discussionsTo picContainer.cfm?ID=1554>
. Mark Perry's response was notable:
> "Sounds like your PMM does not address Continuous Improvement very well or
> even at all. That is not surprising as most PMMs address management of the
> project effort from initiating through closing rather than management of the
> complete project management process including the management of the activities
> that occur both before initiating as well as after closing. Hence, with
> respect to lessons learned, they are usually filed and forgotten and/or people
> spend more time debating how to collect and where to file lessons learned than
> doing anything about them. Many people believe, as do I, that every process or
> best practice should include a post-closing continuous improvement step. One
> of the "inputs" to this step is your documented lessons learned. And one of
> the outputs of this step is the project managers recommendation for continuous
> improvement based upon the observed lessons learned. Such recommendations can
> include tooling, training, and process improvements. Also, the continuous
> improvement step includes submission of the documented recommendations for
> continuous improvement to the PMO, IT Dept, or project orgnization management
> authority as well as their disposition and status. The end result is a
> priority and focus on continuous improvement actions. The lessons learned
> repositor can be structured in in number of useful ways. One common approach
> is to capture lessons learned feedback by PM process area, by tools used, and
> other measurable areas that can help direct actionable solutions. For example,
> if lessons learned consistently point to skill level errors or a PM tool
> limitation, then continuous improvement recommendations for such things as PM
> training and/or PM tool upgrades can be evaluated and acted upon. I would
> suggest giving ample attention to the lessons learned repository and what
> shoud go there, etc. and then turning your focus on Continuous Improvement.
> That is, what you plan to do with your lessons learned. We have helped a
> number of clients with continuous improvement. If you would like, I would be
> happy to put you in touch with some of them. Hope this helps..! Best regards.
> -- Mark Perry, VP of Customer Care, BOT International"
Best,
Dave
| | | ---------------Original Message---------------
From: Ashish Gautam
Sent: Tuesday, January 03, 2012 1:33 PM
Subject: Store Lessons Learned Database
Hi ,
You Can use Share point, Wiki or Excel based.
1st step - to collect
2nd step - Sanity check , as some might be repeated or may not be a exact
fit
3rd step - classify them as
- what went right
- what went wrong
- what could have been done better ( this should also be there)
Categories them - You can also put categories for the point as project
management areas, technical areas, and other...
capture these information with some project data like type, domain,
complexity,
Build database and share it with project team
Thanks
-Ashish
"Success is getting what you like, Satisfaction is liking what you have got" |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment