Develop Project Plan
Discuss about the Requirements Management Documentation On Software.
Gantt chart for the project is given below,
The identified Critical Path of the project is,
WBS |
Task Name |
Duration |
Start |
Finish |
1.1 |
Requirement Analysis |
2 days |
Mon 7/2/18 |
Tue 7/3/18 |
1.2 |
Collecting Required Information |
3 days |
Wed 7/4/18 |
Fri 7/6/18 |
2.1 |
Activity Listing |
17 hrs |
Mon 7/9/18 |
Wed 7/11/18 |
2.2 |
Scheduling activities |
3 days |
Wed 7/11/18 |
Mon 7/16/18 |
2.3 |
Complete Plan Development |
5 days |
Mon 7/16/18 |
Mon 7/23/18 |
2.4 |
Plan Review |
2 days |
Mon 7/23/18 |
Wed 7/25/18 |
2.5 |
Risk Management Plan |
3 days |
Wed 7/25/18 |
Mon 7/30/18 |
2.6 |
Plan Approval |
0 days |
Mon 7/30/18 |
Mon 7/30/18 |
3.1 |
Checking sites for required space fitout |
2 days |
Mon 7/30/18 |
Wed 8/1/18 |
3.2 |
Site Selection |
3 days |
Wed 8/1/18 |
Mon 8/6/18 |
3.3 |
Design of the new office |
3 hrs |
Mon 8/6/18 |
Mon 8/6/18 |
3.4 |
Quotes of new design |
5 days |
Mon 8/6/18 |
Mon 8/13/18 |
3.5 |
Construction of the site |
2 wks |
Mon 8/13/18 |
Mon 8/27/18 |
3.6 |
Construction Completed |
0 days |
Mon 8/27/18 |
Mon 8/27/18 |
4.3 |
Installation at the new office location |
2 days |
Mon 8/27/18 |
Wed 8/29/18 |
4.4 |
Rewire and network offices |
3 days |
Wed 8/29/18 |
Mon 9/3/18 |
4.5 |
Move computers, phones and server to new location |
0.5 days |
Mon 9/3/18 |
Mon 9/3/18 |
4.6 |
Set up computer and phone access for all staff |
1 day |
Tue 9/4/18 |
Tue 9/4/18 |
4.7 |
Office relocated |
0 days |
Tue 9/4/18 |
Tue 9/4/18 |
5 |
Project Closed |
0 days |
Tue 9/4/18 |
Tue 9/4/18 |
- Weekly Staff Updates
WEEKLY STAFF UPDATES |
||
PROJECT NAME Red Office Relocation Project |
||
ACTIVITIES COMPLETED THIS WEEK |
||
ACTIVITIES IN PROGRESS |
NEXT ACTION |
DUE DATE |
ACTIVITIES DUE TO START NEXT WEEK |
||
ISSUES FOR IMMEDIATE ATTENTION |
Monthly Reports to Management Team
Project Status Report |
PROJECT NAME Red Office Relocation Project |
Department: |
Project Sponsor: |
Program Manager: |
Project Manager: |
Project Phase: |
Status Report Period: |
Date Submitted: |
Project Status Summary |
Budget |
Schedule |
Scope |
Weekly Reports to Project Sponsor
WBS |
Task Name |
% Completed Status |
||||||
Mon |
Tues |
Wed |
Thurs |
Fri |
Sat |
Sun |
||
1.1 |
Requirement Analysis |
|||||||
1.2 |
Collecting Required Information |
|||||||
2.1 |
Activity Listing |
|||||||
2.2 |
Scheduling activities |
|||||||
2.3 |
Complete Plan Development |
|||||||
2.4 |
Plan Review |
|||||||
2.5 |
Risk Management Plan |
|||||||
2.6 |
Plan Approval |
|||||||
3.1 |
Checking sites for required space fitout |
|||||||
3.2 |
Site Selection |
|||||||
3.3 |
Design of the new office |
|||||||
3.4 |
Quotes of new design |
|||||||
3.5 |
Construction of the site |
|||||||
3.6 |
Construction Completed |
|||||||
4.3 |
Installation at the new office location |
|||||||
4.4 |
Rewire and network offices |
|||||||
4.5 |
Move computers, phones and server to new location |
|||||||
4.6 |
Set up computer and phone access for all staff |
|||||||
4.7 |
Office relocated |
|||||||
5 |
Project Closed |
- Milestone Reports to Stakeholders
MILESTONE STATUS REPORT |
||||
PROJECT NAME Red Office Relocation Project |
||||
DEPARTMENT: |
||||
PROJECT SPONSOR: |
||||
PROGRAM MANAGER: |
||||
PROJECT MANAGER: |
||||
PROJECT PHASE: |
||||
MILESTONE REPORT |
||||
S. NO. |
MILESTONE |
DUE DATE |
STATUS |
% COMPLETED |
The monitoring system for the project of Red Office Relocation Project is developed using the monitoring system for the project include the following steps,
The monitoring system would comprise of the following activities like,
Envisioning: The initiation and analysis comprise of the process of envisioning for developing the effective enlighten of the project development. The envisioning of the project at the initial phase would comprise of the effective alignment of the operations.
Planning: The planning phase would be monitored in the two phases of specs and design for the alignment. The design and development of the specific building development would be aligned for the alignment of the effective operations.
Building Project: The development of the project and testing would be aligned with the implication of the improved functional and development model. The project development would be helpful for easing the functional development of the improved functional alignment.
Delivering Product: The delivery of the products would be aligned with the implication of the delivery and support implication. The product delivery for the operations would be supported for the formation of the operations.
The project team would require the support and development of the functional and effective implication of the support development. The development of the support for the project team development and alignment of the improved functional and effective plan development has been supported by the consideration of the improved development (Kerzner, 2017). The support in the project would require the implication of the activities supporting the alignment of the improved communication plan development. The project completion would align with the formation of the successive formation of the activities.
WBS |
Task Name |
Duration |
Start |
Finish |
0 |
Red Office Relocation Project |
47 days |
Mon 7/2/18 |
Tue 9/4/18 |
1 |
Initialization |
10 days |
Mon 7/2/18 |
Fri 7/13/18 |
1.1 |
Requirement Analysis |
2 days |
Mon 7/2/18 |
Tue 7/3/18 |
1.2 |
Collecting Required Information |
3 days |
Wed 7/4/18 |
Fri 7/6/18 |
1.3 |
Developing Initial Documentation |
2 days |
Mon 7/9/18 |
Tue 7/10/18 |
1.4 |
Charter Document is Developed |
2 days |
Wed 7/11/18 |
Thu 7/12/18 |
1.5 |
Submission of documents |
1 day |
Fri 7/13/18 |
Fri 7/13/18 |
1.6 |
Kick off |
0 days |
Fri 7/13/18 |
Fri 7/13/18 |
2 |
Planning |
15.13 days |
Mon 7/9/18 |
Mon 7/30/18 |
2.1 |
Activity Listing |
17 hrs |
Mon 7/9/18 |
Wed 7/11/18 |
2.2 |
Scheduling activities |
3 days |
Wed 7/11/18 |
Mon 7/16/18 |
2.3 |
Complete Plan Development |
5 days |
Mon 7/16/18 |
Mon 7/23/18 |
2.4 |
Plan Review |
2 days |
Mon 7/23/18 |
Wed 7/25/18 |
2.5 |
Risk Management Plan |
3 days |
Wed 7/25/18 |
Mon 7/30/18 |
2.6 |
Plan Approval |
0 days |
Mon 7/30/18 |
Mon 7/30/18 |
3 |
Pre-location Activities |
20.38 days |
Mon 7/30/18 |
Mon 8/27/18 |
3.1 |
Checking sites for required space fit out |
2 days |
Mon 7/30/18 |
Wed 8/1/18 |
3.2 |
Site Selection |
3 days |
Wed 8/1/18 |
Mon 8/6/18 |
3.3 |
Design of the new office |
3 hrs |
Mon 8/6/18 |
Mon 8/6/18 |
3.4 |
Quotes of new design |
5 days |
Mon 8/6/18 |
Mon 8/13/18 |
3.5 |
Construction of the site |
2 wks |
Mon 8/13/18 |
Mon 8/27/18 |
3.6 |
Construction Completed |
0 days |
Mon 8/27/18 |
Mon 8/27/18 |
4 |
Relocation Activities |
24.88 days |
Wed 8/1/18 |
Tue 9/4/18 |
4.1 |
Pack up server, phones and computers |
0.5 days |
Wed 8/1/18 |
Wed 8/1/18 |
4.2 |
Backup of data |
1 day |
Wed 8/1/18 |
Thu 8/2/18 |
4.3 |
Installation at the new office location |
2 days |
Mon 8/27/18 |
Wed 8/29/18 |
4.4 |
Rewire and network offices |
3 days |
Wed 8/29/18 |
Mon 9/3/18 |
4.5 |
Move computers, phones and server to new location |
0.5 days |
Mon 9/3/18 |
Mon 9/3/18 |
4.6 |
Set up computer and phone access for all staff |
1 day |
Tue 9/4/18 |
Tue 9/4/18 |
4.7 |
Office relocated |
0 days |
Tue 9/4/18 |
Tue 9/4/18 |
5 |
Project Closed |
0 days |
Tue 9/4/18 |
Tue 9/4/18 |
The checking and reviewing of the financial records would be aligned with the formation of the effective alignment development The implication of the project utilization can be aligned for the simplification of the financial records for aligning with the successive formation of the operations (Isaac & Navon, 2014). The financial budget development would be helpful for easing the process of the improved development model. The reviewing of the financial records can be aligned for the implication of the successive factors. The review would be aligned for the alignment of the successive development of the improved functional and development model.
Administer and Monitor Project
The recruitment strategy for the project would comprise of the improved functional development method. The recruitment of the staff for the project can be aligned for the implication of the operational development model (Krieger et al., 2016). The staff recruitment would be aligned for the analysis of the profitable development of the activities. The recruitment of the project staff can be aligned for the formation of the operations. The staff recruitment would be aligned with the help of easy process development. The alignment would also be helpful for easing the process of the improved functional and development. The staff development would align for the utilization of the improved analysis process
The final report would be deployed for the alignment of the effective alignment method. The final report of the project would be based for the alignment of the functions so that implication of the improved functional and development model (Mooney et al., 2017). The final report of the project would be based on the alignment of the effective and smart development of the operations. The final status report for the project would be as follows,
Project Closure Report |
|
PROJECT NAME Red Office Relocation Project |
|
Department: |
|
Project Sponsor: |
|
Program Manager: |
|
Project Manager: |
|
Project Phase: |
|
Status Report Period: |
|
Date Submitted: |
|
Project Status Summary |
|
Budget |
|
Schedule |
|
Scope |
The post project review report would comprise of the checklist for the project as following,
Checklist Item |
Checked? |
Is the project completed in the estimated time and budget? |
þ |
Does the project deliverable meet the quality standard of the final project deliverable? |
þ |
Are the functions of the project aligned with the implication of professional development? |
þ |
Can the functions of the project be fused with the analysis of the effective and smart functional development? |
þ |
Does the deployment would be formed for the utilization of the functions supporting the implication of the marketing strategies? |
þ |
Alla, S., Pazos, P., & DelAguila, R. (2017). The Impact of Requirements Management Documentation on Software Project Outcomes in Health Care. In IIE Annual Conference. Proceedings (pp. 1419-1423). Institute of Industrial and Systems Engineers (IISE).
Isaac, S., & Navon, R. (2014). Can project monitoring and control be fully automated?. Construction management and economics, 32(6), 495-505.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.
Krieger, N., Waterman, P. D., Chen, J. T., Soobader, M. J., & Subramanian, S. V. (2016). Monitoring socioeconomic inequalities in sexually transmitted infections, tuberculosis, and violence: geocoding and choice of area-based socioeconomic measures—the public health disparities geocoding project (US). Public health reports.
Liu, W., & Walsh, T. (2018). The Impact of Implementation of a Clinically Integrated Problem-Based Neonatal Electronic Health Record on Documentation Metrics, Provider Satisfaction, and Hospital Reimbursement: A Quality Improvement Project. JMIR Medical Informatics, 6(2), e40.
Mooney, H., Carlson, J., Downing, K., & Tschirhart, L. (2017). Documentation in the Middle: Active Phase Project Documentation for Inclusive and Effective Team-Based Research.
O'Neill, R. (2015). Recommendations for Updating the Alaska Department of Transportation Construction Project Documentation Manual.
Sicard, M., Barragan, R., Muñoz-Porcar, C., Comerón, A., Mallet, M., Dulac, F., ... & Bravo-Aranda, J. A. (2016). Contribution of EARLINET/ACTRIS to the summer 2013 Special Observing Period of the ChArMEx project: monitoring of a Saharan dust event over the western and central Mediterranean. International journal of remote sensing, 37(19), 4698-4711.
To export a reference to this article please select a referencing stye below:
My Assignment Help. (2019). Requirements Management Documentation On Software. Retrieved from https://myassignmenthelp.com/free-samples/requirements-management-documentation-on-software.
"Requirements Management Documentation On Software." My Assignment Help, 2019, https://myassignmenthelp.com/free-samples/requirements-management-documentation-on-software.
My Assignment Help (2019) Requirements Management Documentation On Software [Online]. Available from: https://myassignmenthelp.com/free-samples/requirements-management-documentation-on-software
[Accessed 18 December 2024].
My Assignment Help. 'Requirements Management Documentation On Software' (My Assignment Help, 2019) <https://myassignmenthelp.com/free-samples/requirements-management-documentation-on-software> accessed 18 December 2024.
My Assignment Help. Requirements Management Documentation On Software [Internet]. My Assignment Help. 2019 [cited 18 December 2024]. Available from: https://myassignmenthelp.com/free-samples/requirements-management-documentation-on-software.