Daily Scrum

[devinchristianson]

Scrum 3/3 - We distributed tasks such as documentation, focus group planning, and sprint 2 development planning (choosing stories to prioritize, choosing who will do what. I will be working on mouse/touchscreen input, and flask implementation, as well as the Sequence and Domain model documents.

[dawsinb]

Scrum 3/3 - Discussed plans for documentation and coding for deliverable 2. We didn't realize that there was supposed to be two separate sprints this deliverable so we are going to count the code I was just working on in what I thought was the meantime to be for the first sprint of this deliverable and or now counting the second print to be happening now. As such we are finding someone else to be the product owner for the last sprint since I primarily worked on code then. I will be the product owner for this upcoming sprint and will guide people on what needs to be implemented for the code as well as focusing more on documentation.

[arevello]

3/3 We talked about the focus group, documentation, and user stories. My tasks are to implement user story 7, having the application recognize notes from a MIDI keyboard correctly, help with the sequence models, as well as email Sanonda and dispute some of our grades for assignment 1

[jeremythiboutot]

Scrum 3/3: Talked about documents needed to be created and updated, assigned people to documents and updating. Choose user stories to implement. Talked about code and focus group.

[AlexandreFeren]

Scrum 3/10: Allocated work to group members, ensured that documents were all in order and organized in GitHub, and decided on the new leadership for sprint 3. Discussed what documents need updating and which can be left alone for the third sprint in which I will be primarily focused on documentation for deliverable 2.

[devinchristianson]

Scrum 3/10: I am Scrum Master for sprint 3, and we have decided who will be doing development for this sprint, as well as who will be doing what doumentation. I will be integrating the existing static application with Flask, and working on the sequence diagrams and domain models documents.

[arevello]

3/10: I will be working on documentation mostly for this sprint, creating more use case and sequence diagrams and creating the format for the playback data

[devinchristianson]

3/17 - Organized final push, gathered data for team member reports, discussed plans for the next sprint. I'm going to be working on the Sprint 3 review, Domain model document, and the sequence document.

[AlexandreFeren]

3/17 - coordinated responsibilities for the end of the sprint and deliverable, as well as discussing what needs doing for the next sprint. I will be working on the Domain document with Devin C. and potentially some minor edits to other documents.

[arevello]

3/17 - discussed what needed to be done for next deliverable and talked about plans and roles for the next sprint. Coordinated what documents need to be finished and what code changes need to be implemented for the deliverable

[dawsinb]

3/10 - Discussed what I will be doing as product owner (sprint/product backlogs), and went over logistics/planning for the focus group.

[AlexandreFeren]

Discussed the progress that has been made during this sprint, currently not much as the sprint effectively started on Wednesday. I created an informal poll for when everyone will be available to meet for scrums in the wake of COVID-19, tentatively Tuesdays pending approval from everyone's availability. I will be working on chord playback in this sprint and maybe poking around at accounts using google sign-on if I have enough time to get around to it.

[devinchristianson]

We talked about what our goals were for the next two sprints, how covid was effecting our plans/schoolwork, and agreed to meet next tuesday. I will be working on google signon for the next 2 sprints, as well as the backend stuff thats needed to make that happen

[jeremythiboutot]

3/27 Talked about what needs to be done and who was assigned to what. Talked about availability again now that everyone is home and things are different. Planned when our next meeting was to see how things are going. I will be trying to update some documents from previous deliverable that need it

[AlexandreFeren]

4/4 - (forgot to update the board at the time) discussed where to go with the project in the upcoming weeks of the deliverable and which documents and issues people would be assigned to.

4/13 - Discussed the progress made since the last scrum and what issues may be worth taking care of in the next day or 2 before the deadline. Additionally briefly discussed good practices for updating issues and merges on GitHub. Documents were assigned to the group members, I will be mostly working on the Configuration Management Plan Document with Devin C.

[devinchristianson]

4/13 - Discussed progress made (on code & docs), and what needed doing next. I've worked on testing, and the config plan, test, and sprint review docs. I'm going to be continuing to work on the config plan and Test doc.

[arevello]

4/4 - discussed documents I will be assigned to and user stories to be implemented

4/13 - Trying to put out fires after all the power and internet outages. Assigned more docs to myself, as I have the two boring non coding roles for this deliverable. Work on SRS, detailed design, creating sequence diagrams for new user stories, sprint reviews, and product backlog

[dawsinb]

4/4 - Discussed which documents I will be working on going forward, and currently working on code refactoring. I will be the scrum master for Sprint 5 and thus worked on setting up the next scrum.

4/13 - After many difficulties with power and internet outages, still working on documentation and finishing the code refactoring. Working on adding sustain functionality as well now.

[arevello]

4/27 - Discussed which slides will be worked on for the presentation and discussed the best way to complete those. I will be doing the sequence diagram, use cases, and design docs.

5/1 - Discussed who would be doing what documents for the final deliverable. I will be fixing issues with the test plan, adding a new test for the metronome, and fixing the design document.