Project Charter¶
Lezioni alla pari¶
January 4, 2020
Team Members¶
Ovidiu Andrioaia
David Cirdan
Luciano Mateias
Zhiyang Xia
Document Control¶
Change History
| Revision | Change Date | Description of changes |
|---|---|---|
| V1.0 | 01/04/2020 | Initial release |
Document storage
This document is stored in the project's GIT repository at: https://github.com/KilliKrate/Software-Documentation-G6/blob/master/docs/Project%20Charter/index.md
Document Owner
Group 6 is responsible for developing and maintaining this document.
Table of Contents¶
Schedule Information (Major milestones and deliverables)
Financial Information (Cost estimate and budget information)
Project Title: Lezioni alla Pari¶
Start Date: 04/10/2019¶
End Date: 09/13/2019¶
Project Manager: Ovidiu Costin Andrioaia¶
Project Sponsor: ITI G. Marconi¶
Customer: Nadia Dallago, Lorenzo De Carli¶
Users: Public and Private Institutions and Companies¶
Stakeholders and Expectations¶
Team: has the authority to make decision for the entire project, incuding resource management, and has to organize and complete tasks based on the other stakeholders needs and partner feedback.
Customers: will use the application to share learning material and leave simple quizzes as a way to summarize each lesson.
The Sponsor: will have an application to enhance the school’s learning experience for its students and professors, while also gaining local visibility since it was made by its students.
Purpose¶
Thanks to the creation of an online open-source learning platform students and professors alike will be able to streamline knowledge sharing between small groups, classes, or even entire departments, while also making computerized quizzes and tests easier to make. Other insitutions and companies will also be able to use this system for learning materials and resources, especially for interns or new employees.
Goals and Objectives¶
The overall goal is to give school and company figures an easy to use and intuitive platform to share knowledge by creating courses and quizzes. The app is expected to:
- Provide an account login, registration and options section
- Provide a way to create and manage courses and quizzes
- Provide a way to add partecipants to a course, in the form of collaborators or students
- Function in a simple and intuitive manner, so that it's usable to all demographics
- Deliver content efficiently and on-demand
Schedule Information (Major milestones and deliverables)¶
| Date | Review / Milestone |
|---|---|
| 04/10/2019 | Project start |
| 04/15/2019 | Software Documentation and planning completed |
| 04/16/2019 | Start of the first iteration |
| 05/20/2019 | Review of the first iteration |
| 05/22/2019 | Start of the second iteration |
| 07/01/2019 | Beta release and feedback from stakeholders |
| 07/08/2019 | Further development of the platform |
| 09/13/2019 | Application fully downloadable from Github repository |
Financial Information (Cost estimate and budget information)¶
-
1 project manager and back-end developer and at 4 hours per week for 24 weeks
96 hours * €20/hr = €1920 -
1 marketing specialist and front-end developer at 4 hours per week for 24 weeks
96 hours * €20/hr = €1920 -
1 back-end dev at 4 hours per week each for 24 weeks
96 hours * €15/hr = €1440 -
1 front-end dev at 4 hours per week each for 24 weeks
96 hours * €15/hr = €1440
384 hours total, €6720 total, avg, €17,5 per hour
Project Priorities and degrees of freedom¶
Internal development dates are generally flexible only by a few days at most, and with the authorization of the project manager. Budget is extendable in terms of hours put in by each team member. The team members amount of weekly hours may change based on the amount of work to be done, as organized by the project manager. Roles are changeable based on workloads of individual team members. Roles are expected to shift throughout the project as needs arise.
Approach¶
The SCRUM development strategy will be used to its fullest extent, as development will be based on Sprints, after which feedback from the stakeholders will be received and analyzed for subsequent iteration. After the back-end and basic front end has been deployed, a beta phase will start, in which all partners will give useful feedback for UI and UX improvements before the final release.
Constraints¶
The project will have to be supported by at least 3 partners before the beta phase, in order to have an acceptable amount feedback. The application must satisfy security and privacy standards of public institutions before release. If support after release or partners is not sufficient, the platform will be launched to the public domain as an online learning tool.
Assumptions¶
Team members will work from home, since no office space is available. Collaboration will be made possible through Github.
Success Criteria¶
At least 3 official insitutions/companies that have successfully adopted our platform will be considered as a success to the project. The platform’s efficiency in the learning process can be measured through an integrated star-based review system. We expect this outcome to be achieved in about 2 years.
Scope¶
The software will provide users with the tools necessary for the creation of illustrated text documents and will also enable them to upload video lessons. A Q&A section will be available on each lesson in a forum-like structure. The result of the quizzes will be accessible by the creator of the lesson, who will also be able to review the answers given by each user. The project does not include a file-sharing system, although it could be implemented as part of a post-release update.
Risks and obstacles to success¶
The project faces a notable risk because of the lack of the team's relevant experience on developing database-based applications. A base monthly financial target has to be achieved in order to keep the project alive. Not reaching the minimum target will result in the failure of the project and the consequential end of support.