Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: David Hughes
Progress on the project from the previous sprint:
-
Scheduled weekly meeting time and set up Zoom meeting: Thursdays @ 7:30PM MST
-
Created Slack workspace
-
Created Project Proposal Document
-
Created Github Repository
-
Created Trello Board
-
Created Google Drive folder
-
Shared Personal User Manuals for each team member via Slack
-
Created Project Scope Ideation document
-
Created Meeting Agenda template
-
Trello Board Snapshot
What went well?
Building out the tools to communicate and collaborate with each other (Trello, Slack, Github, Google Drive, Zoom) User manuals - learning about each other’s work and communication styles Everyone showed up to weekly meetings and participated
What didn’t work?
Having a clear path forward for next week Kicking off coding for project
How can the team improve?
Maybe start to assign some tasks to people if everyone agrees so that we improve Communication and organization ahead of time
Choose new scrum master for next sprint
Mike!
Initial project feature ideas:
Features:
-
Store data
-
User retrieves data
-
Visualize data
Architecture Brainstorm:
Welcome Interface
-
Hospital Blood Transactions
• Blood donation entry
• Transfusion entry
-
Find available blood
• Search/View any hospital’s inventory
a) Proceed to checkout
• Optimal match search
a) Proceed to checkout
-
Complications
• Record
• Search
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Michael Becker
Weekly Standup (~5 minutes total for all team members) Each team member must provide the following:
• What did you do last week?
-
Project Mock
-
Database Mock
-
Reviewed other mocks
-
Reached out to professor about services for front end and back end: do stuff locally
-
Updated Git to not have .ipynb file
• What are you doing this week?
-
Markdown file in Git
-
Working on Milestone 3 due next week
-
Finalize outline for application architecture
-
Looking for user stories
• Are any obstacles stopping you?
-
Waiting on decision for today’s meeting to start html
-
Watching course videos
Progress on the project from the previous week:
• Work completed tonight will be updated in markdown file and pushed to Git
• User stories, come up with your own before next week
What we have achieved for the sprint:
We finalized the initial application architecture, finalized the initial database architecture, decided who would be using the application, agreed on assumptions:
Who would be using the site?
- Hospital/bank administrator
Assumptions
-
Assumed the application is stored on a server that only hospital/bank administrators can access application
-
Secure login is already established
-
All hospitals are already in database so no need to ever create a new one with our system
-
Automated dispose of expiration (list by date of donation, 42 days after donation shelf life)
-
Minimum stock levels (can’t go below a certain threshold)
-
Home button on every subsequent page
-
Each transaction is one unit
-
Assume multiple donations are different transactions and have doctor's approval
Proposed Application Architecture
Welcome Interface with About page (Who is eligible to donate blood?, etc.) - Dylan
-
Hospital Blood Transactions
• Blood donation - David
• Transfusion (need to make sure blood is in bank) - David
• Sending blood from one hospital to another (checkout) - Mike
-
Find available blood
• Show all hospitals in one visual - Dylan
• More detailed view of specific hospitals inventory with search/list - Travis
- Go to send to blood to another hospital page(button at bottom of page)
-
Complications
• Report
• View reports for specific hospital and blood type - Cyro
Proposed Database Architecture
Blood Banks and Hospitals Table
- Hospital ID
- Type
- Name
- City
- State
- A+ Inventory
- A- Inventory
- B+ Inventory
- B- Inventory
- AB+ Inventory
- AB- Inventory
- O+ Inventory
- O- Inventory
Donor Table
- Donor ID
- Name
- Blood Type
Patient Table
- Patient ID
- Name
- Blood Type
Transaction Table
- Transaction ID
- Donation
- Transfusion
- Transport
- Date
- Time
- Donor ID
- Patient ID
- Medical Professional
- Hospital ID
Complication Table
- Transaction ID
- Comments
What went well:
• Everyone had great mock ups and attempted the project
• Helpful to have visuals for everyone to discuss
What didn't work:
• Different platforms made it more difficult for people to view others work
How can the team improve:
• Keep working as a team
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Michael Becker
Weekly Standup (~5 minutes total for all team members) Each team member must provide the following:
• What did you do last week?
-
Created Weekly Status markdown and pushed
-
Initial Application Architecture
-
Usage Assumptions for the Application
-
Proposed User Stories
-
Initial Database Architecture
-
Page Template
• What are you doing this week?
-
Submit Milestone 3
-
Scrum master for the week will submit the milestone
-
Dylan is scrum master for next week
• Are any obstacles stopping you?
-
Nothing really other than learning things in the class as we progress
-
Very proactive right now, will look to keep momentum going
Progress on the project from the previous week:
• Focusing on user establishing stories, added to assumptions, column to database table.
What we have achieved for the sprint:
We finalized the User Stories we will be using for constructing the application:
User Stories
-
Administrator logging a blood donation
-
Administrator logging a blood transfusion
-
Administrator requesting blood transfer
-
Administrator wants to view blood in all hospitals using visualization
-
Administrator wants to look at their own hospital's inventory
-
Administrator wants to see complications
-
Administrator wants to document complication
-
Administrator wants to know why this application was developed and what it does
To attempt/complete for next week
-
About page (Cyro)
-
Branch for each story, do not merge until the end (everyone)
-
Start to buildup database (Mike)
What went well:
• Looks like we are well ahead of pace right now
• Good discussions
What didn't work:
• All was good this week
How can the team improve:
• Keep working as a team
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Dylan Kayyem
-
Updated templates for user stories
-
Added user stories to Trello
-
Templates for donation and transfusion input
-
Create database design / collect data
-
Went over Mike's database example
-
Labeled primary key's for each table
-
yellow - primary key
-
green - foreign key
What went well?
- Action planned to win
What didn’t work?
- Had a great week of collaboration
How can the team improve?
- Keep it up monkeys!
To attempt/complete for next week
-
We picked features/pages that we would focus on for next week.
-
Names are written next to potential key features below...
Homepage?
1.Welcome Interface - About page (Who is eligible to donate blood?, etc.) - Dylan
Hospital Blood Transaction Pages?
-
Blood donation - David
-
Transfusion (need to make sure blood is in bank) - David
-
Sending blood from one hospital to another (checkout) - Mike
'Find available blood' Pages?
-
Show all hospitals in one visual - Dylan
-
More detailed view of specific hospitals inventory with search/list (Potential to add a 'send blood to another hospital page'(button at bottom of page)) - Travis
'Complications' Pages?
-
Report - Cyro
-
View reports for specific hospital and blood type - Cyro
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Dylan Kayyem
-
Created mockups for pages
-
Created database code
What went well?
- Setup sql/data used for each page
What didn’t work?
- Continued to have a great week of collaboration!
How can the team improve?
- Keep up the greap work team! Keep the communication ongoing via slack.
To attempt/complete for next week
- Each team member add a desription of particular database/sql commands used for each page.
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Cyro Freire de Lima
What went well?
- The tasks and stories assigned for this week and extra stories were developed by the group.
What didn’t work?
- Everything worked well.
How can the team improve?
- Just keep working.
To attempt/complete for next week
- Complete all the mockup pages
- Complete the html, js, css files for the mockup pages.
Attendees: Michael Becker, Travis Byrne, Cyro Freire de Lima, David Hughes, Dylan Kayyem
Scrum Master: Travis Byrne
-
Deployed app
-
Made Demo video
-
Added tests
-
Automatic inventory updates from donation/transfusion
-
Importing sample data from CSV
-
Presentation Powerpoint
-
Fixed Transfer Page
-
Finishing home page and Visualization page
What went well?
-
Functioning app!
-
App deployed successfully
-
Good layout/design
What didn’t work?
-
Trouble implementing some tests
-
Running out of time
How can the team improve? Keep it up! Prepare for the presentation
To attempt/complete for next week
-
Finishing the presentation slides
-
Practicing giving each part of the presentation