Showing posts with label Steps. Show all posts
Showing posts with label Steps. Show all posts

Friday, January 28, 2011

Project Management Steps to Take For Success

Identify Stakeholders and Sponsors


Identify the project's stakeholders and sponsors, in addition to a project champion in top management. Mainly because most projects require time resources and cooperation from people in numerous numerous areas of the business, using a champion in top management will insure that the project will be taken seriously, and is going to be a priority for those working on it.


Create an Objective Document


Create an objectives document, that will define the project's scope, requirements, and constraints, as well as a clearly defined list of deliverables. Requirements needs to be realistic and deliverables need to be tangible and measurable. The objectives post stands out as the project's principal top-level documentation to your duration from the project.


Develop a Project Plan


Develop the overall project plan with the objectives page as a guide. Identify the many tasks that ought to be achieved, then break them down into tiny tasks that are simpler to track and measure. Assign 1 owner for each task, whilst numerous people may well end up working on it, because it is important to obtain a single individual who is ultimately responsible for the completion of each task. Accurate time estimates and projected prices for each career must be determined. Order the tasks to create the best use of resources and time, placing particular emphasis on tasks that are on crucial paths for your project. Make note of any possible risks and point these to the plan. Measurable milestones must be set, and if it makes sense to your project, control the project in phases. A phased technique will enable separate evaluations and sign-offs to occur as the project progresses. Back-out plans ought to also be created if necessary. It is essential for project managers to individual the planning process, as the accomplishment or failure of any project is ultimately the responsibility on the project manager.


Assemble Project Resources


As component in the development the project plan, determine if the correct resources exist for successful completion on the project. If not, determine what methods could be needed to procure the required resources. Insure that cost estimates do not exceed the overall project budget, and that prohibitive time constraints do not exist for people assigned to tasks. Assemble one of the most team possible, keeping in mind that most team members will have other work responsibilities in addition to working on the project. Team members need to be chosen not merely for their expertise, but also for their capacity to jobs effectively on the team and get jobs done with a minimum quantity of supervision.


Procure Project Approval


Participate in any needed reviews to get approval to move forward on the project plan. All stakeholders and sponsors need to sign off on a project plan and schedule ahead of any jobs is started. If any difficulties from the overall project plan or schedule are noted, make the required adjustments until approval is obtained. By no means begin a project with out full approval.


Monitor Project Progress


Once the project is underway, always monitor the progress of the project, doing certain how the milestone dates are becoming met. If ability difficulties are encountered, analyze the problem, get suggestions if needed, and then right the issue. Resolutions should be discovered simply to avoid compromising the overall project timeline. Communication from the team members and people assigned to person tasks is critical.


Develop a Reporting Structure


Decide on the reporting procedure and stick with it for the duration on the project. The progress in the project ought to be continually measured against the overall goals and schedule for your project. Preserve careful tabs on the progress of each team member, as most times the tasks of one person will depend heavily over a successful and timely completion of prior tasks inside project's timeline. It's specially important not to allow the schedule slip for tasks that were determined being on the project's important path. Implement status meetings, daily or weekly progress reports, or other reporting processes as required to monitor the progress with the project. Particular attention must be paid to project milestones, being a failure to gain a milestone is usually an indicator of the serious problem, which need to be evaluated and addressed immediately.


Measure Project Final results and Progress


Measure the outcomes against the objectives and evaluate the deliverables that are getting produced as the project progresses. If a phased process is getting used, get stakeholder approval and sign-off quickly on every phase ahead of the following phase is started. Pay particular attention to any deliverables that could affect the overall project timeline. Evaluate the overall success from the project at the end of each phase or important milestone, and make adjustments if necessary to preserve the entire project on track. Don't wait until it is too late to deal with problems, and ask for aid or suggestions if needed. Hold careful records and write-up everything as the project progresses. If adjustments or changes needs to be created during the project schedule, everyone on the team ought to be made aware of them.


Project Completion and Sign-off


As the project nears completion, evaluate the deliverables to produce certain they meet the overall goals and objectives on the project. Complete any diagnostic tests or evaluations that could be required for ones project, and address any training needs that could possibly be component in the process. Purchase approval and sign-off inside the project stakeholders and sponsors. Produce a project closure report, which documents the entire project and the deliverables that have been produced. At this issue the project is also formally regarded to become complete, and is also handed over on the help team if appropriate. Overall project feedback need to be provided to all team members at the conclusion in the project.


Effective project management is crucial to the success of any project, regardless of the size and scope. Very good communication, planning, organization, teamwork and assist are essential in order to maintain a project on track. A thorough understanding the project could be the very first step in project management. With out a clear understanding of the goals and objectives, any project can be tough to control and complete successfully.

Sunday, December 19, 2010

Successful Project Management - Eight Simple Steps to Follow


A failed project can lead to loss of revenue and opportunity; failure to achieve business goals; diversion of resources from other activities; sapping of staff morale and, perhaps, even business failure. So, as projects become more complex and critical to business performance, how do you improve your chances of success?

Follow these eight simple steps to achieve great results in your projects.

1. Get management and stakeholder commitment

In the first instance, you need to have the real commitment of management and stakeholders -- the people who will benefit from the project. Be sure that your project has a sustainable business case and that it can deliver real business benefits, so understand both its business and technical objectives. You must maintain business focus to avoid the common pitfall of projects that deliver a technically correct solution but one that does not meet business requirements.

