Skip to main content

Lessons Learned: Improving Your IT Professional Services Automation



I can’t tell you how many times I’ve heard people voice their frustrations about how badly their IT project management processes suck because every project is just as painful as the last. It makes you want to grab project managers by the shoulders and say,
“Dude, if you want your next project to go more smoothly, you actually have to DO Lessons Learned exercise. You know that, right?”
Not sure how to go about doing Lessons Learned the right way for your project? No worries, I’m here to help you. A few weeks ago, I came across a great article called, “IT - Professional Services Automation” that does an excellent job of laying out the basic for IT - Professional Services Automation.
Improving as we do things: You don’t need to wait for the project to end to have the Lessons Learned meetings. Meetings organized as the project progresses can bring fabulous ideas that help the ongoing project. If you’re doing things thoroughly, each status meeting should include a brief section for “the good, the bad, and the ugly”— asking your team members what’s working and what isn’t. And keep track of all that information as you go so you don’t forget. Lessons Learned is about always improving and finding better, more efficient ways to accomplish things.
I also highly recommend applying Lessons Learned feedback directly to your IT project template if it makes sense to do so. That way, your template will be saved and ready to do things better next time you do that kind of project.
Bottom line, Lessons Learned is really the best way to figure out how to do your projects (especially the repeatable kind) better, consistently. If you don’t do it, well, then you’re probably insane.

Comments

Post a Comment

Popular posts from this blog

Leading Managers Using Latest Resource Management Software

There are numerous resources available to a company a manager has to effectively coordinate in order for the company to succeed. These resources may include manpower, funds and information technology. Prior to the creation of resource management software, managers a new hard time designating the various resources to the diverse projects that the companies were willing to undertake. During this period, the managers worked in an environment that was packed with paper. It was at times inconvenient when it came to looking through these papers to gain access to the kind of information. It was irritating and time wasting for managers. This concern and the complexity of the resource management contributed to the introduction of affordable resource management software that has greatly aided in boosting the way that the managers synchronize and allocate these resources. This has gone a long way in boosting the efficiency and accuracy and reliability of the managers as well as ensuring max...
1 comment
Read more

Scrum vs Waterfall

Relatives Sizing Of User Reports (Scrum) Tee-Shirt Sizes. Intended for release planning we might use estimates of comparative size. When less is known about the consumer stories (features or requirements) for a release, we can estimate by using a wide brush approach. Based upon such standards as how intricate we think the end user story is, how much effort it will take, and the unknowns or doubt, we give it a tee-shirt size (XS, S, M, L, XL). We can then compare all the user tales and assign relative sizes. For example, we can take one user history and based on the above conditions assign it a tee-shirt size of "Large. " We are able to then compare all the other stories against this "Large" size and assign the relative value of each story. This relative size estimating can ensure that the product owner (business representative) choose user reports to prioritize for a release. Story points. We all can then assign each tee-shirt size story factors based on an ir...
Post a Comment
Read more