You are on page 1of 17

SOFTWARE DEVELOPMENT PLAN

FOR THE

GreatVines

Contract Nr. 2445122

Project title # MD-GR-112021

Cazacliu Cristian,
Roșca Doinița,
Florea Cristina,
Kalinovski Bogdan
Introduction

GreatVines is an all-in-one Sales Execution Platform for beverage suppliers, distributors, and
promotional agencies. Powered by Salesforce, our suite of mobile tools help you manage 3-
tier account relationships, plan appropriate sales activities, create smarter goals for growth,
and monitor trade spend and marketing programs. GreatVines offers the flexibility to adapt
your sales strategy for rapidly changing market conditions, and supplies analytics to precisely
measure the results you need to quickly collaborate with your channel partners.

Together, GreatVines solutions combine powerful technology and potent methodology to


deliver results in each of the following solution modules, which can be used as a full suite or
independently as needed.
Content
1 Document attributes.............................................................................................................4
1.1. General.........................................................................................................................4
1.2. Revision history............................................................................................................5
1.3. Terms and abbreviations..............................................................................................5
1.4. Scope............................................................................................................................5
2 Description of the functional...............................................................................................5
2.1. Deployment options.........................................................................................................5
2.2. Individual user account information................................................................................6
2.3. Data retention information...............................................................................................6
3 Project Management Plan....................................................................................................7
3.1. Project management structure..........................................................................................7
3.2. Project members contact information..............................................................................8
3.3. Communications Management.........................................................................................8
3.3.1. Meetings................................................................................................................8
3.3.2. Reporting...............................................................................................................9
3.3.3. Communication channels......................................................................................9
4. Quality Assurance................................................................................................................9
5. Risk Management..............................................................................................................10
5.1. Risk Management process..............................................................................................10
5.1.1. Risk identification and qualification...................................................................10
5.1.2. Risk evaluation....................................................................................................10
5.1.3. Risks quantitative analysis..................................................................................10
5.1.4. Risk response planning.......................................................................................10
5.2. Risk Monitoring, Controlling, and Reporting............................................................11
6. Application Software Design, Development and Implementation Plan............................11
7. Training Plan.....................................................................................................................12
7.1. Strategy and Approach...............................................................................................12
8. Coordination With Associate Developers.........................................................................12
8.1. Involvement in the Project Performance....................................................................13
8.2. System documentation...............................................................................................13
9. Warranty Service Plan.......................................................................................................13
9.1. Incident resolution process.........................................................................................14
9.2. Change request inclusion...........................................................................................15
9.3. Quality assurance and control....................................................................................16
1 Document attributes
1.1. General

Project title Informational platform “GreatVines”


Project ID MD-GR-112021
Document title SOFTWARE DEVELOPMENT PLAN
Author Andavi Solution
Audience Alcohol Distributors

1.2. Revision history


Version Comments Reference Date Author
1.0 Initial version of the Contract No. 2445122 20.08.2010 Andavi
document Solutions

1.3. Terms and abbreviations


Term Description
Software a document what defines the management plan of a project and is
development plan used for the successful management of a project

PMP Project Management Plan


Supplier Andavi Solutions

1.4. Scope
This document describes the approach and various processed to be considered for the Project.

The main process to be considered described into the sections :

- Project Management Plan


- Schedule Baseline and Work Br

The main processes to be considered described into the sections :

- Project Management Plan


- Quality Assurance
- Risk Management
- Application Software Design, Development and Implementation Plan
- Training plan
- Coordination and Turnover Plan
- Warranty Service Plan
2 Description of the functional
2.1. Deployment options

For any mobile , desktop or web application there are three relevant and actual deployment
option that affect the process for requesting information :

1. Servers hosted directly by company – GreatVines – and managed directly by


company.
2. Servers hosted by company but managed and controlled by a customers
3. Private servers , which is the most common one .

