Basics Project Management Life Cycle: Wrap-up Step

After a project has been completed, the last step is the final wrap-up. A complete summary should be written of every step of the project along with changes made to the original outline of the work as well as any alterations to budgets and the overall lessons learned from the project. This will be very helpful to you and your company in completing future projects.

How do you think that feedback differs from criticism in Project management?

- Feedback is specific to improving performance
- Feedback is offered with positive intention of helping
- Feedback is about the performance, not the person

What exactly is a skill in project management?

In project management, a skill is the ability to coordinate behaviour to achieve an objective.
A skilled project manager knows what it takes to manage both tangible and intangible ressources, and how to coordinate both people and process to sucessfully complete a project.

Business Effectiveness

"Hire the best. Pay them fairly. Communicate frequently. Provide challenges and rewards. Believe in them. Get out of their way and the will knock your socks off".
- Mary Ann Allison

As a manager, do you delegate?

Here are some common myth about delegation:
1. There is not enough time to delegate
2. My employees are not competent enough
3. If you want it done right, you have to do it
4. People won't think you are on top of the job
5. You should not delegate what you are good at doing

Project Management and Webcasting using WebEx

The WebEx online meeting technology definitely helps to streamline project management with your partners remotely:

- identifying additional needs
- managing projects visually
- save money on meetings and/or traveling by using online technology
- speeding up the processes within the projects

WebEx recordings or live webcasts, note that recorded webcast can be posted and shared, getting your message out to more people, faster.

As an IT Architect how do you measure success (II)?

In respect to what KPI your organization follows or not, The simplest way for IT architect (matters any Architect) to measure his/her success is:

1) Develop your growth plan for short term and long term, what and where you want to be.
2) Knowledge Acquisition in changing business demands.
3) Build a design or solutions were all business elements (People process and Technology) are met and bridge all the gaps.
4) Achieve excellency in your work to gain buy-in for all your plans and designs.
5) Request Testimonial/Recommendations for your work (efforts are useless if you're not appreciated).

If you are done with above, you are on TOP success list, rest will follow :)

As an IT Architect how do you measure success (I)?

In my opinion the success is measured by:

Was the solution implemented?
Did it provide the expected results?
and finally, Is the solution flexible enough to withstand change?

I mention the last one because IT is built on top of change. Any IT Architect (of any vertical) must incorporate the change aspect on its solutions. Please do not reduce the support for change just to the upgrades and additions to the solution. The end-of-life, disposal and deployment of new solutions also counts as change.