Limited Offer Get 25% off — use code BESTW25
No AI No Plagiarism On-Time Delivery Free Revisions
Claim Now

E-commerce site for book selling Project Plan

By /
E-commerce site for book selling Project Plan

Version No: 19-03-2020 Copy: 1

Document Acceptance and Release Notice

This document is authorised for release once all signatures have been obtained.

PREPARED:SNEHA MARUPAKULA -41724Date:24/03/2020
(for acceptance)RAVI NUKALA -41505


SWAMY GUDURU-41568 KAUR NAVEET -43310

ACCEPTED:
Date:24/03/2020
(for release)Dr Paul Darbyshire Project Sponsor, VIT

Table of Contents

Introduction 7

Objectives of the Project 7

Scope 7

Areas to include/ Exclude 7

System Interface 7

Major Deliverable 7

Assumptions 7

Organization 7

Structure 7

Roles and Responsibilities 7

Scheduling 8

Control and Reporting 8

Risk/ Constraints Management 8

Delivery Strategy 8

Approach/ Methodology 8

Standards and Procedures 8

Introduction

The project that is being carried out is the development and deployment of the e-commerce site for book selling. The web presence has become an integral part of the business firms and operations in the present times. The majority of the users now wish to access the online channels to make respective purchases from the business organizations. The lack of web presence has a negative impact on the customer engagement and it can become extremely difficult to retain the customers without the web channels (Brown, 2017). The web portal in the form of a website is one of the most common methods to ensure the web presence and interact with the customers along with the conduction of the e-commerce operations. The book selling by an organization is also being launched on the e-commerce site to ensure that increased number of customers can be involved in the business.

Currently, the business does not have a web channel to provide the customers with the ability to purchase books online. This has led to the gaps in the customer engagement and satisfaction levels as the web presence is integral to the business firms in the present era. The customers also expect the businesses to provide them with the options to browse and purchase products online. The e-commerce site for book selling will bridge the existing gaps and will provide an online channel to the customers to buy the books online. The e-commerce site will provide the customers with an online portal to buy the books which will lead to the expansion of the customer base by at least 33%. The customers currently look for an online channel to serve their needs and the implementation of the site will enhance the customer satisfaction percentage by a minimum of 70% (Madison, 2015).

Objectives of the Project

The objective of the E-commerce site for Book Selling project is to increase the customer base by a minimum of 33% and witness the customer satisfaction scores to be improved by 70%.

Scope

Areas to include/ Exclude

The scope of the project will include the planning and analysis of the e-commerce site that is to be developed for book selling. The responsive web design and the source code development using PHP and MySQL languages will be a part of the scope. The parallel testing and customer collaboration followed by the deployment and maintenance of the site will be the part of the project scope (Boateng, 2015).

The project scope will not cover the marketing of the e-commerce site among the customers or the third-parties.

System Interface

Graphical User Interface (GUI)

The e-commerce web site for book selling will be developed for the customers to give them the ability to purchase and view books online. The site shall have a simple and attractive user interface. For this purpose, the e-commerce site will be designed as per the responsive web design principles. The users will be able to access the site on the desktop and mobile platforms in the desired orientation (Bott & Mesmer, 2019). The GUI will be kept simple with a consistent layout to avoid any issues around inconsistency. Also, it will have easy navigation and the over-scrolling on any page will be avoided.

Security Interface

The e-commerce site will require the customers to register themselves and the account history of the customers will be maintained by the site. The site will also have the details of the books and the information around their availability. The customers will be able to purchase the books online and the payment information will be stored on the site. These information sets will be critical and must not be exposed to the third-parties (Kalyani & Mehta, 2019). As a result, the site will have an in-built security interface with the session management, multi-fold authentication, malware protection, access control, and encryption mechanisms. This will keep the site information protected from the security attacks.