Private Any private servers used by Andavi Solution may be operated by arbitrary
servers business ,groups or individuals with no direct link to the main company.

- Andavi Solution do not have direct access to these servers


- Andavi Solution cannot control or regulate how servers works and
how are they operated
- Andavi Solution cannot access or regulate information flow on
these servers

The customers registration mandatory requires an email address, a last and


first name, a phone number.
Login form for this platform can be found here :
https://greatvines.cloudforce.com/

2.2. Individual user account information

GreatVines is an online platform and the interaction between customers and the platform happens
based on an account. Most of their customers are other companies, and GreatVines provide them a list
of services.

To create a customer account on this platform is requested to introduce your first name, last name, a
working email, a phone number and company name

To identify the proper user account, the specific server therefore must be named as well
(generally in form of the URL).
2.3. Data retention information

GreatVines is a Nielsen Connected Partner. As part of the Connected Partner program, the
TDLinx account universe can be embedded into the GreatVines platform and leveraged with
great results by users of the GreatVines tool. TDLinx provides suppliers, wholesalers and
marketers with universal coverage and unique codes for every store in retail trade channels
and for every outlet in on-premise trade.

For alcohol beverage companies, the TDLinx data provides insight into over 770,000
stores/outlets and more than 9,800 accounts. It is updated daily and delivered automatically to
GreatVines at regular intervals.

3 Project Management Plan


This section describes project management procedures, defines main roles, responsibilities,
communication channels.

3.1. Project management structure


Project roles and responsibilities are presented below:

Role Authority
Project Manager  Coordinate activity of the team
 Approve every modification in project and documents
 Ensure free communication between each member of team
 Assigned experts to be involved directly in Project phases.

Developing team  Define and manage System architecture


lead / system  Define and evaluate risks associate to Project and System.
architect  Identity user and system requirements
 Define 3rd parties integration solutions and constrains
 Elaboration of Solution High level and Low-level design, as well as other
relevant technical documentation and ensure that the documents are up to
date.
 Prioritize, estimate and assign tasks
 Review System code.
Business analyst  Business analysis and requirements description and definition
 Management of the System requirements
 Management of the Project stakeholders
 Documents version control
 Define acceptance procedures
 Coordinate trainings and QA process
Trainer & Quality  Reviewing customer requirements and making sure they are met
manager  Elaborate Testing and Acceptance Plan, including testing and acceptance
checklist,
 Working with the Purchaser team for acceptance activities appropriate
performing
 Set up and maintaining controls and documentation procedures
 Trainings and development of training materials
Senior developer  Create wireframes to decide on layout
 Write and review code for Systems
 Run functionality testing and debug code
 Elaborate technical documentation
 Coordinate and update documentation

3.2. Project members contact information


First and Last Role Email Address
Name
Cazacliu Cristian Project Manager cristian.cazacliu45@gmail.com

Florea Cristina System architect florea.cristi@gmail.com

Rosca Doinita Business analyst doinita.rosca22@gmail.com


Kalinovski Bogdan Senior developer bogdan.kalinovski@gmail.com

3.3. Communications Management


3.3.1. Meetings

Project Progress Meeting

Initiator Project Manager


Frequency Twice per month (Tuesday at 10:30 Chisinau time)
Duration Up to 2 hours
Participants Project Manager, system architect, Business analyst, Senior developer
Predecessors Progress reports, previous minutes
Delivery Minutes of the meeting (in English)

Status update meetings

Initiator Business analyst


Duration Up to 15 minutes
Frequency Every Tuesday at 10:30 (Chisinau time)
Participants Project Manager, system architect, Business analyst, Senior developer
Predecessors Progress reports
Delivery Logs updated
Technical Meeting

Initiator Business analyst


Frequency According to Projects needs
Duration Up to 3 hours
Participants Project Manager, system architect, Business analyst, Senior developer
Predecessors Project Plan
Delivery Minutes of the meeting (in English)

