PROJECT INFORMATION

Project Title:

Property condition program

Project Aim:

desarrollar un sistema eficiente para validar y cargar datos de condiciones de propiedades al sistema BiiP del Departamento Estatal de Gobierno (SGD).

Project Background:

El Departamento Estatal (SGD) ha contratado a WeCheck para la recoleccin de datos sobre el estado de los edificios y necesita desarrollar una serie de mdulos para validar y cargar estos datos en el sistema ERP BiiP.

Key Benefits of the Project:

This project will result in the following outcomes and benefits:

Mejora en la eficiencia y exactitud delmantenimiento de propiedades

Optimizacion de recursos y reduccion de costos

Project Objectives:

The overarching project objectives are:

Desarrollar mdulos para recoger, validar y subir datos de propiedades.

Asegurar que los datos y las fotos asociadas cumplan con los estndares de calidad y formato necesarios.

Implementar un sistema de gestin de errores y generacin de informes.

SCHEDULE MANAGEMENT PLAN OVERVIEW

Provide the purpose of this subsidiary plan and its structure. You should refer to relevant peer reviewed resources and cite these resources in support of your overview and the schedule management plan.

Remember that your audience may not have a full understanding of schedule management planning. Therefore, your overview and the schedule management plan are designed to identify how the scope will be defined, organised, developed, tracked and validated. This project management subsidiary plan should include descriptions and definitions of processes followed for each subsection, written in a manner to instil confidence and answer key questions asked by all stakeholders.

Note that the schedule management plan should specify how the project schedule will be developed, monitored and controlled and this schedule management plan is aligned to the case study requirements.

1. Introduction

Purpose: The purpose of this Schedule Management Plan is to outline the approach for developing, managing, and controlling the project schedule for the Property Condition Program (PCP). This plan ensures that all project activities are completed within the specified six-week timeframe, aligning with the project's objectives and requirements.

Scope: This plan covers the entire scheduling process, from initial development to final release, including task definition, sequencing, duration estimation, and schedule control measures.

2. Schedule Development

Schedule Framework:

Tools Used: MS Project, Project Libre, or Project Plan 365. These tools will be employed to create and maintain a detailed Gantt chart, illustrating the project timeline and dependencies.

Schedule Structure: The Work Breakdown Structure (WBS) will be used to break down the project into manageable tasks and milestones. The tasks are derived from the project activities listed in Appendix 2.

Task Definition and Sequencing:

Tasks will be defined based on the project activities, such as module development, testing, and integration.

Dependencies and relationships will be established using techniques like network diagrams and Gantt charts. This will ensure that tasks are completed in the correct sequence and any dependencies are properly managed.

3. Schedule Estimation

Estimation Techniques:

Three-Point Estimation: For the B3 File Validation and B4 Desktop Validation modules, three-point estimation will be used due to varying productivity levels among developers. The very experienced developer will achieve 110% productivity, while the new developer will achieve 45% productivity. Estimates will be calculated using the formula:

[Equation]ExpectedDuration=6(O+4M+P)

where [Equation]O is the optimistic estimate, [Equation]M is the most likely estimate, and [Equation]P is the pessimistic estimate.

Resource Allocation:

Resources, including experienced and new developers, will be allocated based on their productivity levels. The schedule will be adjusted to account for varying efficiencies.

4. Schedule Control

Monitoring and Reporting:

Progress Tracking: Progress will be monitored using the selected scheduling tools, with updates reported on a weekly basis.

Performance Metrics: Key performance indicators (KPIs) will be used to track schedule adherence. Deviations will be recorded and addressed through corrective actions.

Change Management:

Handling Changes: Any changes to the schedule will be managed through a formal change control process. Changes will be documented, assessed for impact, and communicated to stakeholders.

5. Schedule Adjustments

Compression Techniques:

Fast Tracking: Tasks that can be overlapped without causing delays will be identified to reduce the overall project duration.

Crashing: Additional resources may be applied to critical tasks to shorten their duration if necessary.

Contingency Planning:

Risk Management: Potential risks affecting the schedule will be identified, and contingency plans will be developed to mitigate these risks.

6. Roles and Responsibilities

Stakeholders:

Project Manager: Oversees the schedule development and ensures adherence.

Development Team: Provides input on task durations and dependencies.

Test Team: Coordinates testing activities and updates the schedule based on test results.

Project Team:

Internal Resources: Their roles include defining requirements, monitoring progress, and providing feedback.

External Resources: Include developers and testers whose productivity and availability will be factored into the schedule.

7. Tools and Techniques

Scheduling Tools:

MS Project, Project Libre, or Project Plan 365 will be used to develop the Gantt chart and network diagrams.

Techniques:

Critical Path Method (CPM): Identifies the longest path through the project and determines the minimum project duration.

Resource Leveling: Ensures that resources are allocated efficiently without overloading.

PROJECT SCHEDULE

Describe milestones and activities, and present a high-level version of the schedule you have developed.

Please define milestones and how they will be tracked.

Please remember that milestones are a 'point in time' and are therefore achieved on a single date. Milestones have a zero duration.

Milestones:

Milestone	Date
Project kickoff	Day 1
Infraestructure setup complete	Day 15
Module development complete	Day 43
Testing complete	Day 63
Release to production	Day 66

