novoda / ncu Goto Github PK

Show buddy information at the end of onboarding for each NCUee

Acceptance Criteria

• At the end of the onboarding the user should be able to see their buddy information in a card

User should be able to leave a module they have already started, while keeping all the progress saved, and start a new one.

Acceptance Criteria

• User is currently working on a module and task, is able to save progress and leave the task not finished and the module not finished
• When going back to the overview you should be able to see that the previous module had been started but is not the selected one right now visually
• If you click on another module you should be able to start that module
• If you go back to the half done module you should be able to continued it and select it again

Allow user to log out from their account

Acceptance Criteria:

• While log in into the app the user has option to logging out

Allow the app to be able to be accessible with @novoda email google account Google SDK

Acceptance Criteria:

• User opens the app and gets Login screen where the user can sign in using Google account

• Once the user is signed up some user data should have been filled like his name, role, novoda office and buddy information.

The onboarding text of the NCU is compromised of bold and regular text sizes in different cards (for introduction, modules, etc). The text is fully written down on the drive and the NCU repo.

Acceptance Criteria

• User has successfully log in for the first time
• Onboarding mission statement about the NCU is displayed in light cards

When clicking on a module on the visual tree, before starting the module you should also be able to expand the description of the module to see the tasks that compromise it.

Acceptance Criteria

• You can expand description of the module to see the tasks that compromise it

Allow user to set their own study goal, time for module and goals.

Acceptance Criteria

• Allow for the user to set up their own study goal, study goal should have a due date and a module completion task as the goal

• The study goal should be editable and deleted if necessary

Design a system to see which modules have been completed by other NCUees and what they did when completing them.

Acceptance Criteria

• When looking at the modules you should be able to see which novodians have completed this module and how

While the user is doing a module they should be able to see the materials that would be necessary or could help complete said module. Those materials should be links.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for supporting materials.
• The materials should be links that can be clicked and open proper apps or explorers

When clicking on a module on the visual tree you should be able to start the module. This task should update the backend

Acceptance Criteria

• On Module list you can start module
• When going back to the visual list and the set of goals those should have been updating reflecting the new module started

While the user is doing a module they should be able to see the materials that would be necessary or could help complete said module. Those materials should be links.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for supporting materials.
• The materials should be links that can be clicked and open proper apps or explorers

Design a system to see which modules have been completed by other NCUees and what they did when completing them.

Acceptance Criteria

• When looking at the modules you should be able to see which novodians have completed this module and how

Allow user to set their own study goal, time for module and goals.

Acceptance Criteria

• Allow for the user to set up their own study goal, study goal should have a due date and a module completion task as the goal

• The study goal should be editable and deleted if necessary

Allow user to log out from their account

Acceptance Criteria:

• While log in into the app the user has option to logging out

The onboarding text of the NCU is compromised of bold and regular text sizes in different cards (for introduction, modules, etc). The text is fully written down on the drive and the NCU repo.

Acceptance Criteria

• User has successfully log in for the first time
• Onboarding mission statement about the NCU is displayed in light cards

User should be able to complete tasks on the module and save their progress.

Acceptance Criteria

• Be able to set some tasks as complete by filling up the necessary information
• Make sure the progress is automatically saved on the backend
• Be able to see the completion/progress in a visual way on the tree and on the module itself

User should be able to leave a module they have already started, while keeping all the progress saved, and start a new one.

Acceptance Criteria

• User is currently working on a module and task, is able to save progress and leave the task not finished and the module not finished
• When going back to the overview you should be able to see that the previous module had been started but is not the selected one right now visually
• If you click on another module you should be able to start that module
• If you go back to the half done module you should be able to continued it and select it again

Allow user to see their module list as a visual progression eg: tree

Acceptance Criteria

• User finished onboarding or opens the app and sees a visual representation of their modules for the NCU

• There should be a visual difference to modules completed, started and yet to start

Show buddy information at the end of onboarding for each NCUee

Acceptance Criteria

• At the end of the onboarding the user should be able to see their buddy information in a card

Allow user to tap on the visual representation of the module and read the summary of the module.

Acceptance Criteria

• User can see the tree of the modules, and read a summary of the module when clicking over the tree

• user can go back to the tree once clicked out of the module summary bubble

The onboarding text of the NCU is compromised of bold and regular text sizes in different cards (for introduction, modules, etc). The text is fully written down on the drive and the NCU repo.

Acceptance Criteria

• User has successfully log in for the first time
• Onboarding mission statement about the NCU is displayed in light cards

User should be able to leave a module they have already started, while keeping all the progress saved, and start a new one.

Acceptance Criteria

• User is currently working on a module and task, is able to save progress and leave the task not finished and the module not finished
• When going back to the overview you should be able to see that the previous module had been started but is not the selected one right now visually
• If you click on another module you should be able to start that module
• If you go back to the half done module you should be able to continued it and select it again

Allow user to set their own study goal, time for module and goals.

Acceptance Criteria

