Has anyone recently implemented a (new or revised) project management methodology/process in an organization in the recent past and have lessons to share? I am looking for a diversity of environments: IT vs. Enterprise cross-functional; chaos vs. previously structured; private vs. public sector; different industries... so I would appreciate if you can include details on your environment while providing the lessons learned. Thanks. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I am in this way right now. All lessons learned can be resumed on this. Before to start the initiative (we perform this as an initiative that became to a project) we deal with this like any type of other solution. And what we did is what you can find inside the article I publish in my blog in the address below. No matter what my article said the main lesson learned is: to implement this is a matter of organizational strategy so you have to take into account the impact you will create in the whole organization. And because it is a matter of strategy some people inside the organization have decided it according to strategic imperatives. For example, is your organization is in the organizational life cycle phase named "growth" forget about to implement some methodology because the strategical focus is to make money no matter the order you follow to do thing to get money.
http://www.projectmanagement.com/blog/How-...Analysis/15655/
In my opinion, any kind of information that you want to share need to be organize. I always look at the possibility to have something that look like a Workbreak down so you can dig from the first level.
An I agree with Sergio the context would make it possible or difficult. Saving Changes...
Samuel, you don't have to reinvent the wheel. It is better to do it yourself. We can share with you examples of what we have done in our projects but they may be quite different from yours.
Lessons learned are simple the knowledge gained during a project; this include how issues were addressed and how they should be address in the future.
You have to document the causes of issues, the corrective actions you took to overcome those issues.
Once you documented all the issues, the corrective or preventive actions, this documentation need to be distributed so that it becomes part of the historical database for future projects.
Hi Jose, great info. My concern is regarding how to search this later. Do you add this into a system later. How to associate this with similar projects in the future to really use this information to enhance future projects?
Samuel, you don't have to reinvent the wheel. It is better to do it yourself. We can share with you examples of what we have done in our projects but they may be quite different from yours.
Lessons learned are simple the knowledge gained during a project; this include how issues were addressed and how they should be address in the future.
You have to document the causes of issues, the corrective actions you took to overcome those issues.
Once you documented all the issues, the corrective or preventive actions, this documentation need to be distributed so that it becomes part of the historical database for future projects.
Hi Jose, great info. My concern is regarding how to search this later. Do you add this into a system later. How to associate this with similar projects in the future to really use this information to enhance future projects?
...
1 reply by Jose Quintal-Aviles
Feb 25, 2017 4:21 PM
Jose Quintal-Aviles
...
Rodrigo.
Of course you have to save all this type of documents in a repository, in a company's server. You can classify all your lessons learned per type of project, location, scope, etc. You define your categories. Besides, you can add tags to each lesson so it is easier for any indexing system to create a catalog for future search.
Thera are project management software in the market that can do this and much more. Or simply, use a server as you use your hard drive and store whatever you want.
Regards
Jose:
Agree with Samuel; do your research but do your internal discovery, apply what fits and build it yourself based on your culture, project environment, needs of the organization and PMs and make it useful. In my experience, many PMs already have their lessons learned from years of experience, some org PMO has round-tables for internal PMs to share lessons learned and unfortunately, lessons learned are unique point in time information. It's good to look back but each project is unique but best thing is to start. Good luck. Saving Changes...
Jose Agostinho BaitelloAcademic Faculty Member| Centro Universitario FEISao Paulo, Sp, Brazil
Mar 31, 2016 5:10 PM
Replying to Sergio Luis Conte
...
I am in this way right now. All lessons learned can be resumed on this. Before to start the initiative (we perform this as an initiative that became to a project) we deal with this like any type of other solution. And what we did is what you can find inside the article I publish in my blog in the address below. No matter what my article said the main lesson learned is: to implement this is a matter of organizational strategy so you have to take into account the impact you will create in the whole organization. And because it is a matter of strategy some people inside the organization have decided it according to strategic imperatives. For example, is your organization is in the organizational life cycle phase named "growth" forget about to implement some methodology because the strategical focus is to make money no matter the order you follow to do thing to get money.
http://www.projectmanagement.com/blog/How-...Analysis/15655/
Hi Jose, great info. My concern is regarding how to search this later. Do you add this into a system later. How to associate this with similar projects in the future to really use this information to enhance future projects?
Rodrigo.
Of course you have to save all this type of documents in a repository, in a company's server. You can classify all your lessons learned per type of project, location, scope, etc. You define your categories. Besides, you can add tags to each lesson so it is easier for any indexing system to create a catalog for future search.
Thera are project management software in the market that can do this and much more. Or simply, use a server as you use your hard drive and store whatever you want.
Regards
...
1 reply by Rodrigo Dantas Santiago
Feb 28, 2017 9:26 AM
Rodrigo Dantas Santiago
...
Hi Jose, this is exactly what I was looking for: an idea of what I can store. I found some in other treads and your tip. I will start creating a form in sharepoint and linking to the project (where I can find cost, saving, local, time, etc) and add 2 fields to add positive and negative information already. Actually we use sharepoint to input the project information. I hope I can start like this and while it's moving forward and I enhance this.
Thank you!!
