Developing And Managing Project Work Breakdown Structure And Schedule

Creating Work Breakdown Structure

1. Why do we use WBS for Project Management?

The project management is the analysis of the works dependent on the alignment of the specific and smart alignment of the operations. The WBS stands for work breakdown structure and it involves the development of the work and aligning the significant listing of functions. The work breakdown structure would allow the division of the complete project into specific smaller operations for ensuring that the implication of the works would be implied with the implication and development. The WBS would be developed for ensuring the division of the smaller work packages and it would allow the easy division of the works. The complete project would be subdivided into smaller sub projects for ensuring the work division is aligned cohesively. The division of the work would be helpful for ensuring the alignment of the specific work allocation and development.

1. As a project manager, in which document do you track the schedule progress such as activities completed, activities in program, actual start and finish dates, percentage complete, hours spent, resource allocations, etc.

(a) Project Schedule

(b) Schedule Baseline

(c) Schedule Management Plan

(d) Schedule Network Diagram

Answer: Schedule Baseline is helpful for keeping track of schedule progress by keeping accounts of activities completed, activities in program, actual start and finish dates, percentage complete, hours spent, resource allocations, etc.

1. What is project baseline and what does it include?

The project baseline can be defined as the implication for storing the scheduled values estimated at the project planning method to act as a reference point.

The project baseline includes the values of schedule, cost, and resource usage that had been estimated at the initial planning phase. It helps in keeping track of the project progress enabling whether the project would be completed successfully.

1. Describe how to use milestone tracking as a means of measuring project progress.

The milestone tracking is helpful for enabling the use of tracking methods like checklist, documentation, and log books for analyzing the progress of the project. The milestone identification would be done considering the practical perspective of the work. The achievement of the specific points would be dependent on the alignment of the works and formation of the smart work development and alignment of the successive work development. The use of the milestone tracking would be helpful for defining the project milestones, overseeing the project progress, and identifying the project status. The completion of the project activities would be implied with the listing of the activities and forming the utilization and information listing for the operations.

1. What is the percent complete approach to measuring project progress?

The project progress would be completed with the formation and listing the application management. The percent complete approach would be effectively measures with the formation of the works and allocation of the smart management works. The complete approach would be implied with the functional listing of the works. The project progress would be effectively implied with the continuation of the works and development of the implied management works. The measurement of the project progress would be implied with the continuation management. The completion of the project would be effectively managed with the utilization management formation. The measurement of the project progress would be implied for the successful listing of the alignment management.

1. What is cost variance?

Estimating Project Duration and Dependency

The cost variance is the value difference between the cost’s actual management and the budgeted amount of utilization. The cost variance calculation would be aligned with implication management and utilization of the factors. The completion of the smart and effective management would be implied with the listing of the cost variance calculation. The cost variance calculation would be required for aligning the management of the information and taking care of the conceptive management of the works. The calculation of the cost variance is done by subtracting actual cost from earned value.

Hence, for over budgeted projects, CV would be negative whereas under budgeted project would have positive value. The value ‘0’ of CV would be helpful for ensuring that the project final budget and estimated budget is same.

1. What happens during execution phase of the project?

The execution phase is characterized by the use of the proper documents like project charter, schedule, resource usage, cost budget, risk management plan, and design for achieving the final output of the project. The development of the works would be effectively implied with the continuation of the effective work experience. The execution phase involves the simplification of the improved work experience for forming the utilization management. The formation of the works would be supported by the utilization of the works and formation of the smart work development. The project execution would be aligned with the formation of the implication management. The project execution would be effectively implied for taking care of the factors for managing the development model. The execution phase would be responsible for executing the works and forming the successful implication of the works.

1. John is managing a project. The project is three quarters done when the site engineer reports that due to inherent complexities in a certain task the deliverables would get delayed. This would involve additional analysis and then implementation. He requests that this new work that was not envisaged earlier be added to the scope and also the time be added to the schedule. You and the site engineer have analyzed the impact of this change to cost and have written up a change request approval from the change control board. Just today you have received approval from the change control board – what should be the immediate course of action?

(a) Start Work immediately

(b) Ascertain the impact of this change to scope, schedule, and cost before making any change

