Wednesday, April 20, 2011

projects failing. lessons learned.

Having been involved in several engagements past months, I took some lessons from what I consider to be good technology with bad implementations. These were not necessarily failed projects but I had a feeling of unaccomplished work. And this is because I am usually passionate about the technology I work with and I want to drag people with me, which didn't happened. Why I had these mixed feelings and the lessons I draw:

Lesson 1. Project Scope. Define the scope of your project and DO NOT cease to pressures by either your sales or customer. DO NOT accept further changes in scope without estimating impact and effort implied. Otherwise you will usually end up with more effort spend, which will translate into business issues on your side.

Lesson 2. Team skills. This is a point where the project itself needs to be planned around building or gathering the proper technical skills. Without that, I learned the hard way that nobody on customer side will ever be able to takeover your work. On the other side, not having the proper team skills upfront will again end up with more effort spend on the project.

Lesson 3. Project Setup itself. If you're working with people not willing to listen or not able to understand what you're saying, project will not end up in good conditions.

Lesson 4. I give pretty good estimates on activities part of different WBS. This last one is for me to compensate the above three points :)
Post a Comment

Disclaimer: The information in this weblog is provided "AS IS" with no warranties whatsoever, and confers no rights to any institution/person/organization. These are my personal thoughts and ideas. When I am inspired by others I give credit, I do not assume other's work and efforts. This site is NOT supported, approved, blessed etc. by Lotus Software and/or IBM Corporation.

Creative Commons License

This work is licensed under a Creative Commons Attribution 3.0 License.