Communication plan
Table of Contents
Introduction
The approach is to upgrade the existing business (a shop) started by my grandfather using the management approaches. The aim will be to use Scrum methodology for developing a website for the shop that will allow the customers to interact and make the purchase from the shop online. This proposal will cover the details of the project in a summary and same will be used for the future project.
Needs/Problems
It is an old shop and thus, brand value for my shop in locals is high however, we are unable to interact with the customers outside locals. Thus, the approach is being applied to develop a website that will allow the customers to access the same services from anywhere. This will be alternatively improving the sales and enhance the business.
Goals/Objectives
To constraints of the project are: timeline will be two months, cost for developing the website will be $30,000, and the quality will be kept high through modifying the website will all the functions of an ecommerce website.
Scope
The scope is to introduce all the 15000 items on the showcase of my website and allow the customers to make the purchase and get the product at their home using website.
Backlog
Functional Requirements:
Non-Functional Requirements
Maintainability: Testability, stability, and changeability.
Function ability: Security, compliance, SEO-Friendly, and User friendly.
Schedule
Cost
| Task Name | Cost ($) |
|---|---|
| Marketing | 1,500 |
| Planning | 1,750 |
| Analyse requirements | 1,000 |
| Design Website | 3,500 |
| Build Website | 6,000 |
| Test website | 1,000 |
| Make the necessary changes required | 750 |
| Launch website | 3,000 |
| Maintenance and Support | 1,500 |
| Total | 20,000 |
Risk Management
Communication Plan
| Type of communication | Owner | Frequency | Topic of concern |
|---|---|---|---|
| Project Team meeting | Manager | Every Week | Project progress, milestones, issue and risks log, leaves, and other business |
| Scrum meeting | Manager | Daily | Past and future plans discussion and the obstacles on the way |
| Project Status | Manager | Every Week | Discussion over the key project details including budget, schedule, issues, risks, and benefits |
| Project progress | Manager | Every week | One to one meeting regarding project flow |
| Project control meeting | Manager and Sponsor | Every Month | Project key constraints discussion |
| Quality Assurance | Manager | Everyday | Baseline and ongoing delivery discussions |
Bibliography
Papadopoulos, G. (2015). Moving from traditional to agile software development methodologies also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, 455-463.
Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.