Project Scope
Pashendale Holdings Ltd (PHL) is a construction company that operates from Australia. The company now wishes to expand its customer base along with the shares in the market to gain competitive edge. There are strategies that are necessary to implement to carry out smooth expansion. Web presence is mandatory for the business organizations to reach out to the customers and maintain customer relations. PHL has decided to update its website through a redevelopment process. The content modification and UI enhancement will be the prime points of focus in the redevelopment activities. This will improve the customer experience and the human-computer interaction.
Some of the new features that will be included in the website are enhanced construction platforms, newer development models, latest updates on company activities, client feedback & testimonials, industry details, and smooth networking. The visual appeal and aesthetics of the site will improve for the betterment of the customer engagement and customer trust with the company (Bower and Finegan, 2009).
Project Scope
The team members will execute the following activities and these will be a part of the project scope.
- The members of the project team shall cover the analysis of the project requirements, feasibility study, estimations and calculations, and preparation of the Gantt chart for the project will carry out planning activities.
- Data collection techniques shall be executed by the members of the project team and prepare the requirements metrics.
- The project team will do the designing of the website and UI/UX design proposal shall be prepared.
- Source code development, definition of the database, and unit testing of the source code is included in the scope of the project (Corvello, Will and Ratta, 2017).
- Testing of the website to determine the flaws in the site and log the defects for the defects detected during the process (Fageha and Aibinu, 2013).
- The website implementation on the servers and the user trainings come under the scope of the project.
- The senior management will carry out the reviews and inspections and the management of the changes will come under the scope.
- Website support services
- Closure activities included in the scope are tracking of the project status, reporting tasks and activities, conversion of the data sets, documentation activities, technical writing, reflective analysis, and lessons learned.
There are several third parties involved in the project for providing the tools for design, development, testing, and implementation activities. The procurement of the tools and the negotiations required for procuring the tools will not come under the scope of the project (Mirza, Pourzolfaghar and Shahnazari, 2013).
Work Requirements
- Initiation & Planning Phase: The first set of work requirements is included in the initial and planning phase of the project. The members of the project team shall cover the analysis of the project requirements, feasibility study, estimations and calculations, and preparation of the Gantt chart for the project will carry out planning activities (Zwikael, 2009). The deliverables due at the end of this phase are Statement of Work (SoW) and a detailed project plan.
- Design & Development Phase: Data collection techniques executed by the members of the project team include interviews, domain analysis, observations, brainstorming sessions, and group discussions followed by the definition of the requirements metrics. The project team will do the designing of the website and UI/UX design proposal shall be prepared. Source code development, definition of the database, and unit testing of the source code is included in the scope of the project (Tran and Park, 2014). The deliverables due at the end of this phase are website design proposal and source code (Malahova and Tiwari, 2014).
- Testing & Implementation: Testing of the website to determine the flaws in the site and log the defects for the defects detected during the process is the first activity in this phase. The website implementation on the servers and the user trainings come under the work requirements of the project. The senior management will carry out the reviews and inspections and the management of the changes will come under this phase. The website support services are also a part of this phase. The deliverables due at the end of this phase are defect report and review report (Rose, 2013).
- Project Conversion & Closure: The closure activities in the work requirements are tracking of the project status, reporting tasks and activities, conversion of the data sets, documentation activities, technical writing, reflective analysis, and lessons learned. The deliverable due at the end of this phase is closure report. It is the last deliverable for the project and its submission will mark the end of the project (Zidane, Johansen and Ekambaram, 2015).
Schedule/Milestones
There are four phases in the project. Each of these phases has a set of sub-activities under it. The start date of the project is 10th August 2018 and the end date of the project is estimated as 10th December 2018. The total duration of the project comes out to be 87 days. The first phase of the project will start on 10th August 2018 and it will end on 21st August 2018. The second phase of the project is due to start on 22nd August 2018 and it will end on 8th October 2018. The second phase of the project will provide the source code of the website and its design as the deliverables. The third phase of the project will start on 9th October 2018 and it will end on 5th December 2018. The last project phase will start on 23rd October 2018 and it will end on 10th December 2018.
There are deliverables due at the end of each phase. The submission of these deliverables to the project sponsor and the acceptance of these deliverables will mark the project milestone.
Pricing
There are four phases in the project. Each of these phases has a set of sub-activities under it and there are costs associated with each activity. The project costs include cost of resources, development costs, design costs, testing costs, implementation costs, and closure costs. The start date of the project is 10th August 2018 and the end date of the project is estimated as 10th December 2018 with a total budget of $263,404. The first phase of the project will start on 10th August 2018 and it will end on 21st August 2018 with the budget of the phase as $29,152.
Work Requirements
The second phase of the project is due to start on 22nd August 2018 and it will end on 8th October 2018 with the budget of the phase as $144,776. The second phase of the project will provide the source code of the website and its design as the deliverables. The third phase of the project will start on 9th October 2018 and it will end on 5th December 2018 with the total budget as $60,172. The last project phase will start on 23rd October 2018 and it will end on 10th December 2018 with the budget of the phase as $29,304.
The technique used for the estimation of the project budget is bottom-up estimation technique. The cost estimation is included for the activities at the last level of the hierarchy. The activities at one level up are included and the cost estimation for them is included. In this manner, the overall cost of the project comes up.
Acceptance Criteria
Statement of Work (SoW)
The first deliverable due for the project is the Statement of Work. It is a document including the highlights of the project. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Introduction to the project is clear and concise
- Project scope is present in the document with in-scope and out-of-scope items (Zwikael and Globerson, 2004)
- Work requirements for every project phase are present in the document.
- The project schedule covering the names of the project activities, duration of each activity, start and finish dates, and project milestones are present in the document.
- Project pricing with the name and description of the technique and cost for each activity is present in the document.
- Acceptance criteria for each of the project deliverable are well defined.
Project Plan
The second deliverable due for the project is the Project Plan. It is a document including the details of the project-planning phase. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Clear definition and description of the project management methodology and system development methods
- Definition of the project scope with in-scope and out-of-scope items and the scope management process (Pandit and Tahiliani, 2015)
- Project schedule estimation technique and detailed project schedule
- Project budget estimation technique and detailed project budget
- Name and description of the project resources, roles and responsibilities of each resource in the project team
- Name and description of the key project stakeholders, techniques for managing the project stakeholders
- Communication management plan for the project – communication methods, communication strategies and protocols, communication reports and meeting guidelines
- Risk management plan – identification, analysis, treatment, monitoring, and closure of the project risks
- Conflict resolution and management approach
- Quality management plan for the project – planning, assurance, control, and continuous improvement of the project quality
Website Design Proposal
The third deliverable due for the project is the Website Design. It is a document including the details of the website design in terms of the wireframes and the UI/UX aspects of the site. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Design approach and methodology for the website for its redevelopment (Braganca, Vieira and Andrade, 2014)
- List and description of all the design tools is present in the proposal
- Wireframes of each of the web page are present in the proposal
- UI/UX aspects of the site are present in the proposal
- Design diagrams are included in the proposal
Source Code
The fourth deliverable due for the project is the Source code. It is a document including the details of the website development activity. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Name and description of the methodology for website development
- List and detail of the development tools
- Source code for the site
Defect Report
The fifth deliverable due for the project is the Defect Report. It is a document including the details of the testing activity on the website. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Name of the defect with a unique defect id and a status
- Defect summary with a one-liner description of the defect (Ditlevsen, 2003)
- Description of the defect in detail
- Steps for reproducing the defect
- Rate of reproducibility
- Priority/Severity score of the defect
- Resource assigned for handling the defect
- Date of filing the defect
- Set of comments and references
Review Report
The sixth deliverable due for the project is the Review Report. It is a document including the details of the review activities on the site. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Date of review is present in the report
- Summary of the review describing the deliverables/components under review (Mossalam and Arafa, 2016)
- Review comments with positive and negative aspects
- Areas of improvements and points to consider
- Future development activities and comments
Closure Report
The seventh deliverable due for the project is the Closure Report. It is a document including the details of the closure activities on the site. The Project Sponsor will review and accept the deliverable only when it meets the following set of criteria:
- Details of the project activities for the entire timeline of the project (Zohrehvandi, 2017)
- Lessons learned and reflective analysis
- Areas of improvement and current limitations
Acceptance
The contractor (name) gives the acceptance on the Statement of Work (SOW) for the website redevelopment project. The document is open to changes unless the desired quality levels are touched.
|
Pashendale Holding Ltd |
[Contractor company name] |
|
|
Company name |
Company name |
|
|
Full name |
Full name |
|
|
Title |
Title |
|
|
Signature |
Signature |
|
|
Date |
Date |
References
Bower, D. and Finegan, A. (2009). New approaches in project performance evaluation techniques. International Journal of Managing Projects in Business, 2(3), pp.435-444.
Braganca, L., Vieira, S. and Andrade, J. (2014). Early Stage Design Decisions: The Way to Achieve Sustainable Buildings at Lower Costs. [online] Available at: https://dx.doi.org/10.1155/2014/365364 [Accessed 4 Aug. 2018].
Corvello, V., Will, A. and Ratta, A. (2017). Routine project scope management in small construction enterprises. International Journal of Project Organisation and Management, 9(1), p.18.
Ditlevsen, O. (2003). Decision modeling and acceptance criteria. Structural Safety, 25(2), pp.165-191.
Fageha, M. and Aibinu, A. (2013). Managing Project Scope Definition to Improve Stakeholders’ Participation and Enhance Project Outcome. Procedia – Social and Behavioral Sciences, 74, pp.154-164.
Malahova, A. and Tiwari, A. (2014). A Methodology for Developing Web-based CAD/CAM systems. International Journal of Science and Engineering Applications, 3(6), pp.159-166.
Mirza, M., Pourzolfaghar, Z. and Shahnazari, M. (2013). Significance of Scope in Project Success. Procedia Technology, 9, pp.722-729.
Mossalam, A. and Arafa, M. (2016). The role of project manager in benefits realization management as a project constraint/driver. HBRC Journal, 12(3), pp.305-315.
Pandit, P. and Tahiliani, S. (2015). AgileUAT: A Framework for User Acceptance Testing based on User Stories and Acceptance Criteria. International Journal of Computer Applications, 120(10), pp.16-21.
Rose, K. (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)-Fifth Edition. Project Management Journal, 44(3), pp.e1-e1.
Tran, T. and Park, J. (2014). Development of integrated design methodology for various types of product — service systems. Journal of Computational Design and Engineering, 1(1), pp.37-47.
Zidane, Y., Johansen, A. and Ekambaram, A. (2015). Project Evaluation Holistic Framework – Application on Megaproject Case. Procedia Computer Science, 64, pp.409-416.
Zohrehvandi, S. (2017). Planning project closure phase in combined cycle power plant projects. Procedia Computer Science, 121, pp.274-281.
Zwikael, O. (2009). The Relative Importance of the PMBOK® Guide’s Nine Knowledge Areas during Project Planning. Project Management Journal, 40(4), pp.94-103.
Zwikael, O. and Globerson, S. (2004). Evaluating the quality of project planning: a model and field results. International Journal of Production Research, 42(8), pp.1545-1556.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
