3.

SCOPE MANAGEMENT –
3.1 WORK BREAKDOWN STRUCTURE –
Task Dependencies Resources Start End Notes
Date Date

1. Requirements Construction of Acquiring/locating 12/06/22 - Keep this going

the entire requirements on until the end
system of the project.
1.1 Application 13/06/22 13/06/22
architecture
document
1.2 Figma Construction of Stakeholder 14/06/22 16/06/22
prototypes web/app approval
1.2.1 Web app 14/06/22 15/06/22
design
1.2.2 Mobile app 15/06/22 16/06/22
design
2. Back end Data control 17/06/22 22/06/22

2.1 Media database Show info in Datacenter 23/06/22 25/06/22

the web/app
2.2 Authentication User logins Collecting student 25/06/22 26/06/22
provider info
2.3 Provide Analysis of Student feedback 26/06/22 28/06/22
collected data to student
concerned feedback
individuals.
3. Web application student 28/06/22 10/07/22 May change
feedback according to
system stakeholder
feedback
3.1 Home page 28/06/22 30/06/22 Dashboard

3.2 Login page 30/06/22 01/07/22

3.3 User profile 01/07/22 02/07/22

3.4 Feedback 03/07/22 06/07/22

portal
3.5 Admin portal 06/07/22 08/07/22

4. Mobile student 11/07/22 20/07/22 May change

application feedback according to
system stakeholder
feedback
4.1 User 11/07/22 13/07/22
authorization
4.2 User profile 14/07/22 15/02/22

4.3 feedback portal 16/07/22 19/07/22

3.2 DEPLOYMENT PLAN –

After the construction of the application beta version of the application will be
released to check for bugs and get the user feedback to improve the quality of
the product. Expert personnel will be appointed for monitoring and maintenance
of the application. Timely meetings will be held for discussion on the
improvement of the application. A list of the members involved in developing the
application will be kept so that they can be addressed if needed.

3.3 CHANGE CONTROL MANAGEMENT –

Standard change requests should be made, and they’ll pass through
management review.
Change requests will be evaluated in a structured way for analyzing imaginable
outcomes.
A change log should be maintained which contains the date of the
implementation of the changes, and the personal details by whom changes were
implemented. Only assigned personnel will have the authorization to make
changes. The rollback process to the previous version should be determined.
When changes are implemented project management plan documentation
should be updated accordingly.
System accessibility should be controlled to prevent unauthorized access.
The new version of the application should be tested thoroughly.
A documented authorization of change will be acquired.

7. COMMUNICATIONS MANAGEMENT –
 Communication planning is one of the most important parts of project
planning. Communication with the stakeholders will help clarify all the goals
and objectives.
The communication planning process will help in understanding relationships
between audiences, messages, activities, and materials. It helps clarify who
needs to know what and when.
Communication planning will clarify the roles and responsibilities an individual
needs to carry out. It will bring all members involved with the project to the
same page.
Communication about the requirements and changes in the project will
provide clarification among the members.
Letting members know the value of their contribution to the project and
integrating their opinions brings a sense of ownership which can motivate
them to work with heart.

7.1 COMMUNICATION MATRIX –

Responsible Audience Vehicles of Frequency Medium Feedback
Party/ Situation communication Mechanisms/
Notes

Introduce Project team, Kick-off Once Face-to- Each member

project, review Project meeting (10/06/22 face will get a
objectives and manager @ 10 am) specific time to
goals. Stakeholders, share their
thoughts or ask
questions.
Review status of Project team, Status review Weekly Face-to- Each member
the project. Project meeting (Sundays face / video should prepare
manager @ 10am) conference their reports for
the respective
weeks.
Review Figma Model design Team meeting Once Video Each team
prototypes team (16/06/22) conference members
should be
clarified about
the model
design
Discuss , review Development Team meeting As Face-to- Members can
technical and team required face share their
design problems problems and
and solutions provide
solutions.
Request for Project team, Change control As Video Necessary
changes Project meeting required conference documents
manager should be
Stakeholders present.
Web application Project team, Project review Once Face-to- Feedback
delivery and Stakeholders, meeting (09/07/22) face needs to be
review Project documented
manager
Mobile Project team, Project review Once Face-to- Feedback
application Stakeholders, meeting (20/07/22) face needs to be
delivery and Project documented
review manager
Discussion Project team, Close-out Once Video A close-out
about future Stakeholders, meeting (25/07/22) conference report will be
maintenance, Project created added
and assigning manager to project
eligible report.
personnel,
completion of
all deliverables