---
# System prepended metadata

title: Project Charter
tags: [Deliverable, Ideation]

---

# Project Charter
###### tags: `Deliverable` `Ideation`

## Project General Information

**Project Name:** AppConnect Workflow Manager
**Project Sponsor:** Talkdesk
**Team Leader:** Pedro Lopes

## Project Description

Talkdesk is a company that offers call center-like solutions for companies.
Talkdesk currently has a marketplace with apps that complement the main product. These apps can be submitted by external developers, but the process is currently not very efficient, involving google forms for submissions, email exchanges between the developers and the Talkdesk team and full manual verification of every app submitted by the Talkdesk team.
Wishing to improve the process, Talkdesk asked for a product that solved that issue, a platform that offers the external developers with a better experience for submitting their apps and that lightens the burden for Talkdesk workers by making automatic checks to the submitted product. This platform should make it intuitive for the developer who checks the state of the products submitted by him/her. On Talkdesk’s side, this platform should have an easy way to access all submitted apps and an intuitive way to access each app’s contents to analyze and to decide whether the app is allowed to enter their marketplace.

## Scope

This product will be available for Talkdesk's workers that are assigned to verify the apps submitted to the AppConnect marketplace and to all external developers that wish to submit apps to that same marketplace.

## Business Case

To reduce the average time (13 weeks) wasted by Talkdesk's workers by automating the submission process and by introducing automatic checks to submitted apps.
To make it easier and faster for external developers to submit apps to AppConnect *(as well as monitor the state of the submission process)*.

## Constraints

**Time:** 4 months, but all students have 4 more subjects to work on during that period of time
**Quality:** Prioritize quality over the number of implemented features
**Manpower**: 9 developers + 1 services worker + 1 or 2 multimedia worker(s)

## Project Deliverables
- A web application backended by a highly extensible workflow system to assist both developers and Talkdesk teams.
- Detailed and well-written documentation that allows Talkdesk employees to modify the workflow.

## Benefits
- Decrease the time gap between the app submission and the app approval in the AppConnect MarketPlace (average 13 weeks as of right now)
- Improve feedback of the submitted apps when reporting invalid properties
- Reduce time spent on solving submission errors
- Increase AppConnect's customer satisfaction

## Key Stakeholders
- Developers that submit apps &rightarrow; Can follow every stage of the approval process
- Talkdesk teams that analyze the apps &rightarrow; Can see the current approval processes and work on them in an organized way
- Supervisor
- Company members

## Success Criteria
:white_check_mark: The ease associated with the app submission process
:white_check_mark: Flexibility and automation of the process/workflow.

## Schedule 
- Presentation of the Product's Vision  `27/03/2020`
- End of the Product's Development  `29/05/2020`
- Presentation of the Product (LGP Challenge)  `05/06/2020`
- End of the Handover  `19/06/2020`
## Steering Comittee

**Company CEO:** Christopher Abreu
**Company CTO:** Miguel Duarte
**Company CMO:** David Soares
**Company CBO:** Fábio Seixas


## Project Team

 - Amr Abd Alrahman (MIEIC)
 - Christopher Abreu (MIEIC)
 - Diogo Teixeira (MIEIC)
 - Filipa Durão (MIEIC)
 - João Alves (MIEIC)
 - Luís Oliveira (MIEIC)
 - Olavo Silva (MIEIC)
 - Pedro Lopes (MIEIC)
 - Ricardo Silva (MIEIC)
 - Joana Camacho (MESG)
 - Maria Leite (MM)

## Risks
Since the working team is relatively big (11 people) and most of the team is composed of developers (9 developers) it might get difficult to coordinate efforts. Moreover, each of the team members has a different schedule, making it difficult to organize meetings.
As this project is being made in the context of a Curricular Unit, one must keep in mind that the course tasks are more important than the product implementation itself. Moreover each element has other courses that have to be taken care of at the same time. This is a very large time constraint that can delay the development process.
The team is multidisciplinary, so communication between different areas can generate conflicts further ahead in the project.
In an early stage of planning/developing we cannot rule out the possibility of adopting a strategy that can compromise the project (strategic risk).
Finally, the project requested is demanding and has several different technologies to be used, and as such, technological difficulties may be encountered during the development.
