Website Redevelopment Project – Scope, Schedule, Pricing, And Acceptance Criteria

Introduction/Background

Pashendale Holdings Ltd (PHL) is an Australian construction company that has decided to follow the strategies to expand its customer base and market share. To achieve the strategic goals, the CEO of the company has recommended the upgrade of the current website of PHL. The project is a website redevelopment project to include richer content and new elements on the site. The primary purpose of the website redevelopment is to enhance the user experience of the site and to improve upon the customer feedback and customer interaction services available on the site.

The website shall have the elements as new construction platforms, enhanced building developments, client testimonials, latest company news, industry information, and enhanced network platform. The redevelopment of the website will provide the organization with the ability to meet the changing customer requirements and gaining the opportunity to have competitive edge in the market (Bower and Finegan, 2009).

The project scope shall cover the project planning activities in which the project plan, implementation plan, test plan, schedule, training plan, and transition plan. The design and development activities in the project scope shall include the UI/UX design of the web pages and source code development for the site (Corvello, Will and Ratta, 2017). The scope covers the web site testing and reporting of the defects that may occur. The scope will also cover the implementation of the site, training to the end-users, and documentation for project closure (Fageha and Aibinu, 2013).  

The project team will not carry out any of the marketing activities for the company. The distribution and advertising tasks and processes are also not included in the project scope. The steering committee and management will carry out all of the negotiations with the third-party vendors. The team members will not participate in any of such negotiations and discussions (Mirza, Pourzolfaghar and Shahnazari, 2013).  

• Initiation & Planning Phase: It is the first project phase that shall cover the approval on the project requirements, analysis of the business case, and project planning activities. The Statement of Work and Project Plan are the deliverables to submit at the end of this phase (Zwikael , 2009). The planning activities include the estimation of the project scope, schedule, and budget along with the planning of resources, stakeholders, training, transition, and implementation.
• Design & Development Phase: The web site design in the form of UI/UX elements is the first deliverable of this phase. The source code development is the task of the development team and the source code is the deliverable associated with the task (Tran and Park, 2014). The phase includes the creation of the wireframes of each of the pages. The web developer also does unit testing before passing the build to the testing team for verification, validation, and defect logging (Malahova and Tiwari, 2014).
• Testing & Implementation: System testing, regression testing, performance testing, security testing, and usability testing are the testing activities that the team will execute. The website implementation and deployment is also a significant project task in this phase (Rose, 2013).
• Project Conversion & Closure: The last phase is the closure phase that will cover training and transition activities. The final documentation and technical writing is also an activity for this phase. The submission of closure report will mark the end of the project (Zidane, Johansen and Ekambaram, 2015).

The project schedule is present in the table below and includes the name of all the project tasks and activities. The duration of each activity and the corresponding start and finish dates are present. The project duration is 87 days with the start date of the project as 27 August 2018 and the finish date as 25 December 2018. There are four phases in the project as project planning, design & development, testing & implementation, and conversion & closure phase.

WBS	Task Name	Duration	Start	Finish	Predecessors	Resource Names
1	Website Redevelopment Project	87 days	Mon 27-08-18	Tue 25-12-18
1.1	Project Planning	8 days	Mon 27-08-18	Wed 05-09-18
1.1.1	Requirements Specification Analysis	3 days	Mon 27-08-18	Wed 29-08-18		Web Developer, Business Analyst, Project Manager, Web Designer ,Database Engineer, Implementation Engineer, System Tester
1.1.2	Feasibility Study & Scope Determination	2 days	Thu 30-08-18	Mon 03-09-18	3	Business Analyst, Finance Officer, System Tester, Web Developer, Implementation Engineer, Security Tester
1.1.3	Project Estimations – Scope, Schedule, Budget, Resources	2 days	Thu 30-08-18	Fri 31-08-18	3	Finance Officer, Project Manager
1.1.4	Project Planning – Testing, Implementation, Training, Transition	2 days	Tue 04-09-18	Wed 05-09-18	5,4	Project Manager, Database Engineer, Implementation Engineer, System Tester, Trainer, Business Analyst
1.1.5	Work Breakdown Structure	1 day	Tue 04-09-18	Tue 04-09-18	4	Project Manager, Web Designer ,Web Developer, Finance Officer, Business Analyst, Implementation Engineer
1.1.6	Milestone 1: Statement of Work & Project Plan	0 days	Wed 05-09-18	Wed 05-09-18	6
1.2	Design & Development	34 days	Thu 06-09-18	Tue 23-10-18
1.2.1	Data Collection & Requirements Metrics	6 days	Thu 06-09-18	Thu 13-09-18	8	Business Analyst, Project Manager, Finance Officer
1.2.2	Procurement of tools and equipment	4 days	Thu 06-09-18	Tue 11-09-18	8	Hardware[1],Software[1]
1.2.3	Website Design – UI/UX Aspects & Wireframes	6 days	Fri 14-09-18	Fri 21-09-18	10	Web Designer
1.2.4	Review of Website Design Proposal	3 days	Mon 24-09-18	Wed 26-09-18	12	Web Developer, Project Manager, Business Analyst, Implementation Engineer, Security Tester, System Tester
1.2.5	Commencement of changes and source code development	15 days	Thu 27-09-18	Wed 17-10-18	13	Web Designer ,Web Developer
1.2.6	Database definition and unit testing	4 days	Thu 18-10-18	Tue 23-10-18	14	Database Engineer, Web Developer
1.2.7	Milestone 2: Website Design Proposal, Source Code	0 days	Wed 17-10-18	Wed 17-10-18	12,14
1.3	Testing & Implementation	42 days	Wed 24-10-18	Thu 20-12-18
1.3.1	Website Testing	10 days	Wed 24-10-18	Tue 06-11-18	15	Security Tester, System Tester, Web Developer
1.3.2	Implementation on PHL Servers	21 days	Wed 07-11-18	Wed 05-12-18	18	Implementation Engineer
1.3.3	User Trainings	5 days	Thu 06-12-18	Wed 12-12-18	19	Trainer, Project Manager
1.3.4	Review & Inspection Processes	4 days	Thu 13-12-18	Tue 18-12-18	20	Business Analyst, Implementation Engineer, Project Manager, Security Tester, System Tester, Finance Officer, Database Engineer
1.3.5	Management of Changes	2 days	Tue 18-12-18	Thu 20-12-18	21	Database Engineer, Implementation Engineer, Web Designer ,Web Developer, Business Analyst
1.3.6	Website Support Services	2 days	Wed 19-12-18	Thu 20-12-18	21	System Tester, Database Engineer, Implementation Engineer, Security Tester
1.3.7	Milestone 3: Defect Report, Review Report	0 days	Tue 18-12-18	Tue 18-12-18	18,21
1.4	Conversion & Closure	35 days	Wed 07-11-18	Tue 25-12-18
1.4.1	Status Tracking & Reporting	2.5 days	Thu 06-12-18	Mon 10-12-18	18,19	Implementation Engineer, Project Manager, System Tester, Web Designer ,Web Developer
1.4.2	Data conversion and migration	2.5 days	Wed 07-11-18	Fri 09-11-18	15,18	Database Engineer
1.4.3	Documentation & Technical Writing	3 days	Wed 07-11-18	Fri 09-11-18	15,18	Technical Writer
1.4.4	Reflective Analysis, Lessons Learned for Closure	3 days	Fri 21-12-18	Tue 25-12-18	23	Project Manager, Business Analyst, Database Engineer, Finance Officer, Implementation Engineer, Security Tester, System Tester, Technical Writer, Web Designer ,Web Developer
1.4.5	Milestone 4: Closure Report	0 days	Tue 25-12-18	Tue 25-12-18	29