(c) Perform Quality Assurance

(d) Make sure that the scope baseline and schedule baseline are update to reflect the approved change before implementing the change

Answer: (d) Make sure that the scope baseline and schedule baseline are update to reflect the approved change before implementing the change

1. The project time management process consists of following seven processes:
2. Define Activities
3. Develop Schedule
4. Plan Schedule Activities
5. Sequence Activities
6. Estimate Activity Durations
7. Estimate Activity Resources
8. Control Schedule
9. The representation of the plan for executing the project’s activities including durations, dependencies, and other planning information, used to produce project schedule along with other scheduling artifacts is known as:

(a) Schedule Compression

(b) Schedule Model

(c) Schedule Data

(d) None of the above

Answer: (b) Schedule Model

1. The method of estimating project duration or cost by aggregating the estimated of the lower-level components of the WBS is known as:

(a) Alternative Analysis

(b) Bottom-up Estimating

(c) Parametric Estimating

(d) Three-point Estimating

Answer: (b) Bottom-up Estimating

1. During project execution, a work item has taken twice as long as the estimation. The estimates were provided for by the Project Architect and an external consultant. The client has asked if the deadline can be brought forward by a week. Which of the following actions can you take?

(a) Use the triangle of constraints to understand and explain to the client that if the deadline is brought forward the scope and/or cost will increase

(b) Analyze the risk and add it to the Risk Breakdown Structure

Implementing Mechanisms to Measure, Record and Report Progress

(c) Use the Delphi Method to determine if this request can be accommodated

(d) Provide the client with the new schedule and communicate the risk of bringing forward the deadline

Answer: (d) Provide the client with the new schedule and communicate the risk of bringing forward the deadline

1. During a work breakdown structure meeting you have decomposed the deliverable into the work packages and created your WBS dictionary. However, you now want to decompose the work packages to assist you in estimating, executing, and control the project. These decomposed work packages are called?

(a) Milestone

(b) Work packages can’t be decomposed into smaller units

(c) Activities

(d) Control Accounts

Answer: (c) Activities

1. As the project manager of a project, you needed to estimate certain activity duration before team members were acquired. In acquisition of the project team, you find that the actual competency levels of the acquired team members are much lower than what you had anticipated. In such a case, you will:

(a) Make no changes to the schedule

(b) Make changes to the activity duration and schedule incorporating the changed competency levels

(c) Inform the customer that the project is behind schedule

(d) Ask the project team members to meet the original schedule by putting in overtime if required

Answer: (b) Make changes to the activity duration and schedule incorporating the changed competency levels

1. A Project Manager has finalized scope baseline and started to define activities using company’s templates and procedures. What is missing to complete the work?

(a) Organizational Process Assets

(b) Enterprise Environmental Factors

(c) Requirements documentation

(d) Activity List

Answer: (d) Activity List

1. Work Breakdown Structure

The work breakdown structure would allow the division of the complete project into specific smaller operations for ensuring that the implication of the works would be implied with the implication and development. The WBS would be developed for ensuring the division of the smaller work packages and it would allow the easy division of the works. The following diagram would show the work breakdown structure for the project,

Project Schedule

The project schedule has been developed using the implication of the project adaptive modulation development management. The scheduling of the adaptive framework would be effectively implied with the successful completion of the works. The scheduling of the works would be effectively developed compiling the management of the works would be effectively managed with the successful alignment of the works and formation of the successful work development. The project schedule has been divided into the following phases,

Initiation Phase: The first phase of the project development and it would be effectively implied with the formation of the smart development of works. The initiation phase involves the accumulation of the information and the alignment of the works cohesively. The utilization of the activities like requirement analysis, charter documentation, submission of documents, and sign off are considered in this phase.

Planning: The planning is the second phase of the project operations including the development of the activities that are required for execution for project. The planning phase would involve the identification of the works that are required in the latter phases. The planning phase involves the activities of activity scheduling, listing of tasks, completion of plan, and plan approval.

Conducting Ongoing Analysis to Identify Baseline Variance

Designing: The designing is the third phase of the project operations that is being made for making the new design of the website. The website development would be effectively developed for entrapping the new features and programs in a new design. The design development would be effectively implied with the involvement of the functions and activities like website design platform selection, UI graphics are made, font is selected, content is listed, complete designing, and design approval.

