LECTURE 4 BUILDING A PROJECT PLAN RECAPPING OF WHAT HAS BEEN (& MUST HAVE BEEN) ACHIEVED !!!!!

! Checklist Created a Vision Researched the Technology Partnered with the Management Created a Budget Made WBS Assembled a team If not then be ready you will be taught to do the above in this section Creation of the Project Plan Depending on the size of your project plans will vary and will be collection of plans explaining the scenarios and actions Many parts of a project are changeable and some are not such as the scope, charter and performance baselines Project Plan Documents Regardless of Project size some documents and elements are common: o Project Charter o Scope Statement o WBS o Time and cost line for each work Package o Milestones and dateline of milestones o Staff Requirements (their vulnerability and costs) o Risk management and contingency plans o Procurement and its supporting documents Creating Project Scope Management Plan Scope defines the requirements of the project, how these requirements will be met and how the actions will be monitored o Scope Management Plan defines the procedures, methods and the methods in case of a following change/s : Errors and omissions Value-added changes External Events Risk Events Creating Project Schedule Management Plan We need to have definitive benchmarks to identify an end of a task or the project as whole and should reflect the WBS o Project Management Plan defines several following step for the PM and his/her team: Project activities and their duration Order and priorities of activities Identification of Resources and the exact time of use How the schedule of project can be adjusted, compressed, change or maneuvered How the project is monitored and controlled Creating Project Cost Management Plan It estimates the budget and defines procedures to control it o To obtain Project Cost Management Plan accurately we would require the following steps: Project scope baselines Project Schedule Human Resource Plans Risk Register Enterprise environmental plans Organizations process assets

Creating Project Quality Management Plan Quality is creating promised results within the given costs and project timelines o Project Quality Management Plan defines What actions are for your project to achieve quality How you will achieve those actions Ensure that quality exists in the project deliverables Creating Project Team Management Plan Managing teams and employees is based on: i. Culture of the organization ii. Power, decision making and authorities of project leader on his team For effective Team Management, 2 plans are required to be made 1. Human Resource Plan: defines the needed roles and responsible of project team 2. Staff Management Plan: defines how team members are going to be brought into and released from the project Creating Project Communication Management Plan o Strong communication is required among team members for good project management o A communication plan is required to determine: What person need what information When this person will need that information The modality in which information is needed Which stakeholder will supply which information Identify appropriate technologies, forms, meetings etc. Creating Project Risk Management Plan o Risks comes in every size, forms and shapes and in IT Project a project is itself considered a risk o To overcome the risk, an effective management plan is required at all levels of the project and constant input from all the earlier discussed plans o All identifiable risks should be handled with care however project should not be stopped over smaller risk Creating Project Procurement Management Plan o Procurement plan defines the plan you need in order to create a contractual relationship with vendors and contractors in both cases of make or buy o This plan defines four things in detail: Decision to procure for your project Procurements are according to your organization/project Contracts and administration setups etc. Closing of the contract upon agreements o Preparing to Purchase: Purchases can be made for material, resources, facilities, equipments, software, hardware and services o Statement of Work (SOW): It defines what the vendor will provide to the project and contains ample information so vendor can respond in detail on one or more of the following documents: Request for Quote (RFQ) Invitation for Bid (IFB) Request for Proposal (RFP)