290 likes | 306 Views
PROJECT PLAN. What is project? What is project plan? Uses of a Project Plan Inputs and Outputs Standard Project Plan Structure. PROJECT. What exactly is a project? "I am going to add a deck in the backyard. It will be a real project."
E N D
PROJECT PLAN • What is project? • What is project plan? • Uses of a Project Plan • Inputs and Outputs • Standard Project Plan Structure
PROJECT • What exactly is a project? • "I am going to add a deck in the backyard. It will be a real project." • “Our team's project is to determine consumer preferences in our • industry through the year 2010." • "I have a little project I would like you to tackle. • I think that you can be finished by this afternoon."
PROJECT ESSENTIALS • Projects can be viewed as having four essential elements: • a specific timeframe, • an orchestrated approach to co-dependent events, • a desired outcome, • unique characteristics.
PROJECT ESSENTIALSSpecific Timeframe • Much of the effort of the people on a project, and certainly the use of • resources, • including funds, • achieve the desired outcome • be completed as scheduled in an appropriate manner. • Along the way toward completion or realization of a desired outcome, • interim due dates in which "deliverables" must be completed. • a report, • provision of service, • a prototype, • an actual product, • a new procedure, • any one of a number of other forms.
PROJECT ESSENTIALS An Orchestrated Approach to Co-dependent Events Projects involve a series of related events. One event leads to another. Indeed, if projects did not involve multiple events, they would not be projects. They would be single tasks or a series of single tasks Coordination of events for some projects is crucial Effective project management requires the ability to view the project at hand with a holistic perspective. Holistic: The organic or functional relations between the part and the whole.
PROJECT ESSENTIALS A Desired Outcome A desired outcome; something worth striving for; the overarching goal of a project; the reason the project was initiated to begin with. At the end of each project is the realization of some specific goal or objective. Unique Characteristics Even if you have just completed something of a similar projecta month before, the new assignment would still represent an original project, with its own set of challenges. Why? Because as time passes, society changes, technology changes, and your workplace changes.
PROJECT PLAN • Project Plan is a fundamental document that spells out, • what is to be achieved, • how it is to be achieved, • what resources will be necessary. • Any plan is better than no plan, since no plan doesn't lead anywhere
OBJECTIVES OF THE PROJECT PLAN • Theprojectplan can accomplish two major objectives. • it forces the team to constantly ask questions such as: • ·How will we accomplish that? • ·How long will it take? • ·Who will do it? • ·What kinds of deliverables will be required? • ·What are the dependencies? • it forms the bridge between strategy and design. It can be integrated with plans from other teams (e.g., interaction design, content authoring, application development) toward the development of a structured schedule for overall site design.
USES OF THE PROJECT PLAN • Guide project execution • Document project planning assumptions • Document project planning decisions • Facilitate communication among stakeholders • Provide a baseline for progress measurement and project control
PROJECT PLAN is an INPUT/OUTPUT PROCESS Project plan uses output of other planning processes. • INPUTS • Other planning outputs • Historical information • Organisational policies • Constraints • Assumptions • OUTPUTS • Project plan • Supporting detail
INPUTS • Other Planning Outputs • Scope Management (the limits of a subject or an activity) • Time Management (project schedule) • Cost Management (resource requirements) • Historical information • Current situation
INPUTS • Organizational policies • Quality Management – process improvement goals • Personnel administration – performance reviews • Financial Controls – required expenditure reviews • Constraints • Factors that will limit the project (predefined budget, contractual provisions) • Assumptions • Factors, for the purpose of planning considered to be true.
OUTPUTS • Project Plan • Formal, approved document to manage project execution • Project plan includes; • Objectives, Scope, Organisation and Responsibilities, A brief description of the project, Project Schedule, Project Deliverables and Quality Objectives, Dependencies, Plans of Support Activities, Project Facilities and Resourses, Risk Management, Process Options and Deviations, Stages and Objective of the each stage, Project Control, Quality Control, Project Effort Estimate, Project Cost Estimate.
OUTPUTS • Supporting detail • Additional information generated during the process • Technical documentation • Documentation of relevant standarts
PROJECT PLAN -STANDARD • Objectives • List of the objectives of the new system. For example: • To provide faster and more efficient services to the customers • To set-up an environment to facilitate the current and future e-commerce system requirements etc...
PROJECT PLAN -STANDARD • Current System • Definitions and Acronyms • Define and clarify the technical tems (Jargons) and abbriviations that you intend to use in. • Project scope • Project scope means the range or extent of the project. It helps to establish the boundaries of the Requested Systems
PROJECT PLAN -STANDARD • Project summary • Very brief descriptions of the project, how the project initiated, what are the recommended solution and the justification of the recommended solution by emphasising on the key benefits. (HINT: it is best to leave the Project summary as the last task of the report writing)
PROJECT PLAN -STANDARD • Project deliverables • A list of deliverables generated both during and on completion of the project. • For each deliverable, a description of its quality objectives. (For example, the system will meet the requirements specification as demonstrated by the output of the system test...) • The amount of support to be allocated to the implemented system
PROJECT PLAN -STANDARD • Organisation and Responsibilities • The project manager identifies the required project team, and, taking the organisation’s resourse plan and the project skill requirements into account, assigns roles and responsibilities to named individuals. Note: Same person may have multiple roles on a project
PROJECT PLAN -STANDARD • Dependencies • Any dependencies outside of the project manager’s control. (For example, activities to be carried out by a client or subcontractor.) • Internal dependencies must also be considered. (For example, if a needed source cannot become available until another project is completed.)
PROJECT PLAN -STANDARD • Plans for support activities • Configuration Management (Physical System) • Project Training Plan • Quality Plan • Documentation Support • Project Control Plan (revised plan? meetings?)
PROJECT PLAN -STANDARD • Project Facilities and Resources • Office space, office equipment, software product, other support tools • Planning for adequate computer sources (memory, disk, processor), taking into account the size of the software product, the project staffing levels, and past history of the similar projects
PROJECT PLAN -STANDARD • Project Schedule • A Gantt chart of activities, resources and assigned responsibilities allocated to them • Critical dependencies between the project groups must take into account. • Use of any project management software is recommended to produce project schedule.
PROJECT PLAN -STANDARD • Project Efford Estimate • Project efford in person days or person months • Effort to be broken-down by project stage • Information used to derive the efford estimate to be included (i.e. Estimated size of software work products). • Project Cost Estimate • Project cost is estimated. Costs to be itemized (labor, euipment...) • Information used to derive the cost estimate to be included.
PROJECT MANAGEMENT STAGES • Planning & Analyzing(Planlama ve Analiz) • Design (Tasarım) • Realization (Gerçekleştirim) • Integration (Entegrasyon-Birleştirme) • System Validation (Sistem Geçerliliği = test) • Customer Acceptance (Müşteri Kabul) • Maintenance, Education, Guarantee (Bakım, Eğitim, Garanti) • INPUT PROCESS OUTPUT
PROJECT MANAGEMENT STAGES • INPUT PROCESS OUTPUT • Planning & Analyzing (Planlama ve Analiz) • Customer Requests Project Plan & Analyse Report & Project Team • Design (Tasarım) • Project Plan & Analyse Report System & Database Design • Realization (Gerçekleştirim) • System & Database Design Coding, Graphic Design & Hardware
PROJECT PLAN SCHEDULE- Gantt Chart • Planning & Analyzing • Design (Tasarım) • Realization (Gerçekleştirim)
PROJECT PLAN- Organization and Responsibilities JOB DESCRIPTIONS • PROJECT TEAM • Project Manager • System Analyst • Database Manager • Application Software Development Specialist • Tester • Trainer • Technical Support Specialist • Graphic Designer Who is who? – task sharing TASKTIMESTAFF?
PROJECT PLAN DEVELOPMENT • DURING PLANNING AND ANALYZING • TWO IMPORTANT QUESTIONS MUST BE ADDRESSED! • Routine (regular) Tasks • What are the things they want to do, but they haven’t do yet Example: ET VE BALIK KURUMU Requiremets Şartname Proposal teklif Store Accounting Dept. transportation Sözleşme Contract