IT Project and Program Teams (and Individual Members) Require Acknowledgement and Recognition...

Technology Project Management

 

IT Project and Program Teams (and individual members) require Acknowledgement and Recognition ...

because without them their would be no success!

It’s about Team Success! I enjoyed and I am enjoying my career as a member of those teams.

I was proud to be a member of the teams: IT project and program teams built by the project or program manager and team Leads (Business and Technical). I appreciated the teams very much. And with their success came the acknowledgement and recognition they deserved as a team and as individual members.

Management, Project and Program Managers and team Leads must never forget this fact: That unless you are a "one man "show" success does not come without team success. That success, the team’s success, my success, I attribute to committed team members (empowered team members), with knowledge transferred by their interactions, and through their use of lessons learned and Best Practice Processes' (BPPs’) best practices. The teams, with the appropriate methodologies, were proactive to address potential problems, issues and risks with open communication throughout the projects and programs.

And even with their individual goals they were teams that were committed to the primary Goals and Objectives of the projects and programs.

Technology Project Management Best Practices for Lessons Learned

Technology Project Management

Recently I read this article that grabbed my attention: Stop with the Lessons Learned

 

You would have thought that it was about not doing lessons learned but it was not. It was about documenting and conducting a lessons learned session "post mortem". Although it was a positive article, I applied comments to it because documenting  lessons learned is an important activity and should not just be left for project close out (at the end of a project). Lessons Learned must be documented and used throughout the project and program.Lessons Learned must be used for future projects and programs and during the ongoing, or current, project or program.

Read>> Importance of Documenting Lessons Learned In Technology Projects

 

IT Best Practice Processes

Technology Project Management

Best Practice Processes and their BEST (and Good) Practices

ITBest Practice Processes (BPPs): Project/Program Management, the Development Process (Methodology), Configuration Management, and Quality Assurance. Program/Project Managers (IT Program/Project Management) must plan and implement best Practice Processes (BPPs) and their best and good practices (Read Best Practices Here...). Let’s consider each and what they do for a project or program, why they are essential to plan and implement for each and every project and program. Tailor BPPs as required based on the solution, approach and the development methodology (ies) to be used.

The Need For Proven Best Practices For Project Success

Technology Best Practice Processes
 
There are serious concerns going forward in 2011 regarding IT project and program failures, including ERP, SCM and VOIP. Some IT professionals in the industry don’t think that changes required to reduce the rate of failure, or to stop this disastrous trend, is forth coming. In one article this seems to be the case, including a statement by an IT professional, “…he sees no immediate end to trouble projects….”
 
But with knowledge transfer, the documenting and USE of lessons learned and best and good practices there would be changes that increase the success rate for IT projects and programs. Also Best Practices are subject to improvement, must be used before the project or program is initiated (feasibility, to determine what is the best solution), be used for implementation or execution, and for closing out projects and programs.
 
Serious steps must be taken by IT professionals, senior management, Vendors and Subcontractors, e.g., system integration and developers, and customers.

Yes, there are several significant challenges and issues (See 10 ....) that lead to troubled or failed projects or programs)and but there are solutions and we must be diligent and committed to make the changes to increase the Success rate.
 
And while we have listed Challenges and Issues that lead to troubled and failed projects and programs, there are several more issues:
Seasoned IT professionals no longer in the work force to provide knowledge transfer (laid off or retired), Inexperienced and experienced IT professionals working extended hours, having extensive and dual responsibilities, burning out.
 
[Read More...] Proven Best Practices are being presented to overcome the Challenges and Issues.