Major Deliverable

  • Project Proposal: The project proposal will be a document that will comprise of a detailed summary of the e-commerce project. It will also give the highlights of the project scope and implementation strategy along with the project assessment, and governance details.
  • Project Plan: The document will give a detailed account of the plans that will be implemented in the project and will elaborate the schedule, effort, etc. in detail (Rajasekaran, 2015).
  • E-commerce site design: The design will include the UI/UX aspects of the site.
  • Source code: The source code of the site will be developed in the PHP language and it will be delivered.
  • User Feedback Reports: The project will be conducted in sprints the feedback will be obtained from the users after every sprint. The reports will be prepared and delivered.
  • Closure Report: This will be the final project report.

Assumptions

The main assumptions are:

  1. The e-commerce site for book selling will become the primary channel for the business to sell the books.
  2. The resources involved in the project team will be available for a minimum of 40 hours in a week.

Organization

Structure

Roles and Responsibilities

  • Project Admin: Overall project planning, control and management, reviews, and communication
  • Scrum Master: Agile sprints management and planning
  • Web Developer 1: Development of the functional and non-functional aspects of e-commerce site
  • Web Developer 2: Development of the functional and non-functional aspects of e-commerce site (Khalid, Butt, Jamal, & Gochhait, 2020)
  • Tester 1: Website testing and defect reporting
  • Tester 2: Website testing and defect reporting
  • UI/UX Designer 1: Response web design and layout
  • UI/UX Designer 2: Response web design and layout
  • Senior Tech Engineer: tech support and guidance

Scheduling

Work Breakdown Structure

Resource Allocation, Activity Duration, Precedence, and Project Tasks

WBSTask NameDurationStartFinishPredecessorsResource Names
1E-commerce site for book selling132 days19 March 202018 September 2020

1.1Project Initiation13.1 days19 March 202007 April 2020

1.1.1Business context and project goals determination4.1 days19 March 202025 March 2020
Project Admin
1.1.2Project complexity and benefits2.6 days25 March 202027 March 20203Scrum Master
1.1.3Objectives1.9 days27 March 202031 March 20204Project Admin
1.1.4Project governance structure0.7 days25 March 202025 March 20203Project Admin
1.1.5Business assessment and high-level scope2.2 days31 March 202002 April 20205Scrum Master
1.1.6Key project risks and feasibility determination2.3 days02 April 202007 April 20207Senior Tech Engineer
1.1.7Milestone 1: Project Proposal0 days07 April 202007 April 20208
1.2Planning12.8 days02 April 202021 April 2020

1.2.1Detailed project scope3.4 days02 April 202008 April 20207Project Admin
1.2.2Project development and management methodologies2.6 days02 April 202007 April 20207Scrum Master
1.2.3Project Estimates6.4 days08 April 202016 April 2020

1.2.3.1Schedule- WBS, Gantt3.6 days08 April 202013 April 202011Project Admin
1.2.3.2Budget and resources2.8 days13 April 202016 April 202014Project Admin
1.2.4Milestone 2: Project schedule, effort, and budget0 days16 April 202016 April 202015
1.2.5Project elements3 days16 April 202021 April 202016
1.2.5.1Risks and constraints1.5 days16 April 202020 April 202015Senior Tech Engineer
1.2.5.2Communication and quality1.5 days16 April 202020 April 202015Project Admin
1.2.5.3Resources and stakeholders1.5 days20 April 202021 April 202018,19Project Admin
1.2.6Milestone 3: Project Plan0 days21 April 202021 April 202020
1.3Set-up for execution5.4 days21 April 202028 April 2020

1.3.1Eclipse platform and design tools3.2 days21 April 202024 April 202021Senior Tech Engineer
1.3.2Test tools – Selenium, Bugzilla2.5 days21 April 202024 April 202021Tester 1
1.3.3Installation of the tools2.2 days24 April 202028 April 202023,24Senior Tech Engineer
1.3.4Milestone 4: Set-up for project execution0 days28 April 202028 April 202025
1.4Agile SCRUM – Site Development90.25 days29 April 202002 September 2020

1.4.1Sprint 118.05 days29 April 202025 May 2020