You must also have a strong sponsor-- someone who is sufficiently high up in the organisation to sustain commitment to the project and who will fight for it at senior management level. It is not enough simply to gain management and stakeholder commitment at the start of a project -- you must work to sustain it throughout. You can do this by keeping them firmly in the communications loop and making sure that they are aware of major developments, achievements, issues and risks.

2. Define scope, goals and objectives

The scope of a project defines what business areas and processes will be affected. Define it clearly and communicate it to all stakeholders. To avoid any doubt, do not be afraid to say what is not in the scope. Once defined, manage the scope carefully to avoid "scope creep," or widening of what the project will cover. The customer or sponsor should approve changes to the scope, which will almost certainly mean that the project has to be re-planned or re-costed. Don't buy in to a changed scope without re-planning the project -- it is a recipe for almost certain disaster.

The sponsor or customer should define the overall business goal for the project -- the "end game" that it will achieve. Once you understand the overall goal, you can then define the project's business and technical objectives. These are lower level objectives that will contribute to the achievement of the overall goal. They will form the basis of the high-level project plan.

Remember that the longer a project goes on, the more organisational change will take place. So make sure that the project is not overtaken by events that might lead to its failing to meet customer expectations.

Make sure that the project is realistic and that your organisation is capable of undertaking it. What can you reasonably and realistically achieve with the resources provided to you? Challenge your organisation and your team with stretch targets, but avoid "grand design" projects -- they have a nasty habit of failing!

3. Have a written plan

The best way to manage your project is with a written plan. Any project over about one week's duration or involving more than one person needs one. A plan describes:

how the project will be broken up into phases;
what tasks will be carried out in each phase;
who will carry out each task;
how long each task will take;
when each task will start and finish;
what will be the deliverable or end product of each task, and
what the overall project budget is.

A plan can be as simple as a list of tasks with names, dates and deliverables written on a sheet of paper or a complex matrix of phases, tasks, dependencies, responsibilities, dates and costs managed in a software package.

4. Manage project resources and encourage team working

A typical project involves lots of people, including end users or customer staff; technical staff; administrative and financial staff; consultants; contractors; suppliers; external advisors and outside agencies. The attendant relationships create additional dependencies and risks that you need to manage. When you also consider the need to manage cost; provide hardware, plant and machinery; deal with industrial relations; manage process change and train staff, it is clear that resource management is quite a challenge. Therefore, there is a clear need for a skilled project manager and for an effective team, working together and committed to the project.

5. Manage communications

Maintain good communications within the project team and with the wider group of stakeholders and affected groups. The team must not become isolated from the rest of the business environment or from the ultimate customer and users. If it does, the project might run the risk that users will not accept the final system or product. Good communications are particularly important towards the end of a project to ensure that the users or customers are prepared for the implementation and for using the new system or facility.

Management might need to review and amend working agreements to ensure that staff will accept the system. Where the general public is involved, it may be necessary to consider wider communication methods like advertising, focus groups, or pilot implementation.

6. Manage suppliers and external sub-contractors

Modern complex projects usually involve suppliers, sub-contractors, consultants and other external resources. They create further dependencies and risks. Base agreements with suppliers and other external parties on clearly specified requirements that identify the performance standards expected and the products or systems to be designed, developed, and delivered. Meet suppliers and external parties regularly to ensure that they are performing as expected. Remember that your external resources may, in turn, depend on their suppliers and sub-contractors so be clear about whose responsibility it is to manage these dependencies and keep an eye on the performance of sub-contractors.

7. Put in effective control processes

Control processes are used to make sure that the project is proceeding as planned and that deliverables meet required standards. Put simple processes in place. Hold regular project meetings -- every week for most projects -- to review progress against the plan. Use a standard agenda. Document and agree key decisions and formally test and accept major deliverables, which must be clearly verifiable and associated with measurable milestones. Establish a regular reporting process both at project team and project board level to provide formal reports on project status. Make sure that all stakeholders receive the right reports to maintain awareness of the project and its achievements. Establish review and quality assurance processes to maintain the quality of the products or systems being developed and the quality of the project management process. Identify and manage the risks and issues that arise during your project and put in place procedures to allocate responsibility for avoiding, resolving or mitigating them.

8. Close the project

Lastly, bring the project to a formal close and advise all stakeholders and participants that it is complete and has achieved its objectives. Put a lot of work into tying up any last loose ends. When the project is finally over, make sure the required support and operational arrangements are in place. Wrap up project documentation and prepare the final project report. If your organisation has a quality management process, report any lessons learned or suggest opportunities for improvement so that these may be considered in future projects.

Then have a party -- you and your project team will deserve it!








About the author

John Lawlor is an IT manager and consultant and has been delivering large-scale technology and business solutions and advising major public and private sector organisations for over 25 years.

He is the author and presenter of training courses on general management; strategic management; project management; communications skills and personal development. He speaks regularly at seminars on public sector governance; internal audit; public financial management and value for money. He also writes on technology, business and career matters.

For further advice or assistance on the topic covered by this article, please contact John through his website http://johnlawlor.ie

Disclaimer: The views expressed in this article are the author's alone and do not represent those of any employer or other organisation with which he is or was associated.

(c) Copyright - John J. Lawlor. All Rights Reserved Worldwide.