Project Proposal - rosielab/pepper-documentation GitHub Wiki

CMPT 496 Proposal

Title: Product Management and Development of an Interactive Robotics Application

Our CMPT 496 proposal is to develop a new application on the Pepper robots for student ambassadors. The current Pepper apps that student ambassadors use at events are fun and interactive, but not necessarily specific to SFU, particularly SFU FAS or the department of CS. We believe that this could be an opportunity to improve FAS outreach, promote and showcase the work being done in our faculty, and leave visitors with a memorable and joyful experience from our events.

Alyssa is a student student ambassador and can represent the group of those that will be interacting and supervising the visitor-robot interactions. She has a strong understanding of the events a Pepper would be brought to, typical length of interaction, and what current does and doesn’t work with our typical deployments.

Clare represents the group of people attending the events, who are typically a blank slate and have no expectations of what interacting with Pepper is like. She has little to no bias in the current Pepper deployments process, and can be a constant test user of the application we intend to create.

Learning Objectives:

  • Be able to solicit user personas, use cases and scenarios through interviews

  • Be able to write and maintain a product requirement document

  • Be able to create and maintain a product backlog for developers

  • Be able to perform user testing and integrate feedback

  • Be able to develop a robotics application that meets functional and technical requirements

Deliverables:

By the end of the term, we would have an application for a Pepper robot to be deployed at student ambassador events. In the event that the scope of this work would be beyond our capabilities and resources, we would at least have a strong base for us or others to continue to work on this project.

We would have collected and created:

  • An investigation into the current state of student ambassador applications, their benefits and shortcomings, and an understanding of how well they are generally received

  • Use case documentation

  • A well-defined minimal viable product

  • A feature roadmap

  • A UX/UI design for our application

  • A codebase

Another benefit to our project would be that we would likely update a Pepper with new software, which would be a trial run if Rosie Lab intended to update more. We would encounter, and hopefully solve, all those issues.

**Grading Breakdown **

10% - Weekly Meetings (6 total)

30% - Bi-weekly Sprint Reviews (6 total)

10% - Product Requirements Document (PRD), initial draft

20% - Final Demonstration/Presentation

30% - Final Report and Code, including final PRD

Resources

Martinelli, Russ J., and Dragan Z. Milosevic. Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons, 2016.

Pepper Application Development tutorials and resources

Developer Center

Pepper SDK for Android — QiSDK

Advising Staff

Angelica Lim