Creating the slides themselves (organizing and styling) for the final presentation.
• As might be expected, going through bullet points, such as lists, one line at a time and other items, such as use cases or diagrams, in detail can be tedious. Instead, your team may wish to show some graphics to help the audience understand and tell the story of the slides rather than read slides one line at a time.
• The students should pretend that the audience includes customers, the product owner, and other stakeholders, who are trying to find out if the app provides value to them and is the way they wanted it to be.
• In the slides, you are expected to have:
o 1 – 2 Slides: The overview of the app one more time.
o 1 – 2 Slides: Updated User Stories: If your list is long pick 5 – 7 most interesting/important one and only show those.
o 2 – 3 Slides + Demo: Mock-up of the app + Demo of the application.
o 1 – 2 Slides: Some of the most important functional and non-functional requirements – You do not need to go through all of the requirements you have. Pick the ones that you implemented or sound more interesting. Include both FR and NFR (especially security/privacy NFRs).
o 2 – 3 Slides: Some of the important use cases. Select 2 to 3 models/descriptions that you either implemented or they sound more interesting.
o 2 – 3 Slides: Some of the important sequence diagrams cases – Select 3 to 4 models that you either implemented or they sound more interesting.
o 2 – 3 Slides: The domain model and detailed design class diagrams.
o 2 – 3 Slides: The architecture design and design patterns that the team has used.
o 2 – 3 Slides: Summary of the test plan, test cases and results. If you have not completed the Test Plan, instead summarize the functionality implemented and working in the application, and partially implemented, and any bugs.
o 2 – 3 Slides: Results of the focus group and usability study (if you have done one).
o 1 – 3 Slides: Any security and privacy concerns that you have addressed or that remain.
o 1 – 2 Slides: Who did what and the percentage.
o 1 – 2 Slides: What is future work.
o 1 Slide: A link to downloadable application.
• You also must show:
o Kanban Board
o Product Backlog and Sprint Backlog.
• The ability to be engaging and convincing will win the listeners over to you. If anyone is anxious and nervous about presenting, please let me know so I can try to help.
• Team members may present ONLY the work that they have done.
• Each team member in the group must present for about 3 – 4 minutes of the presentation time.
• Place the team member’s name in the slides’ note section to receive credit for developing and presenting the slide.
Creating the slides themselves (organizing and styling) for the final presentation.
• As might be expected, going through bullet points, such as lists, one line at a time and other items, such as use cases or diagrams, in detail can be tedious. Instead, your team may wish to show some graphics to help the audience understand and tell the story of the slides rather than read slides one line at a time.
• The students should pretend that the audience includes customers, the product owner, and other stakeholders, who are trying to find out if the app provides value to them and is the way they wanted it to be.
• In the slides, you are expected to have: o 1 – 2 Slides: The overview of the app one more time. o 1 – 2 Slides: Updated User Stories: If your list is long pick 5 – 7 most interesting/important one and only show those. o 2 – 3 Slides + Demo: Mock-up of the app + Demo of the application. o 1 – 2 Slides: Some of the most important functional and non-functional requirements – You do not need to go through all of the requirements you have. Pick the ones that you implemented or sound more interesting. Include both FR and NFR (especially security/privacy NFRs). o 2 – 3 Slides: Some of the important use cases. Select 2 to 3 models/descriptions that you either implemented or they sound more interesting.
o 2 – 3 Slides: Some of the important sequence diagrams cases – Select 3 to 4 models that you either implemented or they sound more interesting. o 2 – 3 Slides: The domain model and detailed design class diagrams. o 2 – 3 Slides: The architecture design and design patterns that the team has used. o 2 – 3 Slides: Summary of the test plan, test cases and results. If you have not completed the Test Plan, instead summarize the functionality implemented and working in the application, and partially implemented, and any bugs. o 2 – 3 Slides: Results of the focus group and usability study (if you have done one). o 1 – 3 Slides: Any security and privacy concerns that you have addressed or that remain. o 1 – 2 Slides: Who did what and the percentage.
o 1 – 2 Slides: What is future work. o 1 Slide: A link to downloadable application. • You also must show: o Kanban Board o Product Backlog and Sprint Backlog. • The ability to be engaging and convincing will win the listeners over to you. If anyone is anxious and nervous about presenting, please let me know so I can try to help. • Team members may present ONLY the work that they have done. • Each team member in the group must present for about 3 – 4 minutes of the presentation time. • Place the team member’s name in the slides’ note section to receive credit for developing and presenting the slide.