• Allow for the user to set up their own study goal, study goal should have a due date and a module completion task as the goal

• The study goal should be editable and deleted if necessary

While the user is doing a module they should be able to see the materials that would be necessary or could help complete said module. Those materials should be links.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for supporting materials.
• The materials should be links that can be clicked and open proper apps or explorers

When clicking on a module on the visual tree you should be able to start the module. This task should update the backend

Acceptance Criteria

• On Module list you can start module
• When going back to the visual list and the set of goals those should have been updating reflecting the new module started

When clicking on a module on the visual tree, before starting the module you should also be able to expand the description of the module to see the tasks that compromise it.

Acceptance Criteria

• You can expand description of the module to see the tasks that compromise it

Allow the user to press "Read more" button on the onboarding cards and get more text information about specific modules.

Acceptance Criteria

• User is reading a onboarding card that has extra information and thus a + button

• when the read more button is pressed the card gets opened and the user can read the full text of the specific card

• once done reading the user can go back to small card and keep reading the onboarding

While the user is doing a module they should be able to see links to previous work done on that module.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for previous work done.
• The materials should be links that can be clicked and open proper apps or explorers

Allow the user to press "Read more" button on the onboarding cards and get more text information about specific modules.

Acceptance Criteria

• User is reading a onboarding card that has extra information and thus a + button

• when the read more button is pressed the card gets opened and the user can read the full text of the specific card

• once done reading the user can go back to small card and keep reading the onboarding

Design a system to see which modules have been completed by other NCUees and what they did when completing them.

Acceptance Criteria

• When looking at the modules you should be able to see which novodians have completed this module and how

When clicking on a module on the visual tree you should be able to start the module.

Acceptance Criteria

• On Module list you can start module
• When going back to the visual list and the set of goals those should have been updating reflecting the new module started

Design needed for the login process and the screen after the user has been log in.

Acceptance Criteria:

• User opens the app and gets Login screen where the user can sign in using Google account

• Once the user is signed up some user data should have been filled like his name, role, novoda office and buddy information.

While the user is doing a module they should be able to see links to previous work done on that module.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for previous work done.
• The materials should be links that can be clicked and open proper apps or explorers

User should be able to complete tasks on the module and save their progress.

Acceptance Criteria

• Be able to set some tasks as complete by filling up the necessary information
• Be able to see the completion/progress in a visual way on the tree and on the module itself

When clicking on a module on the visual tree, before starting the module you should also be able to expand the description of the module to see the tasks that compromise it.

Acceptance Criteria

• You can expand description of the module to see the tasks that compromise it

Get the onboarding cards to show more than just text

Acceptance Criteria

• Video mission statement shows up on the onboarding cards and is playable from the app itself

Set up a CMS

Allow for the user to see and set up their own challenges to allow for the gamification of the completion of the NCU app.

Acceptance Criteria

Allow the user to press "Read more" button on the onboarding cards and get more text information about specific modules.

Acceptance Criteria

• User is reading a onboarding card that has extra information and thus a + button

• when the read more button is pressed the card gets opened and the user can read the full text of the specific card

• once done reading the user can go back to small card and keep reading the onboarding

Get the onboarding cards to show more than just text

Acceptance Criteria

• Video mission statement shows up on the onboarding cards and is playable from the app itself

Allow user to tap on the visual representation of the module and read the summary of the module.

Acceptance Criteria

• User can see the tree of the modules, and read a summary of the module when clicking over the tree

• user can go back to the tree once clicked out of the module summary bubble

User should be able to complete tasks on the module and save their progress.

Acceptance Criteria

• Be able to set some tasks as complete by filling up the necessary information
• Make sure the progress is automatically saved on the backend
• Be able to see the completion/progress in a visual way on the tree and on the module itself

Allow user to see their module list as a visual progression eg: tree

Acceptance Criteria

• User finished onboarding or opens the app and sees a visual representation of their modules for the NCU

• There should be a visual difference to modules completed, started and yet to start

Allow the app to be able to be accessible with @novoda email google account Google SDK

Acceptance Criteria:

• User opens the app and gets Login screen where the user can sign in using Google account

• Once the user is signed up some user data should have been filled like his name, role, novoda office and buddy information.

Allow user to see their module list as a visual progression eg: tree

Acceptance Criteria

• User finished onboarding or opens the app and sees a visual representation of their modules for the NCU

• There should be a visual difference to modules completed, started and yet to start

Allow user to tap on the visual representation of the module and read the summary of the module.

Acceptance Criteria

• User can see the tree of the modules, and read a summary of the module when clicking over the tree

• user can go back to the tree once clicked out of the module summary bubble

While the user is doing a module they should be able to see links to previous work done on that module.

Acceptance Criteria

• On a full description of module there should be an expanding bracket of information for previous work done.
• The materials should be links that can be clicked and open proper apps or explorers

Show buddy information at the end of onboarding for each NCUee

Acceptance Criteria

• At the end of the onboarding the user should be able to see their buddy information in a card