SCOPE OF WORK: O-Learn

Content

1- Purpose
The purpose of O-learn is to provide an online platform and application in order to improve
online learning about ESG (Environmental Social Governance). This must include
purpose-built executive education courses targeting individuals – working students,
executives, and entrepreneurs – and small-sized organizations such as consulting start-ups
with limited reach into the marketplace.

Since covid-19 the online business has really improved and developed by helping
consumers find alternatives to what they used to do before the pandemic. We want to
provide that service in order to help people get access to education wherever they may be
and whatever tight schedule they can have.

2- General Description dev +obj for future (Felix)

O-learn is making the link between teachers and students.
- Virtual classes (any languages)
- Forum area
- Resources

→ developing

3- Requirement (Romane) ok! +dev

Our website will be compatible with Mac and Windows and our application will be available
on IOS and Android. Indeed, we want our platform to reach people from around the world.
The main language will be english, but users will be able to choose the language they prefer.

How much capacity we need

nb of people we’ll try to reach →
Language
Legal requirements (copyrights, laws we have to follow…)
countries (every country in the world ?)
general structure of the platform (quizz
Language: English
Prices

Element that we received from our clients

4- Resources Required (Responsibility matrix)

O-learn will provide six professional staff to create and optimize the platform.
1. Product owner: Is the person on the product development team who is responsible for
communicating with stakeholders including customers and the development team to make
sure the goals are clear and the vision is aligned with the business objective.

2. Project manager: In charge of the planning, scheduling, budgeting, execution and delivery
of the project with several responsibilities such as

Programmers: (3 people)
- Responsible for designing the application. (Two weeks)
- Responsible for designing and continuously optimizing the product interface, ensuring the
aesthetics of the interface, while following the convenience of customers. (1 week)
- Responsible for dealing with technical problems that occur during the use of customers,
such as the freeze phenomenon when the number of visits is too large. (resolved within 24
hours of the issue)

2. Market researcher: (1 person)

- Responsible for understanding the current market demand, analyzing the drawbacks of the
existing online teaching platforms, and determining our product positioning and market
scope. (1 week)
- Responsible for collecting and analyzing consumer feedback after our application is
launched. (Continued since the launch of the product, once a week)

3. Product Tester: (1 person)

- Responsible for product testing before the launch of our application and every subsequent
new version, such as compatibility issues on different browsers or operating systems. (3
days)

4. Promotion staff: (1 person)

- Responsible for the promotion of the application and the training of relevant personnel,
such as assisting teachers to use the application to ensure the fluency of the teaching.
(proceed)
- Responsible for necessary cooperation negotiations. (proceed)

5- Prerequisites Technical requirements (Gabriela)

Technical requirements

The o-learn platform is cataloged as a Learning Destination Site where different users and
content providers can list their courses and training material. The users can select the
required course and get access to it. The o-learn website hosts the courses and manages
the payment system.

For the design and development stage, we’ll focus on 4 stages: prototyping, UI Design,
Development, Testing & Debugging.
Prototyping (UX design): To understand how the customer journey will be, we’ll create the
user workflow, along with a digital wireframe. This stage will consider the following user
interactions as minimum.

· Registration and profile management

· Search option

· Dashboard design

· Course page design

· Payment gateway integration

· Course creation and editing page

· Reminders and notifications

· Admin panel

UI design: Considered as the interface design stage, we’ll develop a nice design to engage
users and make their interaction smoother, by creating a logo, a UI kit (colors, typos,
elements, and interactions) and in this stage we’ll implement UI in the UX prototypes.

Development: Stage where the prototype becomes the real website, the development team
starts to implement the business logic and key features into a workable product. The
following stages are considered:

1. Deploy server to AWS – basically write the code and verify functionality.

2. Develop a scalable server architecture – adds a level of flexibility in case of growth.

3. Research APIs documentation to include third-side services – Add useful features as

video visualization, quiz maker, etc.

4. Integrate payment gateways.

6- Integrate social media (forum).

Testing & Debugging: Considered as the quality assurance stage where each screen is
reviewed to make sure that everything works as it is supposed to.

7- Project Entry (Cristina)

https://www.whatissixsigma.net/entry-and-exit-criteria/
Entry criteria are the criteria or requirements, which must be met before initiating a specific
task or a process. It is a predefined set of conditions that must exist before a unit of project
work can commence. It is used as a process control mechanism, to determine the
cost-effectiveness of initiating a process or sub process. Entry Criteria should be used as a
preventive tool in the process. It should analyze and prevent the entry of any input that is
trivia and adds no value to the process, such as poor quality specifications tools or
inadequate levels of prior work.
This is entry-testing phase of the program.

SWOT matrix
Survey ? So that we can test the idea…

8- Project Deliverables (Maria)

1. Website development (learning platform)

2. Application linked to the website
3. Training Curriculum:
- Define Objectives
- Assess training needs
- finalize the training objectives and budget
- select trainers
4. (Certificates of completion)
5. (Support Service for Students (forum…) → as a module)
6. Subscription options/ courses price
7. Payment Methods → as a developer / give options

· Timeline

· Milestones

· Project description

· Purpose / objectives

· KPIs

· Risks / issues

· Assumptions

· Acceptance criteria

9- Project Exit (Felix)

There are three main exit strategies: Phasing down, phasing out and Phasing over
As we will only do the planning, it makes most sense to transfer the results over to another
institution. Thus, we choose a phasing over strategy. The project exit has to be kept in mind
during all the operations.
Necessary for planning the exit are the following points:

· Intervention/actions/activities

· Actors (who will implement/manage what)? Everyone what he did?

· Time lines (when will what be done) when are we finished?

· Resources needed (financial, human, material) 10% of the time for everyone?

· Source of resources (who will provide human and financial resources)

· Monitoring and Evaluation (what and when)? Manager?

· Who will monitor the activities - independent monitor manager?

· Other challenges and how they can be addressed ; Any delays, cost overruns, sick days
of important employees; Change of requirements; technical issues;

10- Roles and responsibilities

11- Generic Time Plan
12- Budget

Smartsheet → tutorial

Project Charter:
- Stakeholders/contractors/sponsors
- General Description (watch above)
- Objectives and Purpose (easy access to education + raise awareness on
environment and ESG)
- Risk/issues (R1 : Not having all fields covered by professors / bad reviews + R2 : Not
having enough subscribers (interested people) + R3 : time delays)
 - Assumptions (restrictions, constraints)
- KPIs
- Acceptance Criteria ( 1 : the platform is conceived + 2 : More than ?% have
subscribed to O-Learn)
- Deliverables (
- Timelines
- Milestones (KM 1 : for updates beginning + KM 2 : reports on solutions middle + KM
3 : at the end to close the project)
[[[ Review and acceptance of developed website ]]]
[[[ Review and acceptance of developed application ]]]
[[[ Review and acceptance of curriculum...yet possibly others! ]]]

- Budget
- Resources (team member)
- Responsibility Matrix

· Stake holders (venders)

· Budget

· Resources (Responsibility matrix)

· Deliverables: MARIA

Project Scope (Session 2 in the course)

Project Scope Definition session 3

1. Justification:
The purpose of O-learn is to provide an online platform and application in order to improve
online learning about ESG (Environmental Social Governance). This must include
purpose-built executive education courses targeting individuals – working students,
executives, and entrepreneurs – and small-sized organizations such as consulting start-ups
with limited reach into the marketplace.

Since covid-19 the online business has really improved and developed by helping
consumers find alternatives to what they used to do before the pandemic. We want to
provide that service in order to help people get access to education wherever they may be
and whatever tight schedule they can have. Help people fulfill their career wishes.
2. Objective: (There is a guideline in the sample but we can change it, include KPI)
→Cristina

KPIs: https://www.qlik.com/us/kpi/kpi-examples

- Quality: “learn about environment issues” (teachers should have a average

experience of 5 years teaching in this field or working in the industry)
- Affordable education → 1% of the salary of an average employee
- Great availability of teacher: First Response Time (FRT)
- Positive Customer Reviews
- Average Time Between Failures
- Customer retention

3. Project Deliverables
1. Website development (learning platform) (add a module to support students + add
options for payments methods)
2. Application linked to the website
3. Training Curriculum:
- Define Objectives
- Assess training needs
- Finalize the training objectives and budget
- Organize training selection

Acceptance Criteria
There are three main exit strategies: Phasing down, phasing out and Phasing over

As we will only do the planning, it makes more sense to transfer the results over to another
institution. Thus, we choose a phasing over strategy. The project exit has to be kept in mind
during all the operations.
Necessary for planning the exit are the following points:

· Intervention/actions/activities:

- Assemble all the accepted deliverables;

- Conduct technical tests;
- Invoice the deliverables;
- Run a Beta Phase;
- Launch it
- Project closed

· Actors (who will implement/manage what)? Everyone what he did?

- Everyone finishes what he started

· Timelines (when will what be done) when are we finished?

- Complete the WBS

Part of WBS

· (Resources needed (financial, human, material) 10% of the time for everyone)

· Source of resources (who will provide human and financial resources) (HR)

· Monitoring and Evaluation (what and when)? Manager

· Who will monitor the activities - independent monitor manager

· Other challenges and how they can be addressed ; Any delays, cost overruns, sick days
of important employees; Change of requirements; technical issues;

5. Project description: Requirements and Assumptions

O-Learn website will be compatible with Mac and Windows and our application will be
available on IOS and Android. Indeed, we want our platform to reach people from around the
world. The main language will be English, but subtitles in other languages will be available.

O-Learn is an interactive and easy-to-use platform with the following general structure:
- Quizz
- Lectures
- Mock exams
- Forums
- Live Sessions
- Learning cloud with ressources (videos, documents, studies….)

O-Learn should have the following capacity: we try to reach 2 millions people a year, and
200 000 subscription users per month.

The price will be no more than 25€. The subscription price will not be the same for all users,
depending on different conditions (financial situation, geographical condition…)

The website is based in France and follows the French and European regulations.
Concerning:
- Data privacy policies: the GDPR (General Data Protection Regulation) stipulates
different principles, such as the “data protection since the conception” and the
“security by default”. The principle of responsibility allows companies to no longer
have to contact a supervisory authority to request authorisation to process personal
data. In return, they must be able at all times to provide proof that they are complying
with the regulations.
- Comments: the DGCCRF (Direction Générale de la Concurrence, de la
Consommation et de la Répression des Fraudes) protect a company in case of any
false or mean comments, considered as a misleading commercial practice
- Copyright: french regulations protects the intellectual property
6. Project Milestones
- By deliverables (we wait if one is related to the other):

website → app → training curriculum

- Takes place at a specific time

- Symbolized by a diamond

7. Resources Required
O-learn will provide 5 professional staff and many customers to create and optimize the
platform.

a. Product owner (1 resource):

Is the person on the product development team who is responsible for communicating with
stakeholders including customers and the development team to make sure the goals are
clear and the vision is aligned with the business objective.

b. Project manager (1 resource):

In charge of the planning, scheduling, budgeting, execution and delivery of the project with
several responsibilities such as discuss project parameters with clients, executives, software
developers, planning the project including scope, allocating resources, setting deadlines,
indicate test and maintenance, also responsible for assembling the project team, participate
in supervising each stage, ensure that the project stays on schedule and adheres to
deadlines, keep budget as close possible to the project, track milestones, deliverables and
change request and finally deliver the completed software product to client and perform
regular checks on the product performance.

c. Senior programmer (1 resource):

This person is responsible for the design, development, and implementation of software
programs and website/application that align with the business requirements. He/She leads
junior programmer in encoding, testing, and debugging an organization's software programs
and website/application.

d. Junior programmer (1 resource):

Under the leadership of the senior programmer, the junior programmer is mainly responsible
for the testing of the program and assists the senior programmer in other parts.

e. Software quality engineer (1 resource):

Its purpose is to ensure the software development team is efficiently testing for quality
throughout the product development cycle by designing test plan scenarios, document
software defects and conduct quality checks.

UX Design: To understand how the customer journey will be, we’ll use Whimsical to create
the user workflow, along with a digital wireframe in Figma. This stage will consider the
following user interactions as minimum.

· Registration and profile management

· Search option

· Dashboard design

· Course page design

· Payment gateway integration

· Course creation and editing page

· Reminders and notifications

· Admin panel

UI Design: Considered as the interface design stage, we’ll develop a nice design to engage
users and make their interaction smoother, by creating a logo, a UI kit (colors, typos,
elements, and interactions) and in this stage we’ll implement UI in the UX prototypes.

Development: Stage where the prototype becomes the real website, the development team
starts to implement the business logic and key features into a workable product. The
following stages are considered:

a. Deploy server to AWS – basically write the code and verify functionality.

b. Develop a scalable server architecture – adds a level of flexibility in case of growth.

c. Research APIs documentation to include third-side services – Add useful features as

video visualization, quiz maker, etc.

d. Integrate payment gateways.

→ Responsibility matrix
8. Cost Estimate (for our project we should do both and sound rational and do it per
deliverable not per phase)

-Consensus method (estimation of the budget bcz of similar projects)

Consensus method=> 40 000€

- ratio method (/m2 or /ft2 ): depending on the WBS

9. Risk/issues

10. Stakeholders , contractors, sponsors

Check this SESSION 4 ⇒ WBS for next meeting

SESSION 5 ⇒ RISKS
O-learn is making the link between teachers and students.
- Virtual classes (any languages)
- Forum area
- Resources
KPI
Testing the product: WBS not a resource
- Responsible for product testing before the launch of our application and every subsequent
new version, such as compatibility issues on different browsers or operating systems. (3
days)

Project Constraints Analysis

Quality constraints

The website O-Learn must meet certain quality criteria, which we have defined below.

Content ● Attractive content: verbal information must be professional and

Quality clear.
● Not design a web site too technical, to be accessible to as many
people as possible
● Being able to see how far they are in the course (if they are
advanced or if they still have a long way to go)
● Be able to evaluate themselves and compare their performance to
improve (have a little challenge with themselves)

Structure ● Ergonomic constraints: usability, ease of navigation. Site structure.

Quality (The user should be able to use the website without consulting the
help section).
● Easy access to contact and give feedback: offer multiple points of
contact - phone, email, social media and maybe an easy-to-use
contact form. Above all, ensure that this information is readily
available on an easy-to-find contact page—if not every page of your
site.
 Technical ● Website speed: The requirement is that the website loads in 3
Quality seconds. To improve the website speed O-Learn will consider
optimizing images, video, databases and code.
● Structured code and coding guidelines. This is particularly important
if more than one person is working on the project.
● Moderate link strategy: no links to external sites will be needed,
only internal links within the website.

Aesthetic ● Aesthetics: refer to the look and feel of the site (visual information).
Quality ● Typography. Clarity. Originality.
● Colors: white, black and green (to remember the ESG content)

Time constraint:

All the different steps of O-Learn launching must meet certain time constraints.These
constraints are based on the WBS.
There are 5 main steps:
- Website development
- Training Curriculum
- App development
- Overall test
- Launch

These 5 steps should not last more than 5 months. In our WBS, it lasts 130 days, meaning
4 months and 10 days.

Website This step should not last more than 45 days.

development time It is divided in 3 sub-parts:
constraints - Design < 15 days
- Test interaction < 3 days
- Development < 20 days
- Test and debugging < 7 days

Training Curriculum This step should not last more than 35 days.
time constraints It is divided in 4 sub-parts:
- Courses Selection < 4 days
- Testing method selection < 3 days
- Evaluation method selection < 1 day
- Teacher selection/recruitments < 35 days

App development This step should not last more than 24 days.
time constraints It is divided in 3 sub-parts:
- Design < 10 days
- Development < 8 days
- Test and debugging < 6 days
 Overall test time This step should not last more than 12 days.
constraints It is divided in 4 sub-parts:
- Usability test < 1 day
- Performance test < 1 day
- Security test < 12 days
- Beta test < 7 days

Launch time This step should not last more than 40 days.
constraints It is divided in 3 sub-parts:
- Beta launching < 25 days
- Feedback and adjust < 34 days
- Final version launch < 3 days

TOTAL TIME 156 days or 5 months

CONSTRAINT

Cost constraints:

The website O-Learn must meet certain cost constraints.These constraints are based on the
WBS.
There are 5 main steps:
- Website development
- Training Curriculum
- App development
- Overall test
- Launch

Website development cost
constraints
The total cost of this part should be less than 8500 €
- Design ≤ 2800 €
- Test interaction ≤ 500 €
- Development ≤ 4000 €
- Test and debugging ≤ 1200 €

Training Curriculum cost The total cost of this part should be less than 2700 €
constraints - Curriculum planning ≤ 2700 €

App development cost The total cost of this part should be less than 4200 €
constraints - Design ≤ 1000 €
- Test interaction ≤ 500 €
- Development ≤ 1700 €
- Test and debugging ≤ 1000 €

Overall test cost constraints
The total cost of this part should be less than 3000 €
- Usability test ≤ 300 €
- Performance test ≤ 300 €
- Security test ≤ 1900 €
- Beta test ≤ 500 €
 Launch cost constraints The total cost of this part should be less than 5900 €
- Beta launching ≤ 600 €
- Feedback and adjustment ≤ 4550 €
- Final version launch ≤ 750 €

Insurance The total cost of this part should be less than 1700 €

Software developer expert The total cost of this part should be less than 4000 €

TOTAL COST The total cost of our project should be less than 30,000 €
CONSTRAINT