Execution: It is the most crucial phase of the project activities as the main generation of the output is being done in this phase only. The execution of project activities that had been developed with the consideration of the smart project completion management would be implied with the consideration of the smart management processing. The activities included in this phase involves the UI is made, functions are made, website database is made, website domain is bought, privacy policy is made, security functions are made, integration of work functions, complete website is made, and website approved.

Testing and Monitoring: This phase is characterized by the analysis of the work requirements and the output of the project works. The testing and monitoring of the project outcomes would be effectively implied with the formation of the activities like Simulation, Alpha testing, Beta testing, and Testing Completed. The completion of this phase would involve the completion of the works and forming the alignment of the works dependent on the alignment of the work development.

Closing: The final phase of the project that would involve the activities of website domain is fixed, go live of website, final documentation, submission of documents, sign off, and closure. The completion of the phase would be helpful for documenting the project activities so that it can be used for future references. The project report would serve as the final project completion work.

WBS	Task Name	Duration	Start	Finish
0	Redevelopment of Website for National Archives of Australia	30 days	Mon 12/3/18	Fri 1/11/19
1	Initiation Phase	7 days	Mon 12/3/18	Tue 12/11/18
1.1	Requirement Analysis	2 days	Mon 12/3/18	Tue 12/4/18
1.2	Charter Documentation	4 days	Wed 12/5/18	Mon 12/10/18
1.3	Submission of documents	1 day	Tue 12/11/18	Tue 12/11/18
M1	Sign off	0 days	Tue 12/11/18	Tue 12/11/18
2	Planning	7 days	Wed 12/5/18	Thu 12/13/18
2.1	Activity Scheduling	3 days	Wed 12/5/18	Fri 12/7/18
2.2	Listing of tasks	4 days	Mon 12/10/18	Thu 12/13/18
2.3	Completion of Plan	7 days	Wed 12/5/18	Thu 12/13/18
M2	Plan Approval	0 days	Thu 12/13/18	Thu 12/13/18
3	Designing	6 days	Fri 12/14/18	Fri 12/21/18
3.1	Website Design Platform Selection	2 days	Fri 12/14/18	Mon 12/17/18
3.2	UI Graphics are made	3 days	Wed 12/19/18	Fri 12/21/18
3.3	Font is selected	1 day	Tue 12/18/18	Tue 12/18/18
3.4	Content is listed	3 days	Wed 12/19/18	Fri 12/21/18
3.5	Complete Designing	6 days	Fri 12/14/18	Fri 12/21/18
M3	Design Approval	0 days	Fri 12/21/18	Fri 12/21/18
4	Execution	15 days	Tue 12/18/18	Mon 1/7/19
4.1	UI is made	5 days	Mon 12/24/18	Fri 12/28/18
4.2	Functions are made	4 days	Tue 12/18/18	Fri 12/21/18
4.3	Website Database is made	3 days	Mon 12/24/18	Wed 12/26/18
4.4	Website Domain is bought	1 day	Thu 12/27/18	Thu 12/27/18
4.5	Privacy Policy is made	3 days	Mon 12/24/18	Wed 12/26/18
4.6	Security functions are made	4 days	Thu 12/27/18	Tue 1/1/19
4.7	Integration of work functions	3 days	Wed 1/2/19	Fri 1/4/19
4.8	Complete Website is made	8 days	Thu 12/27/18	Mon 1/7/19
M4	Website Approved	0 days	Mon 1/7/19	Mon 1/7/19
5	Testing and Monitoring	9 days	Mon 12/24/18	Thu 1/3/19
5.1	Simulation	3 days	Mon 12/24/18	Wed 12/26/18
5.2	Alpha testing	2 days	Thu 12/27/18	Fri 12/28/18
5.3	Beta testing	2 days	Wed 1/2/19	Thu 1/3/19
M5	Testing Completed	0 days	Thu 1/3/19	Thu 1/3/19
6	Closing	11 days	Fri 12/28/18	Fri 1/11/19
6.1	Website Domain is fixed	2 days	Fri 12/28/18	Mon 12/31/18
6.2	Go Live of Website	2 days	Tue 1/1/19	Wed 1/2/19
6.3	Final Documentation	4 days	Fri 1/4/19	Wed 1/9/19
6.4	Submission of documents	1 day	Thu 1/10/19	Thu 1/10/19
6.5	Sign off	1 day	Fri 1/11/19	Fri 1/11/19
M6	Closure	0 days	Fri 1/11/19	Fri 1/11/19

