Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due
Submission Reminder
As a team assign one team member to submit all completed documents to the submission folder. Reminder to submit a completed release summary that is completed in the Iteration Plan and Agile Backlog Excel workbook into the Iteration 1, 2, or 3 submission folder your team has completed. Submit your team's Client Sign-Off DocumentsOpens in a new tab to the assigned submission folder.
The assigned team member will also submit the weekly meeting minutes and agenda for the next meeting to the meeting minutes and agendasOpens in a new tab submission folder.
Each individual team member is responsible for submitting their individual status report to the Individual Status ReportOpens in a new tab submission folder. Please note that only your Professor/Instructor has access to these submissions.
Refer to the submission checklist for items required with each submission.
Description
Throughout the course, you will complete three iterations, where each iteration demonstrates your team's progression through the project.
Rationale
This group project proposal will evaluate the following course learning outcomes (CLO):
1. Work as part of a team to accomplish a major undertaking
2. Define the system objectives.
3. Identify the process requirements of each stakeholder.
4. Define system specifications.
5. Design a normalized database.
6. Design user interfaces and reports.
7. Prepare system planning documents.
8. Prepare program design plans.
9. Code program modules.
10. Test program modules.
11. Integrate modules into a complete system.
12. Test the system.
Directions
Your team will work towards completing each of the deliverables provided in the Agile deliverable's checklist. The focus of each iteration is to complete deliverables in the analysis, design, and construction sections as noted in your Iteration Plan, Agile Backlog and project plan. Your team is not required to submit all deliverables for Iterations 1 and 2, only those that can be completed based on the current stage of the project and client feedback. Certain deliverables may only be partially completed. For example, your team may have seven use cases with three completed in Iteration 1 and the remaining four submitted in a future iteration. By Iteration 3 all deliverables must be completed.
Iteration 1
· We recommend that 30 percent of the deliverables are completed.
· Use case diagrams are a required submission. The use case diagrams can be in their early stages where they are stick figures with bubbles. These will be further developed for your team's next iteration.
Iteration 2
· We recommend that 70 percent of the deliverables are completed.
· Use case descriptions that provide a revised list of use case names based on feedback from the Professor/Instructor and/or client.
· Your team will incorporate all of the feedback provided in the previous iteration to adjust and evolve your project as required.
Iteration 3
· 100% of all deliverables must be completed.
· Finalized use case description names.
· Your team will incorporate all of the feedback provided in the previous iteration to adjust and evolve your project as required.
Working Code Demonstrations
A recorded demonstration for your Professor/Instructor to review the progress your team has made on your project. This is a step-by-step walkthrough of your code and what you plan to add based on the use cases selected. For your team's recording, you are required to use picture-on-picture (show your code on the full screen along with your team on the screen). Your team is permitted to assign one group member to present the working code demonstration or take turns presenting different sections of the code.
Your team will add the shared recording with viewers link to your submitted consolidated document.
Speaking expectations are:
· to provide a clear introduction to your code, an explanation of your progression, and concluding remarks about what you will achieve by the next iteration; and
· professional demeanour through use of voice, body language and comfort with presentation content.
Your working code demonstration must be shown to your client either in a scheduled meeting or if the client chooses, they can watch the recorded video.
Recording Instructions
You will record the working code demonstration using Zoom. Below are the instructions for recording and sharing the demonstration with your Professor/Instructor.
To learn more, select the titles below. You can also Open All and Close All.
Open All + | Close All —
Accessing Zoom
Recording, Saving and Submitting
Zoom Options
Release Summary
Using the already existing Iteration Plan, Agile Backlog and Release Summary submitted prior to the current iteration you will input the information for this iteration's release summary. This identifies what your team plans to release throughout each iteration. The release summary will evolve as your project does and can have multiple iteration deliverables running simultaneously.
Revisions
For each iteration, your team will be provided feedback from your Professor/Instructor and your client. Based on the feedback provided, your team is required to incorporate these updates into your next iteration submissions. A reminder that the revisions must be reflected in your iteration plan, Agile Backlog and release summary submissions.
Writing Requirements
All completed deliverables and supporting documents will be compiled into one consolidated document and submitted as a PDF. Ensure your team proofreads your report and all other deliverables submitted for spelling and grammar errors.
Your document will include:
· title page that includes the project title, team members' names, team number, team name, date, course code, Professor/Instructor's name and client name if applicable;
· table of contents;
· page numbers;
· supporting images/graphics; and
· appropriate headings applied, for example, Use Case Diagrams or Working Code Demonstration to clearly indicate what deliverable is being discussed.
Select this link, Iteration Report Template to download a copy and begin consolidating your team's work.
Watch the LinkedIn Learning course Word 2016: Creating Long DocumentsOpens in a new tab to learn how to consolidate your completed deliverables into one Word document. The time to complete the course is 2:13:05.
Submission Checklist
The list provided are all the deliverables your team is working towards completing by iteration 3.
Reminder
Continue to update the Agile Deliverables Checklist provided in week 1 and in the Inception Phase assignment page to track completed deliverables.
Supporting Documents
Iteration 1
· Meeting Minutes and Agenda (submitted separately)
· Client sign-off document (can be submitted after due date based on client's availability to review deliverables)
· Release Summary (submitted to appropriate iteration folder)
· Individual Status Report (submitted separately)
Iteration 2
· Meeting Minutes and Agenda (submitted separately)
· Client sign-off document (can be submitted after due date based on client's availability to review deliverables)
· Release Summary (submitted to appropriate iteration folder)
· Individual Status Report (submitted separately)
Iteration 3
· Meeting Minutes and Agenda (submitted separately)
· Client sign-off document (can be submitted after due date based on client's availability to review deliverables)
· Release Summary (submitted to appropriate iteration folder)
· Individual Status Report (submitted separately)
Deliverables
The information provided for the deliverables will all be provided in the collated document.
Analysis
· Use Case Diagrams
· Use Case Descriptions (minimum of 7)
· Analysis level (Domain) Class Diagram
· System Sequence Diagrams (minimum of 3 significant)
· StateChart Diagram(s) for complex classes (minimum of 3 significant)
Design
· Design Class Diagram
· Design level Sequence Diagrams (minimum of 3)
· Navigation Diagram(s)
· User Interface Prototype (Menu Screen Captures)
· Output Design
· Entity Relationship Diagram (ERD)
· Data Dictionary with field level definitions or Glossary
Construction
· Unit Tests Plan and Results
How Your Assignment Will Be Graded
Your iterations will be graded using the Capstone Rubric located in the Evaluations module. Refer to the Iterations Phases and Iterations Component tab to review the grading criteria. The iterations components tab provides the grading criteria for completing all the deliverables in the analysis, design, and construction sections. The iteration phases tab provides the grading criteria for how your team has aligned the iteration plan and project plan to the current iteration; the incorporation of feedback and recommendations to iterations 1 and 2; and the criteria for the recorded working code demonstration.
Tasks such as the meeting minutes, agenda, and client-sign-off documents are assigned a completion grade that represents 2.5% of your team's final grade. These are located in the weekly checklist tab.
The individual status reports are a weekly submission assigned a completion grade that represents 2.5% of your individual final grade. This is located in the weekly checklist tab.