E-commerce site for book selling Project PlanSocial Media Analytics for MarketingNo A**Hole Rule Part One Quiz #2 InstructionsMaintain and improve the performanceMITS5502DevelopingMaster of Business Administration (MBA)E-R DiagramHLSC122 Evidence for PracticeBusiness Research Methods

FIND A SOLUTION AT Academic Writers Bay

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 -41724
Date:
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:
The e-commerce site for book selling will become the primary channel for the business to sell the books.
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
WBS
Task Name
Duration
Start
Finish
Predecessors
Resource Names
1
E-commerce site for book selling
132 days
19 March 2020
18 September 2020

READ ALSO...   examples of stakeholders generically

1.1
Project Initiation
13.1 days
19 March 2020
07 April 2020

1.1.1
Business context and project goals determination
4.1 days
19 March 2020
25 March 2020

Project Admin
1.1.2
Project complexity and benefits
2.6 days
25 March 2020
27 March 2020
3
Scrum Master
1.1.3
Objectives
1.9 days
27 March 2020
31 March 2020
4
Project Admin
1.1.4
Project governance structure
0.7 days
25 March 2020
25 March 2020
3
Project Admin
1.1.5
Business assessment and high-level scope
2.2 days
31 March 2020
02 April 2020
5
Scrum Master
1.1.6
Key project risks and feasibility determination
2.3 days
02 April 2020
07 April 2020
7
Senior Tech Engineer
1.1.7
Milestone 1: Project Proposal
0 days
07 April 2020
07 April 2020
8

1.2
Planning
12.8 days
02 April 2020
21 April 2020

1.2.1
Detailed project scope
3.4 days
02 April 2020
08 April 2020
7
Project Admin
1.2.2
Project development and management methodologies
2.6 days
02 April 2020
07 April 2020
7
Scrum Master
1.2.3
Project Estimates
6.4 days
08 April 2020
16 April 2020

1.2.3.1
Schedule- WBS, Gantt
3.6 days
08 April 2020
13 April 2020
11
Project Admin
1.2.3.2
Budget and resources
2.8 days
13 April 2020
16 April 2020
14
Project Admin
1.2.4
Milestone 2: Project schedule, effort, and budget
0 days
16 April 2020
16 April 2020
15

1.2.5
Project elements
3 days
16 April 2020
21 April 2020
16

1.2.5.1
Risks and constraints
1.5 days
16 April 2020
20 April 2020
15
Senior Tech Engineer
1.2.5.2
Communication and quality
1.5 days
16 April 2020
20 April 2020
15
Project Admin
1.2.5.3
Resources and stakeholders
1.5 days
20 April 2020
21 April 2020
18,19
Project Admin
1.2.6
Milestone 3: Project Plan
0 days
21 April 2020
21 April 2020
20

READ ALSO...   Products/entrepreneurs effectively marketed in the U.S. - No Plagiarism

1.3
Set-up for execution
5.4 days
21 April 2020
28 April 2020

1.3.1
Eclipse platform and design tools
3.2 days
21 April 2020
24 April 2020
21
Senior Tech Engineer
1.3.2
Test tools – Selenium, Bugzilla
2.5 days
21 April 2020
24 April 2020
21
Tester 1
1.3.3
Installation of the tools
2.2 days
24 April 2020
28 April 2020
23,24
Senior Tech Engineer
1.3.4
Milestone 4: Set-up for project execution
0 days
28 April 2020
28 April 2020
25

1.4
Agile SCRUM – Site Development
90.25 days
29 April 2020
02 September 2020

1.4.1
Sprint 1
18.05 days
29 April 2020
25 May 2020

1.4.1.1
E-commerce site – login, layout, registration, and logout
2.3 days
29 April 2020
01 May 2020
26
Scrum Master, Senior Tech Engineer
1.4.1.2
Web pages design and development
9.25 days
01 May 2020
14 May 2020
29
UI/UX Designer 2,UI/UX Designer 1,Web Developer 2,Web Developer 1
1.4.1.3
User review and changes in the working set
6.5 days
14 May 2020
25 May 2020
30,29
Tester 1,Tester 2
1.4.1.4
Milestone 5: Basic site functions
0 days
25 May 2020
25 May 2020
31