1. Critical Path

The project has been developed using the alignment of the effective and smart work development model. The critical path of project comprise of those tasks that cannot be executed with each other and sum of their individual durations would provide the final project duration. The critical path is identified as the activities aligning with the progress of the project and developing the final outcome of the project. The identified critical path for the project is given in the following table and diagram,

WBS	Task Name	Duration
1.1	Requirement Analysis	2 days
2.1	Activity Scheduling	3 days
2.2	Listing of tasks	4 days
2.3	Completion of Plan	7 days
M2	Plan Approval	0 days
3.1	Website Design Platform Selection	2 days
4.2	Functions are made	4 days
4.5	Privacy Policy is made	3 days
4.6	Security functions are made	4 days
5.3	Beta testing	2 days
M5	Testing Completed	0 days
6.3	Final Documentation	4 days
6.4	Submission of documents	1 day
6.5	Sign off	1 day
M6	Closure	0 days

Critical Path Description: The critical path of the project include the activities of Requirement Analysis, Activity Scheduling, Listing of tasks, Completion of Plan, Website Design Platform Selection, Functions are made, Privacy Policy is made, Security functions are made, Beta testing, Final Documentation, Submission of documents, and Sign off. The completion of these activities and the duration would be implied with the formation of the work that has been successfully. The integration would be effectively developed for integrating the alignment management. The summarization of the activities and the key listing would be implied with the development.

1. Communication of schedule baseline

Managing Project Schedule

The communication of the schedule baseline would be effectively developed considering the utilization of the factors. Schedule Baseline is helpful for keeping track of schedule progress by keeping accounts of activities completed, activities in program, actual start and finish dates, percentage complete, hours spent, and resource allocations. The project baseline includes the values of schedule, cost, and resource usage that had been estimated at the initial planning phase. It helps in keeping track of the project progress enabling whether the project would be completed successfully. The schedule baseline date of 31^st December 2018 has been selected for calculation of the baseline schedule. The following Gantt chart has been set for the baseline schedule for the date of 31^st December,

1. Tracking Gantt Charts

1. Time Rescheduling

The time rescheduling would be done by implying the use of the effective work development and integrating the listing of the effective work management. The time rescheduling would be effectively managed by the alignment of the implicit work development. The rescheduling of the work would be effectively managed with the help of resource inclusion, hiring contractor, and delaying the schedule. The project is largely impacted by the scope trio constraint and the rescheduling would be largely impacted by the formation of the effective alignment of works.

Out of the three options of rescheduling, hiring contractor would be selected as it would help in transferring the risk of delay to an external person that would be solely responsible for the completion of the work. The completion of the works would be highly impacted by the formation of the smart work development. The completion of the works would be eased by inclusion of the external people in the project.

1. What processes will you put in place to:

• Measure
• Record
• Report Progress of activities

in relation to the schedule?

• Measure: Calendar
• Record: Project Log Book
• Report Progress of activities: Gantt chart

1. Describe what you need to do to implement any agreed schedule changes

The following two methods must be followed for implementing any agreed schedule changes

• Make sure that the scope baseline and schedule baseline are update to reflect the approved change before implementing the change
• Provide the client with the new schedule and communicate the risk of bringing forward the deadline

1. Review Project Time Performance

The project time performance can be understood by the following tables and graphs,