1.4.1.1E-commerce site – login, layout, registration, and logout2.3 days29 April 202001 May 202026Scrum Master, Senior Tech Engineer
1.4.1.2Web pages design and development9.25 days01 May 202014 May 202029UI/UX Designer 2,UI/UX Designer 1,Web Developer 2,Web Developer 1
1.4.1.3User review and changes in the working set6.5 days14 May 202025 May 202030,29Tester 1,Tester 2
1.4.1.4Milestone 5: Basic site functions0 days25 May 202025 May 202031
1.4.2Sprint 218.05 days25 May 202018 June 2020

1.4.2.1E-commerce site – Book catalogue and product details2.3 days25 May 202027 May 202032Scrum Master, Senior Tech Engineer
1.4.2.2Web pages design and development9.25 days27 May 202009 June 202034Web Developer 2,UI/UX Designer 2,UI/UX Designer 1,Web Developer 1
1.4.2.3User review and changes in the working set6.5 days09 June 202018 June 202035,34Tester 1,Tester 2
1.4.2.4Milestone 6: Site functionalities0 days18 June 202018 June 202036
1.4.3Sprint 318.05 days18 June 202014 July 2020

1.4.3.1E-commerce site – Social media integration, feedback, payment gateway2.3 days18 June 202022 June 202036Scrum Master, Senior Tech Engineer
1.4.3.2Web pages design and development9.25 days22 June 202003 July 202039UI/UX Designer 2,UI/UX Designer 1,Web Developer 2,Web Developer 1
1.4.3.3User review and changes in the working set6.5 days03 July 202014 July 202040,39Tester 1,Tester 2
1.4.3.4Milestone 7: Site functions0 days14 July 202014 July 202041
1.4.4Sprint 418.05 days14 July 202007 August 2020

1.4.4.1E-commerce site – Security interface2.3 days14 July 202016 July 202041Senior Tech Engineer, Scrum Master
1.4.4.2Interface integration9.25 days16 July 202029 July 202044UI/UX Designer 2,Web Developer 1,UI/UX Designer 1,Web Developer 2
1.4.4.3User review and changes in the working set6.5 days29 July 202007 August 202045,44Tester 2,Tester 1
1.4.4.4Milestone 8: Security Interface0 days07 August 202007 August 202046
1.4.5Sprint 518.05 days07 August 202002 September 2020

1.4.5.1E-commerce site – User guides, Contact Us, About Us2.3 days07 August 202011 August 202046Senior Tech Engineer, Scrum Master
1.4.5.2Web pages design and development9.25 days11 August 202024 August 202049UI/UX Designer 1,UI/UX Designer 2,Web Developer 2,Web Developer 1
1.4.5.3User review and changes in the working set6.5 days24 August 202002 September 202050,49Tester 1,Tester 2
1.4.5.4Milestone 9: Final set of functionalities0 days02 September 202002 September 202051
1.5Deployment & Closure12.75 days02 September 202018 September 2020

1.5.1Final e-commerce site reviews and changes7.5 days02 September 202011 September 202052Web Developer 1,Web Developer 2,Scrum Master, Senior Tech Engineer
1.5.2Evaluation and reflection5.65 days02 September 202009 September 202052Project Admin
1.5.3Closure documentation7.1 days09 September 202018 September 202055Project Admin
1.5.4Milestone 10: Closure Report0 days18 September 202018 September 202056

Control and Reporting

The project will involve the control as per the governance structure that is included above. The members in the project governance board will obtain the reports from the project team members on a weekly basis and will also conduct the reviews to ensure that the project is on track.

The Project Admin will obtain daily status from the Scrum Master who will obtain the project progress details from the rest of the team. The Project Admin will compile the details and will share the weekly report to the Project Governance Board (Radcliffe, 2019).

Risk/ Constraints Management

The main constraints are:

  1. The project will not have more than 5% tolerance for the schedule and budget.
  2. The project will require 100% compliance to the legal, regulatory, and security standards.