Budget and resource meeting

Initiator Project Manager


Frequency Once
Duration Up to 3 hours
Participants Everyone implicated in project
Predecessors Project Plan
Delivery Minutes of the meeting (in English)

3.3.2. Reporting

Progress report will be communicated by Business analyst through email once in 2 working day.

The report will be prepared as per template provided.

Reports must be elaborated in English language.

3.3.3. Communication channels


E-mails to Project manager should be sent with following rules:

To: Project manger


CC:
Subject MD-GR-112021_ letter subject
:

Organizational issues be sent with following rules:

To: Business analyst


CC: Project Manager
Subject: MD-GR-112021_ letter subject
Technical issues be sent with following rules:

To: Business analyst and Development Team Lead


CC: Project Manager
Subject: MD-GR-112021_ letter subject

Communication language for email is English or Romanian.

4. Quality Assurance

Quality assurance provided via mandatory peer review of project management procedures and
reports, combined with configuration management processes.

The Project Manager and Business Analyst, who controls documents lifecycle and QA
procedures fulfillment, supports configuration items list.

5. Risk Management

5.1. Risk Management process


Risk management performed in accordance with PMI standard with following lifecycle:

5.1.1. Risk identification and qualification

Each member of team can identify a risk. He or she will report this risk though email and
should communicate it to the Project Manager.

Project Manager with the risk initiator and other team members qualify the risk, define parts
of project it can fluent and people who may be involved. Risk owner should be defined at this
step. After the qualification, the risk should be included into the risk log.
5.1.2. Risk evaluation
The Project Manager with experts define project parameters risk can fluent to (scope,
duration, and budget).

Following risk attributes should be defined:

 Risk Impact. The potential impact of the risk if it did become a project issue. Valid
options include the following: High, Medium, Low.  These are defined as follows:
 High: Risk that has the potential to greatly impact project cost, project schedule
or performance.
 Medium: Risk that has the potential to slightly impact project cost, project
schedule or performance.
 Low: Risk that has relatively little impact on cost, schedule or performance.

 Probability of occurrence:
 High: more than 80%.
 Medium: Between 20% and 80%.
 Low: Less than 20%.

5.1.3. Risks quantitative analysis.


The Business analyst with experts define metrics for the risk influence (days of delay, amount
of money, and amount of recourses). This information may be added and specified later, than
more information will be collected and analyzed. Business analyst will communicate with
Project Manager and other team members.

5.1.4. Risk response planning


Each major risk (high and medium impact) will be assigned to a project team member for
monitoring purposes to ensure that the risk will not “fall through the cracks”.

For each major risk, one of the following approaches will be selected to address it:

 Avoid – eliminate the threat by eliminating the cause


 Mitigate – Identify ways to reduce the probability or the impact of the risk
 Accept – Nothing will be done
 Transfer – Make another party responsible for the risk
For each risk that will be mitigated, the project team will identify ways to prevent the risk
from occurring or reduce its impact or probability of occurring. This may include prototyping,
adding tasks to the project schedule, adding resources, etc.

For each major risk that is to be mitigated or that is accepted, a course of action will be
outlined for the event that the risk does materialize in order to minimize its impact.
5.2. Risk Monitoring, Controlling, and Reporting
All the Project members are responsible to track, monitor and report throughout the project
lifecycle the risks.

Project Manager is responsible to keep up-to-date Risk Log. A summary of the Risk Log must
be included into the Project Progress Report.

All project change requests will be analyzed for their possible impact to the project risks.

6. Application Software Design, Development and Implementation Plan


GreatVines and our field sales mobile app run seamlessly on all browsers with Internet access,
as well as with mobile applications for iOS, Android and Windows 10. 

GreatVines Mobile (our original mobile solution) is developed with a hybrid HTML5
framework where our field sales mobile app introduces our first pure Javascript Progressive
Web App (PWA) on the latest standards.