WBS	Task Name	Duration	Start	Finish	Predecessors
1.1	Requirement Analysis	2 days	Mon 12/3/18	Tue 12/4/18
1.2	Charter Documentation	4 days	Wed 12/5/18	Mon 12/10/18	2
1.3	Submission of documents	1 day	Tue 12/11/18	Tue 12/11/18	3
M1	Sign off	0 days	Tue 12/11/18	Tue 12/11/18	4
2.1	Activity Scheduling	3 days	Wed 12/5/18	Fri 12/7/18	2
2.2	Listing of tasks	4 days	Mon 12/10/18	Thu 12/13/18	7
2.3	Completion of Plan	7 days	Wed 12/5/18	Thu 12/13/18	2
M2	Plan Approval	0 days	Thu 12/13/18	Thu 12/13/18	8,9
3.1	Website Design Platform Selection	2 days	Fri 12/14/18	Mon 12/17/18	10
3.2	UI Graphics are made	3 days	Wed 12/19/18	Fri 12/21/18	12
3.3	Font is selected	1 day	Tue 12/18/18	Tue 12/18/18	12
3.4	Content is listed	3 days	Wed 12/19/18	Fri 12/21/18	14
3.5	Complete Designing	6 days	Fri 12/14/18	Fri 12/21/18	10
M3	Design Approval	0 days	Fri 12/21/18	Fri 12/21/18	16
4.1	UI is made	5 days	Mon 12/24/18	Fri 12/28/18	13
4.2	Functions are made	4 days	Tue 12/18/18	Fri 12/21/18	12
4.3	Website Database is made	3 days	Mon 12/24/18	Wed 12/26/18	15
4.4	Website Domain is bought	1 day	Thu 12/27/18	Thu 12/27/18	21
4.5	Privacy Policy is made	3 days	Mon 12/24/18	Wed 12/26/18	20
4.6	Security functions are made	4 days	Thu 12/27/18	Tue 1/1/19	23
4.7	Integration of work functions	3 days	Wed 1/2/19	Fri 1/4/19	19,22,24
4.8	Complete Website is made	8 days	Thu 12/27/18	Mon 1/7/19	21
M4	Website Approved	0 days	Mon 1/7/19	Mon 1/7/19	25,26
5.1	Simulation	3 days	Mon 12/24/18	Wed 12/26/18	16
5.2	Alpha testing	2 days	Thu 12/27/18	Fri 12/28/18	20
5.3	Beta testing	2 days	Wed 1/2/19	Thu 1/3/19	24
M5	Testing Completed	0 days	Thu 1/3/19	Thu 1/3/19	29,30,31
6.1	Website Domain is fixed	2 days	Fri 12/28/18	Mon 12/31/18	22
6.2	Go Live of Website	2 days	Tue 1/1/19	Wed 1/2/19	34
6.3	Final Documentation	4 days	Fri 1/4/19	Wed 1/9/19	32
6.4	Submission of documents	1 day	Thu 1/10/19	Thu 1/10/19	36
6.5	Sign off	1 day	Fri 1/11/19	Fri 1/11/19	37
M6	Closure	0 days	Fri 1/11/19	Fri 1/11/19	35,38

Now according to the given project file (or calendar list) it is possible for keeping track of the works. The completion of the project would be listed with the help of tracking Gantt chart as it would help in making sure that the project is working in time.

1. Time Management Issues in Project

Date	Description of problem	Recommended Action for next time	Lesson Learnt Raised by
10/12/2018	Delay in Documentation	Documentation template must be followed	Process Documentation
14/12/18	Website Design Errors	Design Principles using SDLC must be followed	Design Principle Implication
21/12/18	Programming Issues	External Expert must be followed	Debugging of program bugs
1/1/19	Go Live Issues	Vendor must be consulted before implementing the website	Implicational Issues Resolution
5/12/18	Over Budget	Provisional Budget would be used	Budget Performance

References

Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.

Carver, C.L. and Klein, C.S., 2013. Action research: A tool for promoting faculty development and continuous improvement in leadership preparation.

Clark, D.M., Silvester, K. and Knowles, S., 2013. Lean management systems: creating a culture of continuous quality improvement. Journal of clinical pathology, pp.jclinpath-2013.

Managing Schedule Changes

Cohen-Vogel, L., Tichnor-Wagner, A., Allen, D., Harrison, C., Kainz, K., Socol, A.R. and Wang, Q., 2015. Implementing educational innovations at scale: Transforming researchers into continuous improvement scientists. Educational Policy, 29(1), pp.257-277.

Dale, B.G. and Plunkett, J.J., 2017. Quality costing. Routledge.

