top of page
  • Writer's pictureHani Haham - CEO

Tips for Using Project Life Cycle Wisely

Hani Haham CEO of Wizard-Projects



When I start a new project I usually get involved in the initiation phase. This phase is really important since than you decide on the scope, the team and the budget. After this phase is closed and we are convenient with it as a profit project for most of the project types or as a real added value for a software company. We can kick off the project and go on with the Project Life Cycle (PLC). Planning usually takes less time than the initiation but we need to be very carefully and pay attention to the small details so nothing will fall between the chairs. Than we have the execution you can do a great planning but you also have to have a great leadership skills to make all the teams to work together. When tasks are completed it is very important to close the project.

Initiation Phase

  • Identify the stakeholders and understand their interests and expectations

  • Define the project scope, requirements, roles and the job responsibilities

  • Create a team capable of implementing the plan effectively


Planning Phase

  • Define major milestones - Milestones are effective indicators of the teams that helps in focusing on completing the project successfully

  • Manage projects risks and define critical milestones

  • Set Prerequisites - know how to ask questions and find out the prerequisite need to be provided or done prior for the task completion (task, tool, equipment, etc.)

  • Add tasks - add detailed tasks for the project’s short term and high level tasks for the project’s long term

  • Links - Set links between the tasks using Finish to Start, Start to Start, Finish to Finish and lag. Make sure all tasks are linked

  • Finish Milestone - add a finish milestone to the plan, for the project completion

  • Assign resources - assign resources to the tasks human or facilities


Execution Phase

  • Set a Kick of meeting with all teams representatives and management and show the plan. Get an official approval and commitments from team and management for tasks and timelines and set baseline

  • Track the plan on a daily/ weekly basis depending on the project length and Update the status accordingly

  • Reports and KPIs Compare baseline to actual progress on a routine basis. Analyze status. Show the high level picture with a drill down when required

  • Board meeting should meet and discuss risks and escalations, approve or not request to postpone the milestones

Closure Phase

  • Make sure all tasks are completed

  • Make sure that all was implemented, developed and documented as requested

  • Set a closing meeting to discuss lesson learnt from the project

  • Provide recognition for excellent performance to the team members that did an extraordinary work


That's All Folks for today!


18 views1 comment

Recent Posts

See All

1 Comment


david
Apr 02, 2019

Very nice article! It explains a lot. We are about to start to work with the SCRUM methodology. Wish us luck!

Like
bottom of page