The key issues in the project are:

  • Schedule and budget overrun
  • Information security issues
  • Legal/ethical/regulatory non-compliance
  • Communication gaps
  • Technical glitches

The following risk register is developed to assess and treat the risks identified.

RiskProbability (Scale of 1 to 5 5 is highest)Impact (Scale of 1 to 5 5 is highest)Score (Probability x Impact)Treatment
Schedule and budget overrun2510Avoidance
Information security issues3515Mitigation and Avoidance
Legal/ethical/regulatory non-compliance144Avoidance
Communication gaps3412Avoidance
Technical glitches339Transfer

Delivery Strategy

Approach/ Methodology

The e-commerce site for book selling will be developed as per the principles of agile SCRUM methodology. The development project will be conducted in sprints and there will be a total of 5 sprints of 18 days each. These sprints will involve a sub-set of the overall e-commerce site requirements and the design, development, and testing processes will be covered in the sprints (Dixit & Bhushan, 2019).

The management of the entire project will be done as per the guidelines mentioned in the PMBoK methodology.

Standards and Procedures

The project will follow the ethical standards and protocols in which the principles of honesty, professionalism, and integrity will be placed at the top priority.

The project will also involve the legal and regulatory compliance and the Information Privacy standards will always be adhered with (Kautz, Johanson, & Uldahl, 2017).

The communication standards will also be followed in the project and these will include the communication channels as instant messengers, emails, and reports.

References

Boateng, R. (2015). Resources, Electronic-Commerce Capabilities and Electronic-Commerce Benefits: Conceptualizing the Links. Information Technology for Development, 22(2), 242–264. https://doi.org/10.1080/02681102.2014.939606

Bott, M., & Mesmer, B. (2019). An Analysis of Theories Supporting Agile Scrum and the Use of Scrum in Systems Engineering. Engineering Management Journal, 1–10. https://doi.org/10.1080/10429247.2019.1659701

Brown, N. (2017). Updating Assessment Styles: Website Development Rather Than Report Writing for Project Based Learning Courses. 2017 Fall AEE Journal, 6(2). https://doi.org/10.18260/3-1-370.620-31328

Dixit, R., & Bhushan, B. (2019). Scrum: An Agile Software Development Process and Metrics. Journal on Today’s Ideas – Tomorrow’s Technologies, 7(1). https://doi.org/10.15415/jotitt.2019.71005

Kalyani, D., & Mehta, D. (2019). Study of Agile Scrum and Alikeness of Scrum Tools. International Journal of Computer Applications, 178(43), 21–28. https://doi.org/10.5120/ijca2019919318

Kautz, K., Johanson, T. H., & Uldahl, A. (2017). The Perceived Impact of the Agile Development and Project Management Method Scrum on Information Systems and Software Development Productivity. Australasian Journal of Information Systems, 18(3). https://doi.org/10.3127/ajis.v18i3.1095

Khalid, A., Butt, S. A., Jamal, T., & Gochhait, S. (2020). Agile Scrum Issues at Large-Scale Distributed Projects. International Journal of Software Innovation, 8(2), 85–94. https://doi.org/10.4018/ijsi.2020040106

Madison, J. (2015). Agile Architecture Interactions (was: Agile Architecture Insertion Points). IEEE Software, 1–1. https://doi.org/10.1109/ms.2010.27

Radcliffe, D. (2019). The Publisher’s Guide to eCommerce. SSRN Electronic Journal. https://doi.org/10.2139/ssrn.3502502

Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices in software development. Indian Journal of Science and Technology, 8(35). https://doi.org/10.17485/ijst/2015/v8i35/79037

The post E-commerce site for book selling Project Plan appeared first on My Assignment Online.

Plagiarism Free Assignment Help

Expert Help With This Assignment — On Your Terms

✓ Native UK, USA & Australia writers ✓ Deadline from 3 hours ✓ 100% Plagiarism-Free — Turnitin included ✓ Unlimited free revisions ✓ Free to submit — compare quotes

Related Posts

Scroll to Top