Dessinger, J.C. and Moseley, J.L., 2015. Confirmative evaluation: Practical strategies for valuing continuous improvement. John Wiley & Sons.

Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management. Project Management Institute.

Fryer, K., Ogden, S. and Anthony, J., 2013. Bessant’s continuous improvement model: revisiting and revising. International Journal of Public Sector Management, 26(6), pp.481-494.

Fuller, M.A., Valacich, J.S., George, J.F. and Schneider, C., 2017. Information Systems Project Management: A Process and Team Approach, Edition 1.1. Prospect Press.

Goetsch, D.L. and Davis, S.B., 2014. Quality management for organizational excellence. Upper Saddle River, NJ: pearson.

Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach. Routledge.

Heagney, J., 2016. Fundamentals of project management. Amacom.

Holtskog, H., 2013. Continuous Improvement beyond the Lean understanding. Procedia CIRP, 7, pp.575-579.

Hwang, B.G. and Ng, W.J., 2013. Project management knowledge and skills for green construction: Overcoming challenges. International Journal of Project Management, 31(2), pp.272-284.

Intra, C. and Zahn, T., 2014. Transformation-waves–a brick for a powerful and holistic continuous improvement process of a Lean production system. Procedia CIRP, 17, pp.582-587.

Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Kerzner, H., 2018. Project management best practices: Achieving global excellence. John Wiley & Sons.

Lam, M., O’Donnell, M. and Robertson, D., 2015. Achieving employee commitment for continuous improvement initiatives. International Journal of Operations & Production Management, 35(2), pp.201-215.

Larson, E.W., Gray, C.F., Danlin, U., Honig, B. and Bacarini, D., 2014. Project management: The managerial process (Vol. 6). Grandview Heights, OH: McGraw-Hill Education.

Leach, L.P., 2014. Critical chain project management. Artech House.

Lemire, M., Demers-Payette, O. and Jefferson-Falardeau, J., 2013. Dissemination of performance information and continuous improvement: a narrative systematic review. Journal of health organization and management, 27(4), pp.449-478.

Magar, V.M. and Shinde, V.B., 2014. Application of 7 quality control (7 QC) tools for continuous improvement of manufacturing processes. International Journal of Engineering Research and General Science, 2(4), pp.364-371.

Marchewka, J.T., 2014. Information technology project management. John Wiley & Sons.

Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.

Mitra, A., 2016. Fundamentals of quality control and improvement. John Wiley & Sons.

Nadeem, E., Olin, S.S., Hill, L.C., Hoagwood, K.E. and Horwitz, S.M., 2013. Understanding the components of quality improvement collaboratives: a systematic literature review. The Milbank Quarterly, 91(2), pp.354-394.

Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and technology. Routledge.

Oakland, J.S., 2014. Total quality management and operational excellence: text with cases. Routledge.

Okongwu, U., Morimoto, R. and Lauras, M., 2013. The maturity of supply chain sustainability disclosure from a continuous improvement perspective. International Journal of Productivity and Performance Management, 62(8), pp.827-855.

Owen, M., 2013. SPC and continuous improvement. Springer Science & Business Media.

Ross, J.E., 2017. Total quality management: Text, cases, and readings. Routledge.

Sahno, J., Shevtshenko, E., Karaulova, T. and Tahera, K., 2015. Framework for continuous improvement of production processes. Engineering Economics, 26(2), pp.169-180.

Schwalbe, K., 2015. Information technology project management. Cengage Learning.

Singh, J. and Singh, H., 2015. Continuous improvement philosophy–literature review and directions. Benchmarking: An International Journal, 22(1), pp.75-119.

Swartling, D. and Poksinska, B., 2013. Management initiation of continuous improvement from a motivational perspective. Journal of Applied Economics and Business Research, 3(2), pp.81-94.

von Thiele Schwarz, U., Augustsson, H., Hasson, H. and Stenfors-Hayes, T., 2015. Promoting employee health by integrating health protection, health promotion, and continuous improvement: a longitudinal quasi-experimental intervention study. Journal of Occupational and Environmental medicine, 57(2), pp.217-225.

Walker, A., 2015. Project management in construction. John Wiley & Sons.