Both mobile solutions utilize the same credentials as our standard browser environment, are
available in offline mode, and GreatVines Mobile can also be installed by end users from the
device app stores.

The GreatVines Data Integration platform can load data from third-party data providers, such
as Nielsen and VIP, into GreatVines to provide a complete picture of customers and sales
across the 3-tier supply chain. This data includes retailers, national account chains, wholesaler
inventory and depletions, and Sales to Retailers (STR/RAD).

All core GreatVines application functionality and data management, other than reporting and
analytics, is developed on and powered by the Salesforce Lightning Platform. The GreatVines
Mobile application (version 1) was built upon the Salesforce Mobile SDK,  and has been
recognized as a leading partner app for innovation. GreatVines has been a featured partner on
the AppExchange Retail category since 2010, as well as a participant in the annual
Dreamforce conference in San Francisco
7. Training Plan
A software solution can only show all its benefits if used properly. An efficient capacity
building can avoid problems during and after the implementation process.

The Trainer responsibility is to ensure the relevant IT administrators and users of the
Beneficiary’s institution are enabled to autonomously operate and maintain the systems after
the end of the project and the final users understand how to use it properly.

7.1. Strategy and Approach


Due to the large number of users, will be created user guides.

Video tutorial and user guides will be elaborated in English.

8. Coordination With Associate Developers

One of the main Project objective is to ensure that management of the Beneficiary agencies
and their key users of the System are sufficiently experienced to be capable of assuming the
full responsibility for the System operation and other support, maintenance and enhancement
tasks, in order to guarantee the long-term sustainability of the supplied solution.

To achieve the goal introduced following assets should be provided:

 Qualified and trained personnel


 Processes and tools.

The Supplier’s Project Manager will take all the necessary measures in order to ensure that
the experience for duly operate the supplied System.

To achieve the proposed objective, the Supplier, in collaboration with the Purchaser, will
perform the following actions:

 during the implementation period:


- deliver training sessions in accordance with the Training Plan accepted,
- facilitate involvement of Beneficiary key users and management in the Project
implementation

 after the implementation of the System:


- make available to the Purchaser all necessary training materials
- make available to the Purchaser all necessary user and technical documentation.
8.1. Involvement in the Project Performance
In order to have a full and deep understanding of the System, Beneficiary is required to take
part in all Project phases, such as, but not limited to: System analysis and architecture, testing
and acceptance activities according to Project Implementation Plan.

The Purchaser’s Project Manager and EGA Representative are responsible to name the
appropriate team members to participate at:
- Technical meetings
- Project Management meetings

The Purchaser is responsible to involve the appropriate Beneficiary members in the


installation and commissioning works according to Project Implementation Plan.

The Purchaser’s Project Manager is responsible to coordinate the process with the Supplier’s
Project Manager, the communication will be realized according to Project Organization and
Management Plan.

8.2. System documentation


The delivery of documentation regarding the System will ensure that the rotation of
Beneficiary members will not affect the proper functioning of the System and ensure the long-
term workability of the System. The documentation will be delivered according to the Project
Plan, section 3Milestones and deliverable list and will cover: user guides (video-tutorials and
pdf manuals), technical administration guides (administration guides, integration guides,
system architecture).

9. Warranty Service Plan


Warranty Period commences from the date of Operational Acceptance of the System and
extends for 12 months.

When putting into the operation the System, all the related documentation will be delivered to
the Beneficiary and provided knowledge data base transfer (to see the Training Plan and
Turnover and coordination plan).

During the Warranty Period, Andavi Solution. is responsible to ensure System availability and
reduce the risk of distrusted operations due to incident occurrence. Therefore, all the incidents
may be reported by the Beneficiary’s responsible person via support channel: hot line and/or
service desk.
No later than 3 weeks before starting the Warranty period, the Supplier will configure the
Project within the Service Desk and open the account to appointed by Project Manager
responsible persons, assign a Hot line number.