1.4.2
Sprint 2
18.05 days
25 May 2020
18 June 2020

1.4.2.1
E-commerce site – Book catalogue and product details
2.3 days
25 May 2020
27 May 2020
32
Scrum Master, Senior Tech Engineer
1.4.2.2
Web pages design and development
9.25 days
27 May 2020
09 June 2020
34
Web Developer 2,UI/UX Designer 2,UI/UX Designer 1,Web Developer 1
1.4.2.3
User review and changes in the working set
6.5 days
09 June 2020
18 June 2020
35,34
Tester 1,Tester 2
1.4.2.4
Milestone 6: Site functionalities
0 days
18 June 2020
18 June 2020
36

1.4.3
Sprint 3
18.05 days
18 June 2020
14 July 2020

1.4.3.1
E-commerce site – Social media integration, feedback, payment gateway
2.3 days
18 June 2020
22 June 2020
36
Scrum Master, Senior Tech Engineer
1.4.3.2
Web pages design and development
9.25 days
22 June 2020
03 July 2020
39
UI/UX Designer 2,UI/UX Designer 1,Web Developer 2,Web Developer 1
1.4.3.3
User review and changes in the working set
6.5 days
03 July 2020
14 July 2020
40,39
Tester 1,Tester 2
1.4.3.4
Milestone 7: Site functions
0 days
14 July 2020
14 July 2020
41

1.4.4
Sprint 4
18.05 days
14 July 2020
07 August 2020

1.4.4.1
E-commerce site – Security interface
2.3 days
14 July 2020
16 July 2020
41
Senior Tech Engineer, Scrum Master
1.4.4.2
Interface integration
9.25 days
16 July 2020
29 July 2020
44
UI/UX Designer 2,Web Developer 1,UI/UX Designer 1,Web Developer 2
1.4.4.3
User review and changes in the working set
6.5 days
29 July 2020
07 August 2020
45,44
Tester 2,Tester 1
1.4.4.4
Milestone 8: Security Interface
0 days
07 August 2020
07 August 2020
46

1.4.5
Sprint 5
18.05 days
07 August 2020
02 September 2020

1.4.5.1
E-commerce site – User guides, Contact Us, About Us
2.3 days
07 August 2020
11 August 2020
46
Senior Tech Engineer, Scrum Master
1.4.5.2
Web pages design and development
9.25 days
11 August 2020
24 August 2020
49
UI/UX Designer 1,UI/UX Designer 2,Web Developer 2,Web Developer 1
1.4.5.3
User review and changes in the working set
6.5 days
24 August 2020
02 September 2020
50,49
Tester 1,Tester 2
1.4.5.4
Milestone 9: Final set of functionalities
0 days
02 September 2020
02 September 2020
51

1.5
Deployment & Closure
12.75 days
02 September 2020
18 September 2020

1.5.1
Final e-commerce site reviews and changes
7.5 days
02 September 2020
11 September 2020
52
Web Developer 1,Web Developer 2,Scrum Master, Senior Tech Engineer
1.5.2
Evaluation and reflection
5.65 days
02 September 2020
09 September 2020
52
Project Admin
1.5.3
Closure documentation
7.1 days
09 September 2020
18 September 2020
55
Project Admin
1.5.4
Milestone 10: Closure Report
0 days
18 September 2020
18 September 2020
56

READ ALSO...   Personal teaching philosophy

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:
The project will not have more than 5% tolerance for the schedule and budget.
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.
Risk
Probability (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 overrun
2
5
10
Avoidance
Information security issues
3
5
15
Mitigation and Avoidance
Legal/ethical/regulatory non-compliance
1
4
4
Avoidance
Communication gaps
3
4
12
Avoidance
Technical glitches
3
3
9
Transfer
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

Order from Academic Writers Bay
Best Custom Essay Writing Services

QUALITY: 100% ORIGINAL PAPERNO PLAGIARISM – CUSTOM PAPER