There are several costs involved in the project viz. cost of tools and equipment, cost of project resources, training costs, support & maintenance costs, development costs, design costs, and transition costs. The total cost of the project is $263,404. The cost is included using the bottom-up approach in which the activity present at the lowermost level is picked up first. The estimation of the activities present up in the hierarchy is included in the next series of steps.

WBS	Task Name	Cost
1	Website Redevelopment Project	$263,404.00
1.1	Project Planning	$29,152.00
1.1.1	Requirements Specification Analysis	$13,032.00
1.1.2	Feasibility Study & Scope Determination	$3,704.00
1.1.3	Project Estimations – Scope, Schedule, Budget, Resources	$2,864.00
1.1.4	Project Planning – Testing, Implementation, Training, Transition	$5,656.00
1.1.5	Work Breakdown Structure	$3,896.00
1.1.6	Milestone 1: Statement of Work & Project Plan	$0.00
1.2	Design & Development	$144,776.00
1.2.1	Data Collection & Requirements Metrics	$12,768.00
1.2.2	Procurement of tools and equipment	$95,000.00
1.2.3	Website Design – UI/UX Aspects & Wireframes	$3,408.00
1.2.4	Review of Website Design Proposal	$11,376.00
1.2.5	Commencement of changes and source code development	$17,520.00
1.2.6	Database definition and unit testing	$4,704.00
1.2.7	Milestone 2: Website Design Proposal, Source Code	$0.00
1.3	Testing & Implementation	$60,172.00
1.3.1	Website Testing	$17,360.00
1.3.2	Implementation on PHL Servers	$12,600.00
1.3.3	User Trainings	$5,300.00
1.3.4	Review & Inspection Processes	$17,760.00
1.3.5	Management of Changes	$2,528.00
1.3.6	Website Support Services	$4,624.00
1.3.7	Milestone 3: Defect Report, Review Report	$0.00
1.4	Conversion & Closure	$29,304.00
1.4.1	Status Tracking & Reporting	$7,680.00
1.4.2	Data conversion and migration	$1,440.00
1.4.3	Documentation & Technical Writing	$1,680.00
1.4.4	Reflective Analysis, Lessons Learned for Closure	$18,504.00
1.4.5	Milestone 4: Closure Report	$0.00

Project Scope

The document shall have the project background, highlights of project scope, and project work requirements. The SOW shall also have a detailed account of the project schedule with start and finish dates of the project activities, duration of the activities, and deliverable/milestone schedule. The cost of each project phase along with the total cost and acceptance criteria are the mandatory sections in the SOW (Zwikael and Globerson, 2004).

The document shall list out the project description, aims, objectives, project scope, project schedule, project costs, stakeholder list, resources, test plan, implementation plan, training, and transition plan (Pandit and Tahiliani, 2015).

The design proposal shall have UI/UX design and wireframes for each of the web page and the design diagrams as well. The Project Manager and Chief Marketing Officer (CMO) must approve the deliverable (Braganca, Vieira and Andrade, 2014).

The lines of code for each of the web pages and the validation/verification of the same after carrying out unit testing

The detailed account of project defects as detected after the conduction of testing activities. The defect shall have the fields as a unique defect id, defect summary, description of the defect, reproduction rate, resource responsible for resolution, steps to reproduce, and defect status (Ditlevsen, 2003).

The report shall have the comments of the reviewer with the sections as areas of improvements, points to remember, and list of changes. The date of review, name of the reviewer, and additional comments are the other necessary elements for the deliverable (Mossalam and Arafa, 2016).

The final deliverable of the project must have the sections as lessons learned, areas of improvements, project limitations, and a brief summary of the project activities (Zohrehvandi, 2017).

The contractor named below provides acceptance on the Statement of Work (SOW). The parties have the authority to recommend the changes unless the required level of quality is present.

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.