Strategic Project Management: PHL Website Development SOW Report

This report presents a Statement of Work (SOW) for the website redevelopment project of Pashendale Holdings Ltd. (PHL), an Australian construction company. The project aims to enhance PHL's marketing and customer service through a new website featuring client testimonials, new building developments, company news, and an affiliate network platform. The SOW outlines the project's scope, requirements, and the Software Development Life Cycle (SDLC) phases, including planning, defining, designing, building, testing, and deployment. The report emphasizes the importance of intranet integration, resource allocation, and adherence to SDLC phases. It details the project's various phases such as planning, defining, implementation, and conversion, including milestones and acceptance criteria. The project's success hinges on effective planning, design, implementation, and training, ensuring the website meets the specific needs of PHL and its clients.

Running Head: SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Name of the Student
Name of the University
Author Note

1SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Executive Summary
Pashendale Holdings Ltd. or PHL has ensured to maintain its esteemed position in the field of
constructions for a brief period of time. Of late, with the evolution of market with the help of
technology it is imperative and also a step up for those institutions to develop with the emerging
trend. The basic efficiency of any industry can be measured in terms of its performance and how
swift can it deliver products, based on that one can say that efficiency of a company is directly
proportional to the time taken to deliver the product. This is the fundamental reason as to why
PHL Company is developing its website.

2SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Table of Contents
Executive Summary.............................................................................................................1
Introduction..........................................................................................................................4
Project Scope.......................................................................................................................4
Requirement.........................................................................................................................5
Concept of Planning Phase..............................................................................................7
Concept of Defining Phase..............................................................................................7
Concept of Designing Phase............................................................................................8
Concept of Building and Testing Phase...........................................................................8
Concept of Deployment Phase.........................................................................................8
Relevant Project Phases in the given case study.............................................................8
Planning.......................................................................................................................9
Defining.......................................................................................................................9
Implementation..........................................................................................................10
Conversion.................................................................................................................10
Milestone...........................................................................................................................10
Acceptance criteria............................................................................................................11
Acceptance criteria related to the given case study.......................................................11
Conclusion.........................................................................................................................13
Bibliography :....................................................................................................................14

3SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Introduction
Amidst all the companies that are related to the construction industry, PHL or Pashendale
Holdings Ltd. has secured an appreciable position in Australia, with the help of an enhanced
website based on a previous model. The functionality of this website is diverse in nature as it
comprises of testimonials provided by clients, new building projects that are undertaken by the
company along with information about several other industries as well. The incorporation of user
friendly interface along with all of these criteria signifies that the value of customer is uphold
with utter respect in the hindsight of the company’s management. The reason of launching this
website is to attain a specific purpose for the greater good for the company, which is why PHL’s
CEO - Virna Pashendale approved of this project to redevelop the website. The sole purpose of
this website is to cater according to the specific needs of clients and for that the website is
characterized with plethora of choice. The aim of this report revolves around the concept of
designing a SOW or Statement of Work based on the discussion mentioned below.
Project Scope
With the inception of the technology era it is becoming very difficult for companies to
sustain their client base through manual effort. Thus evolving from hardcopies to softcopies is a
just path for several companies, as is the case for Pashendale Holdings Ltd. One of the major
drawback in case of PHL is the lack of information technology infrastructure. In modern days the
absence of a solid IT framework hinders the company in unimaginable ways so as to cope up
with the shortcomings, PHL has devised a plan to redesign the website. Previously, they
outsource the implementation, design training and testing for the website. Now they are
developing their own framework as per their own requirement. PHL wants to enhance the

4SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
website for better customer service and marketing purpose, for that reason there are multiple
processes that needs to be done. The scope of the project’s work comprises of several stages such
as minute planning of each and every stages, execution of those pre planned steps and executing
them accordingly, after that comes the significant stage of implementing and finally the
necessary training to the employees about the new website. All of this stages will be done
keeping one primary thing in the hindsight that exclusion of PHL internal site is a mandatory
factor, thus adequate resources for completion of the project is a must factor for the designer of
the website.
Requirement
The special requirement of the above mentioned project is that Pashendale Holdings
Ltd.’s intranet service in the new website, which brings us to the topic of intranet. The sharing of
information, system and services over a computer network within an organization can be defined
as Intranet. Intranet incorporates various protocols that are familiar with us. Services that can be
found there ranges from HTTP, File Transfer or emails. In other words, it can be interpreted as
further extension and development of a private network by incorporating a part of the internet, by
allowing getaway connection through one or more computer, which is confined within an
organization. The utilization of intranet is almost similar to internet, which has changed the
vision of work culture at international level, the intranet has drastically change the way the entire
organization operates, which is predominantly vivid in departments like collaborations, customer
relationship management and utilization of project management concept. Intranets are usually
managed in-house by the communications, human resources or IGT facets of the company and
because of the intricacy and diversity of the content many intranets and possess a complex
network architecture than the company’s official website, hence it requires a scheduled and

5SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
regular team effort to maintain the network. Along with this it drastically enhance the bottom
line, since all the information required for employee manual, requisition forms and contact list
and many more can be accessed electronically through the internet. This saves cost on the like of
printing and distributing since time is also saved because data can be saved on an as needed
basis. Processes such as benefit enrollment are centralized and expedited. If one combine all
these assets and more one can see that overall work place productivity and operations are
optimized, for this reason it has taken long for corporations to realize the true potential of
intranets, in spite of centrally storing all the data in one place intranets open up new horizon by
becoming communication hubs for many organizations, thereby prompting several companies to
hire bodies that will socialize their intranet and augment correspondence amongst the personnel.
Microsoft SharePoint is the most common software used for intranet in many organizations.
Apart from that, the designer for the website must ensure that it has sufficient resources to design
the project, based on those designs to build and implement the designed project and trouble shoot
any flaws that are present in the implemented website. In case of every software project one of
the fundamental requirement is to maintain every phases of SDLC minutely. Software
Development Life Cycle is shortly known as SDLC, the main objective of SDLC is to
manufacture high quality systems that provides customer requirements and satisfactory delivery.
It works current and planned information technology infrastructure effectively and efficiently
and it is beneficial in terms of both time and money as it can be enhanced simply within a short
period of time.

6SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Figure 1: SDLC
Source: (Lemke 2018)
Concept of Planning Phase
One of the most fundamental and significant stage in SDLC is the requirement analysis.
As per the client’s requirement the business analytics obtained from the needs and necessities of
client’s business and documents, however, the development team were also provided with the
same requirements from the aspects of the Business Requirement Specifications. Assurance in
terms of quality and determining the associated risk along with it plays a pivotal role in this stage
(Lemke 2018). The sole purpose of this stage is to analyze various steps that are needed to
complete the project successfully.
Concept of Defining Phase
The following phase is defining the requirements of the product and to document it,
thereby it is ready to be approved by market analyst or the customer (Rastogi 2015). One of the
tools that are used to complete this stage is SRS, also known as Software Requirement

7SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Specification, its function is to make sure that all the products that are required to complete the
project are already available.
Concept of Designing Phase
Depending on the specified requirements by SRS, usually multiple approaches to design
the architecture of the product is proposed in DDS, also known as Design Document
Specification, which also documents the approaches (Lemke 2018). All of the significant stake
holders ranging from Project Director to Software Designer review the outcome of the DDS as it
comprises of several parameters that are crucial in nature and falls under a continuum ranging
from assessing the robustness of the product to modularity of the design keeping certain
constraints such as time and budget in hindsight.
Concept of Building and Testing Phase
This is one of the most significant stage in SDLC since development actually starts in this
stage. If the design of the project is done accurately then the code generation hassle is lessened at
a great measure. The name testing phase is pretty self-explanatory as activities in this phase
mostly involves testing for product shortcomings.
Concept of Deployment Phase
After completion of the testing phase the product is deployed in real time market and
depending on the feedback of the user if any changes are required then appropriate measures are
taken by the contractor of the project.
Relevant Project Phases in the given case study
In each step of the project, there are diverse range of certain task that must be performed
by the website designer to complete the redevelopment process. The several phases present in the

8SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
task such as planning, design, implementation and conversion phase, each one of the phases are
described in detail later on.
Planning
Primary step in the redevelopment of the project is known as planning phase. This is the
most pivotal stage in the entire process as it outlines the basic steps, based on which the entire
framework of the process will be developed (Sharma and Mishra 2017). In this stage, constructor
present a detailed plan of the entire project to PHL that comprises of scheduling, breaking down
of work structure and the planning of testing, implementation and training are discussed with
PHL’s personnel. The basic purpose of this planning stage is for the designer to get approved and
to be reviewed by PHL’s concerned authority.
Defining
In the next phase, the contractor of the project is involved with the defining the basic
design of the project. Cooperation from PHL is highly solicited by the designer in the process of
accumulating all the necessary pre-requisites for the completion of the project, which falls under
a continuum ranging from establishing metrics to designing and developing the website based on
the gathered requirements. Completion of this project is marked with the approval from PHL
concerned personnel. After approval the contractor update the PHL in weekly meetings of all the
task done (Sharma and Mishra 2017). During this phase, all the coding necessary for the
completion of the project is performed by the contractor and update PHL with minute details of
testing plan, incorporation of all necessary contents provided by PHL in the new website. One of
the significant step in this stage is conducting a test in the contractor’s iLab and perform the
same test again in the beta release which is limited. Following this process the contractor has to

9SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
identify and determine the root cause of trouble (if any trouble arises) and trouble shoot
accordingly.
Implementation
The designing phase is followed by the implementation phase, which is versatile in
nature. Implementation of the new website on the server of the PHL are done with a constant
service provided by the contractor. This service will be provided by the contractor till the project
ends. After this stage the contractor will train the personnel from PHL as per the planning stage
determines.
Conversion
Following the implementation stage comes the next phase known as conversion. Along
with all the document provided by the contractor of the project to PHL the closure of the project
is also presented. The closure of the project will be reviewed by the concerned authority of PHL
and approved if all the tasks from the checklist is completed by the contractor.
Milestone
Tas
k Mode
Task
Name
Duratio
n
Star
t
Finis
h
Predecessor
s
Auto
Scheduled
waiting
for approval 1 day Thu
10/17/19
Thu
10/17/19 7
Auto
Scheduled
Website
Design Review 1 day Thu
10/24/19
Thu
10/24/19 12
Auto
Scheduled
Assignin
g Contractor 2 days Thu
9/26/19
Fri
9/27/19 2
Auto
Scheduled
Training
provided to
employees
2 days Thu
12/12/19
Fri
12/13/19 23
Auto
Scheduled
Project
Formally Closed 3 days Thu
12/19/19
Mon
12/23/19 26

10SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Table 1: Milestones of the project.
(Source: Created by the author using MS project)
Acceptance criteria
In case of a software designing and development project, the communication between
client and the contractor of the project plays a pivotal role in resolving the requirements of the
products. The sole purpose of for developing a product (software) from client’s perspective is to
achieve specific user’s requirements (Rastogi 2015). One of the major characteristics of
acceptance criteria is declaring an appropriate functionality, for an instance, if an application is
being developed with a purpose of sending a packet of information from one end user to another
user, then its functionality should be known as user’s requirements. Acceptance criteria can be
described as a list that formally narrates the fundamentals of user requirement and documented
scenario in terms of product. In other words, acceptance criteria comprises of client’s intent
however the actual solution is absent in acceptance criteria, hence it is contractor’s responsibility
to clarify any complex situation and resolve it. There are various methodologies while creating
an acceptance criteria one of the noteworthy is Scrum (Jain and Suman 2015). Scrum can be
defined as an agile technique through which the team assigned to develop the software works
with acceptance criteria. The basic functionality of Scrum is to simplify the intent of the client
for better understanding of the contractor. An acceptance criteria can be either good or bad
depending on the outcome of the end product. It can be described as a good acceptance criteria if
it encompasses the intents of the client in simple terms and the end product is exactly what the
client wished for, otherwise it is considered bad.

11SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Acceptance criteria related to the given case study
The relevant acceptance criteria form the given case study are as follows:
i) The website must contain testimonials provided by clients.
ii) The content of the website must encompass new building projects that are
undertaken by the company along with information about several other industries
as well.
iii) The website must be user friendly.
iv) The contractor of the project must verify that it has sufficient resources for
completion of the project.
v) The contractor is required to update PHL with the ongoing process regarding the
project in a written format per week.
vi) The design review of the website is to be completed within three weeks after the
commencement of the project.
vii) The implementation review of the website is to be completed within six weeks
after the commencement of the project.
viii) PHL’s personnel’ training is to be finalized within one week after the after the
implementation review. The completion review of the project is to be completed a
ix) Week prior to Christmas Day thereby the final closure of the project can be done
by Christmas Eve.
The PHL personnel responsible for accepting all contents of the product from the
contractor of the development project is Sennveasna Naveen, the Chief Marketing Officer of
PHL. CMO along with three other member of PHL are entrusted with the responsibility of
ensuring that all stages of the website designing project is completed as agreed upon.

12SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Conclusion
To conclude, one can say that the project of redevelopment of the website is
undertaken by the concerned authority of the company with a sole purpose of maintaining
their esteemed position in the field of construction. To remain at the vanguard of the
construction industry PHL has devised this strategy to captivate their clientele. With the
inception of the new website the company will look forward to enhance their output
furthermore. One can infer that valuing opinions of customer and client base fuelled the
concerned authority of the company to carry out this arduous task.

13SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Bibliography :
Ali, K., 2017. A Study of Software Development Life Cycle Process Models. International
Journal of Advanced Research in Computer Science, 8(1).
Borg, I. and Tuten, T.L., 2016. Early versus later respondents in intranet-based, organizational
surveys. Journal of Behavioral and Applied Management, 4(2), p.1069.
Chowdhury, A.Z.M., Bhowmik, A., Hasan, H. and Rahim, M.S., 2018. Analysis of the veracities
of industry used software development life cycle methodologies. arXiv preprint
arXiv:1805.08631.
Dingsøyr, T., 2019. Knowledge management in medium-sized software consulting companies:
An investigation of intranet-based knowledge management tools for knowledge cartography and
knowledge repositories for learning software organisations. arXiv preprint arXiv:1903.11854.
Jain, R. and Suman, U., 2015. A systematic literature review on global software development life
cycle. ACM SIGSOFT Software Engineering Notes, 40(2), pp.1-14.
Karim, N.S.A., Al Ammar, F. and Aziz, R., 2017, September. Ethical software: integrating code
of ethics into software development life cycle. In 2017 International Conference on Computer
and Applications (ICCA) (pp. 290-298). IEEE.
Kerzner, H., 2017. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
King, D., 2017. The Complete Website Planning Guide: A step by step guide for website owners
and agencies on how to create a practical and successful scope of works for your next web
design project. Ireckon Publishing.

14SOW OF PHL’S WEBSITE DEVELOPMENT PROJECT
Kneuper, R., 2017. Sixty years of software development life cycle models. IEEE Annals of the
History of Computing, 39(3), pp.41-54.
Kumar, C. and Yadav, D.K., 2017. Software defects estimation using metrics of early phases of
software development life cycle. International Journal of System Assurance Engineering and
Management, 8(4), pp.2109-2117.
Lemke, G., 2018. The Software Development Life Cycle and Its Application.
Rastogi, V., 2015. Software development life cycle models-comparison, consequences.
International Journal of Computer Science and Information Technologies, 6(1), pp.168-172.
Sharma, A. and Misra, P.K., 2017. Aspects of enhancing security in software development life
cycle. Advances in Computational Sciences and Technology, 10(2), pp.203-210.
Shylesh, S., 2017. A Study of Software Development Life Cycle Process Models. In National
Conference on Reinventing Opportunities in Management, IT, and Social Sciences (pp. 534-
541).
Srivastava, K., 2019. A Study of Software Development Life Cycle Models in Security
Secenario. International Journal of Innovative Knowledge Concepts, 7(3), pp.07-09.