9.1. Incident resolution process


The Beneficiary’s responsible person will report the incidents via Service Desk. One incident
must be associated to one ticket, if more incidents are reported in a single ticket, the Supplier
can close the ticket and request to be opened new tickets for each incident.

If during the incident analysis and solution identification, the Supplier needs more
information, the Beneficiary must provide the support operator with the request information
or ensure operator remote access to the incident location. If the Beneficiary has not provided
the information or access during 3 working days, the ticket is considered resolved and closed.

The Supplier is responsible for incident analysis, solution identification and categorization,
with the primary goal being a quick-as-possible restoration of System being on service.

Support of the System is based on a Service Desk with two levels. Incident processing starts
at first level, 2nd level is getting involved as necessary.

First-Line Support (a support operator) opens an incident ticket and attempts to collect as
much information and diagnostics about the incident as possible, sets the incident priority
(according to policy) and even resolves the issue on the spot, if possible, using Support
Knowledge Base.

If First-Line Support is not able to resolve the incident right away, it will escalate the incident
to Second-Line Support.

When the ticket is assigned to the 2nd level support line, the support operator must provide the
following information:

- Incident description
- A possible cause of the incident
- Expected results and Actual results
- Any print screens and System logs if applicable

Second-Line Support composed of a developer that has participated in developing the of


System. Their purpose is incident diagnosis and resolution. Second-Line Support will pay a
visit to Site if required. The support developer will provide:

- Description of the incident cause


- Description of the solution
- Changes done in order to deliver the solution
- Systems module that was updated
- System documentation update, if necessary

The Beneficiary must confirm the solution and close the ticket in 3 working days, after
solution delivery. If no response if received form the Beneficiary, the ticket will be considered
resolved and will be automatically closed. If the Beneficiary will not confirm the solution of a
closed ticket, a new ticket on the problem will be submitted.

Level Specialist No of Responsibility Functions


technicians
I Supplier 2 Supplier - Collect information and
Support diagnostics about the incident
Operator - Set incident priority
- Attempt to resolve the issue using
Support Knowledge Base
- Escalate the incident to next level
- Assign incident to a 2nd level
II Supplier 2 - Diagnose and resolve incident.
Developer - Pays a visit to Site (if required)
- Expert assistant/support

In order to ensure System maintenance efficiency, it is recommended to assign a dedicated


person from the Beneficiary side, that will be trained to resolve the most comincidents, such
as errors due to bad connections and report the incident via Service Desk.

Support service location and availability:

- Service center address: Chisinau, str. Grigore Vieru 49 .


- Service desk is available 24x7 (help.desk@greatvines.com)
- Hot line is available 8x5 (9:00-20:00, Chisinau time)

9.2. Change request inclusion

During the warranty period, the Beneficiary may address change request to the System. The
change request must be addressed via Project official communication channel.

Change request will be processed according to change requests management plan.

The changes in business functionalities will be provided upon request, the effort of
implementing change request will not exceed 50-man days per annum.
9.3. Quality assurance and control
Periodically the Parties arrange a meeting where they analyze support operations and issues.
As a result of this analysis following tasks will be initiated:

 replenish the Knowledge Base


 support engineer’s trainings
 change requests initiation
 resources deplaning
 SLA negotiation.

The developed Software will be transferred in the Purchaser’s property; thus the source codes
will be submitted during the implementation of the Project.

For the developed Software the Warranty covers:


 Bugs
 Restore after an incident
 Consulting services (functionality, configuration and restore)
 Any adjustments to the solution(s) made by the Purchaser on his own, must be
realized only with the prior approval of the Supplier. If after the
implementation of coordinated adjustments, the functioning of the solution is
affected, the Purchaser shall return to the latest approved configuration.

The warranty will cease if:

 The Purchaser makes any adjustments/modification to the developed software


without the Supplier’s prior consent.

You might also like