Key Activities:

Key Activity	Planned Dates (Start and Finish)

Attach your full project schedule (Using MS Project or ProjectLibre or similar, in agreement with your Learning Facilitator) with a detailed Gantt chart in Appendix 1.

Schedule Methodology:

Identify and describe the methodology that will be used for the project, whether it is critical path, agile or a combination of both. Please remember to support your decision with academic resources.

Scheduling Tools:

Identify and describe the scheduling tools that will be used for the project. These tools can include scheduling software, such as MS Project, ProjectLibre or Gantt Project, as well as reporting software, earned value software and similar.

Level of Accuracy:

Describe the level of accuracy needed for estimates.

The level of accuracy may evolve over time as more information is known (progressive elaboration). If there are guidelines for rolling-wave planning and the level of refinement that will be used for duration and effort estimates, indicate the levels of accuracy required as time progresses.

Please ensure that these concepts have been fully explained to stakeholders via this subsidiary management plan.

Units of Measure:

Indicate whether durations will be in days, weeks, months, iterations, releases or some other unit of measure.

Variance Thresholds:

Indicate the measure that determines whether an activity, work package or the project as a whole is on time, requires preventative action, or is late and requires corrective action. You should agree this with the Learning Facilitator and ensure that it is valid for the case study and duration of the overall project.

Schedule Updates:

Document the process for updating the schedule, including update frequency, permissions and version control. Indicate the guidelines for maintaining baseline integrity and for re-baselining if necessary. While we are not requiring a Change Management/Control Plan in this plan, you may refer to change management as a concept for maintaining baseline integrity.

COST MANAGEMENT PLAN OVERVIEW

Provide the purpose of this document and its structure.

Note that the cost management plan specifies how the project costs will be estimated, structured, monitored and controlled. The cost management plan can include information on the level of authority associated with cost and budget allocation and commitment, funding limitations, and options and guidelines on how and when costs are recorded for the project.

Remember that your audience may not have a full understanding of cost management planning. Therefore, your overview and the cost management plan are designed to identify how the scope will be defined, organised, developed, tracked and validated. This project management subsidiary plan should include descriptions and definitions of processes followed for each subsection, written in a manner to instil confidence and to answer key questions that may be posed by any or all stakeholders.

RESOURCE BREAKDOWN STRUCTURE

Please provide the resource breakdown structure (RBS) for this project, based on the resources that you will allocate to activities. The RBS is a hierarchical structure used to organise resources by category and type and should consider at least the following types of resources: people; equipment; materials and locations.

The RBS within this cost management plan allows your stakeholders to understand the full range of resources required to deliver the project. Where the RBS comes from the resource management plan, the quantity, and assumptions would also be added, to allow for consideration of impacts to the schedule and the budget.

You should remember that your audience may not fully understand the concept of resources or the RBS, so you should include an introduction to the RBS section explaining the purpose of the RBS and the basis on which it has been created.

PROJECT BUDGET

Please present a high-level overview of the budget for this project and how it was determined. You should present a table with the high-level calculation, and attach the spreadsheet via which the budget was calculated as an attachment in Appendix 2. Please remember aggregated costs and the associated contingencies.

PROJECT COST MANAGEMENT PLAN

Units of Measure:

Indicate how each type of resource will be measured.

Labour units may be measured in person hours, days or weeks, but generally in hours based on their hourly rate if they are staff.

Units of measure for contract resources will depend on the contract agreement and payment method, and these may be measured in days as they are often allocated and paid a daily rate.

Physical resources may be measured in litres, tons or whatever is appropriate for the material. Some resources are based on a lump sum or per-use cost; therefore, as an example, room hire may be measured at a rate per day, rate per use or single cost.

Level of Precision:

Indicate whether cost estimates will be rounded to hundreds, thousands or some other measurement.

Level of Accuracy:

Describe the level of accuracy required for estimates. This may evolve over time as more information is known (progressive elaboration). If there are guidelines for rolling wave planning and the level of refinement that will be used for cost estimates, indicate the levels of accuracy required as time progresses.

Organisational Procedure Links:

Cost estimating and reporting should follow the numbering structure in the WBS. It may also follow the organisation's code of accounts or other accounting or reporting structures. Refer to the case study to determine code of accounts or reporting numbering.

Control Thresholds:

Describe the measures that determine whether an activity, work package or the project as a whole is on budget, requires preventative action, or is over budget and requires corrective action.

This is usually indicated as a percent deviation from the baseline and can also be demonstrated with the use of RAG colouring, with specific percentage deviation advised by the colour of the RAG flag.

Rules of Performance Measurement:

Identify and document the level of the WBS where progress and expenditures will be measured. If the project uses EVM, indicate whether costs will be reported at the work package or control account level. Describe the measurement method, such as weighted milestones, fixed-formula, percent complete. Document the equations that will be used to forecast estimated to complete (ETC) and estimates at completion (EAC).

Explain why these tools and measures have been selected and how you will use them to measure and manage performance.

Approvals:

Start Date:		Completion Date:
Student Name:	Enter your name in full	Student No: A000xxxxx
Student Signature:		Date:
Learning Facilitator:
Approved by:		Date: