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

Top skills for successful project leaders

I would say in working over numerous enterprises and with various Executives, authority is the main key to venture achievement. I've seen unremarkable undertakings prevail with fantastic authority while beyond any doubt to-succeed ventures flop because of an absence of initiative. Along these lines, finding and keeping the best venture pioneers is basic. What are the top attributes of fruitful venture pioneers? Extend pioneers do the accompanying: Set Direction. Similarly as with all pioneers, it is essential for venture pioneers to set heading. It is the pioneer's duty to build up the technique and convey it obviously and over and again to the venture group and all through the association. There is a colossal distinction in a venture group with an unmistakable heading where everybody knows how they fit in and how they contribute esteem, than in the ones where the venture pioneer may know it, yet every other person sees just their little bit of the bewilder - not the est

Prototypical Project Management and its maturity

maturity models have been around for several years. A large number of organizations have measured themselves against maturity assessment criteria, and have successfully made a fortune on the outcomes, therefore increasing their ability to deliver business results. Generally there are, however, many organizations that are still in the doldrums of job management improvement. These organizations strive for better job management, but in the process conclude with alternatives that are unlikely to have a positive impact on the project management maturity of the corporation. There is a whole lot discussed maturity models and for the purposes of this discussion I use believed that an organization which is mature in the project management will constantly deliver value adding tasks. Within my consulting engagements over the past twenty years, We have seen an amount of approaches that travel the colours of maturity growth, but that are unsuccessful to deliver continually increasing project s

Always be a Good Manager

Making use of The 'Productive Lazy' Way Avoid the Swamp This kind of is linked in so many ways to the communication topic already protected. If you create a communication plan that ensures to swamp you from 1, what is the benefit; to you or the project? None! The master plan should ensure you are not viewed as the oracle on all matters, or that you feel the bottleneck for a positive information flow within the project team. Most tasks develop communication plans that are the documented method for getting the right information to the right people at the right time. We all know that each stakeholder has different requirements for facts and so the plan specifies what, how and how often communication should be made. What project operators rarely do is consider and map all communication flows, official, unofficial, developing or complete, is to do a load research across the project composition of these communication moves. If they did they would spot bottlenecks much earl

Project Management Software

Search This Blog