Wiki - Andriod-GDUFE/PPtoy GitHub Wiki

Wiki

1、App name:PPtoy

2、Team :

周婷 [email protected]

翁丽清 [email protected]

王琨 [email protected]

林碧华 [email protected]

3、Short description of the app

Our group's app mainly for 2 to 4 year old infants. Our app can exercise the child's ability to recognize, let the child know what the purpose of a good thing, so that children can play in the world at the same time to deepen the understanding of the world.

4、Idea Proposal

https://github.com/Andriod-GDUFE/PPtoy/wiki/PPtoy-ideaproposal

5、Product Backlog

Product Backlog(1)

https://github.com/liqingweng/PPtoy/wiki/Product-backlog%EF%BC%881%EF%BC%89

Product Backlog(2)

https://github.com/Andriod-GDUFE/PPtoy/wiki/product-backlog%EF%BC%882%EF%BC%89

Product Backlog(3)

https://github.com/Andriod-GDUFE/PPtoy/wiki/product-backlog%EF%BC%883%EF%BC%89

6、Architecture &Design

•Links to all the architecture and design artifacts. Initial design and iterations on the designs should be present

Content

•Link to the content (questionnaire, pictures, links etc…)

•This may be in GitHub issues and labelled as Content

•We need to have access to all the content in one click!

7、Scrums

•Organized in inverse chronological order with the names of the developer who submitted the scrum and the date it was submitted

•Sprint 1

•Spring 2

•Sprint 3

•…

8、Demo & Retrospectives

•Organized in inverse chronological order

•Demo & Retrospectives 3

•Demo & Retrospectives 2

•Demo & Retrospectives 1

•…

Testing

•Link to bug reports organized by sprint

•Sprint 1

•Sprint 2

•Sprint 3

•…

•Reports on testing

Process description

•Reflection on the process used during the project (to be done at the end of the semester)

Communications

•Description of all the team communication (chats, face-to-face meetings, SMS, social networks…)

Calendar

•Link

Tools

•List of tools for the project organized by Project Management, Technical and Communications tools

•List all the tools

NB:

•The organization of the wiki is important

•The English is important

•The form is important. It must be easy for the reader to go through all the material

•Create pages if necessary to make the documentation easier to read

•Please do not use long urls. Use short urls

•The organization of the wiki can be changed but all the components must be available

•The size of the images on the wiki must be adapted