Sept 20th: AR Animal ID [0]

Info

Date:  Wed, S20-23
Time: 9:20-9:40am
TA directed

---

Attendance

• Tony Shi
• Pada Mayer
• Jiemin Wang
• Georgin Maliakal
• Daniel Asimiakwini -> Product Manager
• Ahmed Zihan Hossain -> Scrum Master
• Yazeed Mahmoud (TA)

Agenda

1. Project Overview
2. Sprint 1: Project Documentation
3. Sprint 1 Requirements and Deliverables
   • Project Storage
   • Project Requirements
   • Software Design
   • Teamwork
4. First Meetings' Times
5. Scrum Master & Product Manager
6. Q & A

Notes

• Project divided into 5 Sprints

• Sprint 1 has 5 major components

  1. Determine the Projection Description: Understanding the end goals of the Project from the Clients perspective.
  2. Use Project Description to outline a Design plan.
  3. Setup Up All Documentation, will build on it throughout project
  4. Determine plan for Entire Project: Splitting work between the 5 Sprints + extraTam management tasks
  5. Describe the Team.

• Sprint 1 Requirements

  1. Project Storage: All Documentation will be through GitHub Classroom

     • Will be initially setup by Yazeed. The team will build on and maintain the project’s GitHub

  2. Project Requirements: What does the Client want, what is the product

     • Exec Summary- Draft finished
       • 1 Paragraph
       • Project Description
       • The problem product addresses and solves
       • Value Proposition: Essential Functionality of Product. Why choose this product
       • Who will use product?
       • How will they use product?
     • Glossary(Domain Specific)
     • Getting User Stories - Done (maybe)
     • Similar Products
     • Open Source Products(Can Use other already done work/ideas)
     • Technical Resources(All Software Used/Plan to Use and for what)

  3. Software Design: How Design delivers Features and Requirements

     • High Level Architecture
       -Non Formal
       -Visually Explains Design plan
       -Legend
       -Includes All LAYERS x4
       - Presentation
       - Business
       - Product
       - Database
     • Major Data Elements
       • UML Class or ER
     • Interaction Scenarios
       • UML Sequence
     • Low-Fidelity UI -
       • MockUp Design
       • Some Pages/Screens
       • Look and Feel->UI UX
       • Ignore specific pictures, colours details, etc

  4. Project Management(x2)

     • Story Map(Visual-> Sprints By Categories + include US prioritized and their points)
     • Product Backlog: US to GitHub Issues(Points included) A little ambiguous if should be on GitHub or be a separate doc
     • GitHub Issues(see Product Baklog)
     • ALL SPRINTS x5
       • Due Date: Sprint 1-> OCT 2
       • Scrum Roles(Different Pair each Sprint, Everyone must be at least 1 throughout Project OR Stay same throughout)
         • Scrum Master
         • Product Manager
       • List of US
         • By Priority
         • Include FIbonacci No for difficulty
       • List of Tasks to be Completed
       • Assigned List of Tasks to team
         • Est Due date of tasks
       • Estimated Sprint Velocity->sum(US FibNo)
     • No US completion for S1, only generation

  5. Teamwork

     • Team Canvas->Assigning Project Roles Documentation
       • Will use website on eclass
     • Belbin Team Roles
       • Each member gives 3 lists
         • Preferred
         • Manageable
         • Least Preferred
       • Describe All 9 roles
       • Assign People to the 9 roles(can be many to 1 and/or 1 to many)

• A Scrum Master and Project Manager must be selected for each Sprint

  1. Scrum Master: Zihan
  2. Product Manager: Daniel

Action Items

Name	Value
Pada	None
Daniel	None
Georgin	None
Ahmed	None
Jiemin	None
Tony	None