-
Notifications
You must be signed in to change notification settings - Fork 4
Meeting Minutes (Sprint Planning and Reviews)
Raymond Sarinas edited this page Nov 29, 2019
·
1 revision
Attendees: Raymond, Trishia, Jacob (and Mohammad for like 5 min)
- Need to have tasks for different stories ready for work so if anyone can just continue on and pick up a task instead of just abruptly stopping and working on something else altogether.
- Trishia suggested we all work separately on different activities/views/fragments/pages so that there are no conflicts when working on different things simultaneously. Minimize bad things happening early on and then we can deal with integration afterwards (i.e. we can work on all the stuff for one activity, while leaving out OnClickButton functionality, for example, then actually implement that stuff when it is necessary).
- The basic functionality of each individual page/activity should be able to work independently without too much dependency on other things.
- Changed some of the risk levels for the first 3 features; decided that we will modify and refine the story point sizes later when we are actually working on doing the programming stuff.
- “Main Activity” page on the actual will more or less be a navigation hub, where everything else that we have will go out and do other things.
- Need to ask Pranav about using Git Rebase
- Need to book meeting rooms somewhere with big screen or TV so we are not all crowding around a tiny screen/just one person’s computer. (Also need for watching Netflix when taking a break or when deciding to give up on something)
- Raymond suggesting we use Trello for individual story tasks that could then be linked as just a TODO/Task List under actual user story issues that are on GitHub?
- Mohammad says to just use Trello and says he can book DICE first floor rooms → probably best to have these booked for our longer meeting times like this whenever we meet up on weekends to work on the project.
- Raymond will set up team Trello board and organize what we need to get done. Should be set up by Wednesday or Thursday night in time for Friday meeting.
- Backlog looks OKAY, we can try breaking up bigger stories into smaller chunks, then refine again later when we actually work on them (We can do this through Trello so we can make tasks and stuff like that).
- Work on breaking them up throughout the week, just so we don’t have to do too much all at once.
- Anyone other than Pranav use Figma before? We need someone to maintain the mockups and storyboard sequences as we move on, to make sure everything is up to date.
- Raymond suggests that Figma updates will be required to be done after finishing a feature or story, or like, a task that involves changing the UI/UX stuff.
- Need a volunteer to get started, or Raymond will pick one and it will need to be done before next meeting on Friday.
- Trishia maybe a potential volunteer?
- Don’t think anyone has time for this. We will get this done on Friday, or Sunday when we all get together.
- Raymond will get the wiki started.
- Need someone to make an overview description type of thing for the project?
- Mohammad will do the Open Source License stuff
- Someone needs to volunteer to get all our informational references/related tutorials onto a Wiki page.
- Raymond suggests that if someone learns how to do something we should make little tutorials or “how to use this” wiki pages. Will help a lot if someone who doesn’t know how to use something is able to learn quickly what to do instead of watching a 30 min tutorial. (Should include some dummy code and/or link to tutorial.)
- Need to discuss what other special terminology we need in a glossary (Raymond needs help with this).
- How exactly are we going to be dividing up the work?
- We need a working agreement when it comes to code reviews, assigning work/tasks to individuals and how this will work if we are working in pairs or in a group.
- How will we track this work through git commits? Might need to ask on the email chain.
- How does this work if someone is working on a task that needs to be reviewed by multiple people? Like if someone works on something involving the UI and Firestore, who is in charge of reviewing? Will both Jacob and Trishia have to review it? If so, who has the final say? - We are probably and very likely just over thinking this
- Trishia suggests we can pair up and comment and basically review the code specific to their parts alone, then just review overall stuff together and say if it’s okay or not.
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav (ALL)
How exactly are we going to be dividing up the work?
- With code reviews, presumably will have Pranav and Emmett generally oversee reviews to see if they meet both user requirements and if they follow proper convention. A third reviewer could also take a look, depending on who has more expertise on what needs to be reviewed.
- Pranav will take lead in making sure we follow proper code convention and basically act as the architect for our project/app.
- Pranav will also take lead in maintaining Git Workflow, apparently.
- Going to use both Trello and GitHub. Trello will maintain smaller tasks for issues/stories that, if to be made into issues, would be unnecessary (i.e. having a task to “update documentation” or “make a MockFlow account”).
- GitHub integration with Trello; GitHub issues will be linked to Trello Cards which will just be tasks for the team to pick up and work on.
- Trello board will be made public for our TA to have access to and be able to see what we might be working on.
- Figma was too hard to figure out so we are opting out to use MockFlow instead.
- Emmett converted our user stories into issues so that we can later use them and integrate them onto our Trello board.
- Jacob suggests we will likely need to have more than one database - one to be used for testing/development, and one for deployment/production when we actually demo or release the app/project for evaluation.
- Mohammad had an epiphany and now thinks our Mood Events should be called "Vibes" (like how Twitter posts are called tweets).
- Refined the Backlog together; broke down some of the bigger user stories into more manageable chunks (but still subject for refinement as we work on them later on).
- When we beginning actually working on the user stories and have our base code down, we will further refine our user stories so we can all work on them independently or together on branches.
- When reviewing, reviewer needs to put their name on the Trello card for task being reviewed to be held accountable if anything goes wrong.
- Need to look into FireStore/FireBase integration and usage of Geolocation tags and Google Maps API stuff. - Jacob?
- Will try to have weekly meetings on Saturdays from 11am-2pm in DICE 1-250 (Mohammad already got it booked for us).
- No meeting Saturday, October 19. Will have a brief one on Friday, October 18, most likely.
- Convert User Story to an Issue
- Under Issues tab on GitHub, add a new Issue
- Name what the Issue is doing/what it's for
- Add reference to User Story that was converted into an issue
- Assign an owner on the story to be responsible for making sure the story requirements get completed and make sure to have a list of tasks that could be worked on by multiple people.
- Branch Naming Convention: UserStory:IssueID.Task/SubIssue
- Emmett and Mohammad broke down user requirements into issues on GitHub, and into user stories. Emmett added rationale to each story.
- Today, worked together to break up bigger user stories and requirements into smaller chunks.
- Sized stories accordingly and refined rationale on some stories.
- This should be finished, might add Backlog information on Wiki.
- Raymond got started on the Mockup UI/Storyboard, and made a MockFlow account for all of us to use.
- Trishia worked on and did bulk of the work on the Mockup UI and finished up the Storyboard. Mohammad did work on it too.
- Team looked over UI Mockups and Storyboard and refined a little bit.
- Raymond and Trishia will finish up UI Mockups (just need to add labels and descriptions) and update Wiki.
- Jacob, Pranav, Trishia, and Emmett started working on UML diagram.
- Pranav will take on most of the effort into making the UML Diagram with Team's consultation.
- Should be finished by Thursday, October 17.
- Raymond and Mohammad worked on the Wiki, finished the glossary and made all the pages we needed.
- Jacob been doing research and looking into what we need for FireStore and how to use it for what we need for our app.
- Mohammad added the Open Source License stuff
- Raymond, Jacob and Mohammad will continue to maintain Wiki, but Team will need to put in the effort to make sure everything also stays up to date as work progresses.
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav (ALL)
- Finalizing submission for Project Part 2
- Need to get started on code base to be able to start working on actual issues ourselves
- Need to prioritize list of issues so we know what to work on first.
- Team should work on different things (maybe together in smaller groups) to cover more ground?
- Mohammad and Raymond refined the Backlog together; broke down some of the high priority user stories (i.e. those that we need part of our code base) to have task lists that any one of us is able to pick up and work on.
- Trishia, Pranav, and Jacob worked on the code base together. Still a work in progress, still needs some refinement/review.
- We need to further refine stories because our code base as it currently stands has involved and intertwined multiple issues at once with small missing pieces that are still to be worked on from each of those issues.
- Decided that team will no longer use Trello because we may begin to run into the issue of micromanaging and such.
We have come to an agreement that we will, for the most part revert our initial thoughts on renaming “Mood Events” to “Vibes” instead, we will refer to anything with the word “Mood” with “Vibe” i.e. an “Emotional State” is just a “Vibe” and a “Mood Event” will be a “Vibe Event”. This will be reflected in our code base, however, a separate issue to update all the documentation, including the UML and storyboards/mockups should be made?- Emmett to continue working on Backlog and making task lists for later issues.
- Trishia, Pranav, and Jacob continue working on code base.
- Busy week next week with all of us having at least 2 midterms, planning to not have much done by then. Will have another work session next Saturday to get things going smoother.
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav (ALL)
- Finalizing what exactly we plan to have accomplished/completed by November 8 (Part 3)
- Need to re-organize what we have done for the code base and figure out which issues have actually been fully covered/completed.
- Need to prioritize list of issues so we know what to work on first. ✅
- What did we all get done since last week?
- Work Session in groups
- Delete Trello board ✅
- We have created Milestone for Part 3, that is, we plan to finish all necessary work so that the project/application works for an individual user for their own personal use. Part 4 will involve implementation of the social aspect in its entirety more or less.
- Mohammad and Raymond refined the Backlog and will continue do so at weekly meetings most likely with consultation from rest of team. Team discussed what we will be working on.
- Busy week for everyone with midterms with not a lot of progress having been made.
- We need to work on overhauling the UML provided Ali's feedback as well as refining it as we go along, including our code base.
- Emmett will take a look at how we are going to implement using Locations as part of Mood/Vibe Events, as well as handling whatever Intent tests we may need to have.
- Code base merged and ready for work (and refinement once UML completed).
- Mohammad and Raymond continue to work on Issue #35, as well as working on adding unit tests for the code base when ready.
- Trishia going to look into how we should be selecting Emotional States (Vibes) when creating a new Vibe Event.
- Jacob working on setting up Firestore for the team to use.
- Pranav and Emmett working on modifying the UML as well as the model classes we will need as part of our base.
- After next lab, Mohammad will try to set up and maintain CI Pipeline (if necessary).
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob
- What did we get done so far? How much do we have left to do in the next 6 days?
- Distributing work more efficiently and being more consistent across how we have been working (Retro)
- Pranav finished working on and modifying the UML addressing feedback from Part 2.
- Emmett has looked into using Google Maps API and integrating services with our application. Need further discussion with Jacob with regards to how it should work with Firestore and various logging in/authentication issues we have previously discussed.
- Jacob set up Firestore and documented how we could use various queries.
- Raymond refined some issues and investigated looking into using factory patterns for model classes.
- Mohammad tried to set up CI Pipeline using Travis CI lab material to no success. Need to look more into how we could potentially set this up eventually in the future.
- Trishia looking into changing user interface properties and having a custom selector.
- Super busy week and it is looking like might not be able to accomplish our Part 3 Milestone - likely will be pushing it close with respect to getting every "single-player" aspect of the application completed. Location services/map view is likely to be worked on last or at least very close to the deadline.
- Basically getting as much of or Part 3 Milestone completed.
- Raymond will divide up work and oversee what is going on over the week until the deadline and also finish working on issue(s) related to emoticons/colours and any unit testing.
- Mohammad continue looking into using Travis CI and updating all documentation and work on creating the UI/intent tests.
- Jacob to continuously be integrating various database-related functionality as we go along completing issues/stories.
- Pranav to work on as much as he can with the basic functionality of Adding a Vibe Event and will manage making sure our code is coherent.
- Trishia will work on all the user interface design/aspects of the app to make sure it looks presentable as well as working on various Vibe Event activities like editing, deleting and making sure we adhere to what we are intending to have in the mockup.
- Pranav will complete as much of the basic functionality for the application as he can with support from rest of team.
- Emmett will take on integrating authentication with Firestore and Google Maps services into our app.
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav
- Complete work on what we missed in Part 3 Milestone and what we can do.
- Discuss how much work we want to get done this week and refine all remaining backlog stories/issues.
- Do we still want to do Travis CI? GitHub CI is also an option.
- Cleaning up Product Backlog/Issues
- Do we want to use Toast everywhere?
- Choosing a custom selector for picking a Vibe
- All worked collaboratively before deadline for Part 3, managed to complete a majority of what we wanted for the Part 3 Milestone. Only had issues with the Map View, but we are still able to see the Map.
- A lot of the testing was not completed since we still haven't decided how to test with the Database.
- Will try to get everything done from Part 3 Milestone, and by the end of the week try to get logging in with authentication completed.
- Mohammad will look into using other CI options but probably will not have time to implement/use.
- Pranav will handle where we will be using Toast
- Raymond figured out the Custom Picker - we will be using a CarouselPicker library.
- Need to do a lot of refactoring because of last minute changes and additions from working on Part 3. - Need to do these ASAP because might get swamped with having to refactor too much of the base.
- Continue on finishing the Part 3 Milestone issues/stories/.
- Raymond will continue to divide up work and oversee what is going on over the week, finish implementing the CarouselPicker and work on refactoring and assisting with UI aspect of the Map View.
- Mohammad continue looking into using some sort of CI, updating all documentation and continue to work on creating the UI/intent tests while assisting with any other issues that need to be worked on.
- Jacob to continuously be integrating various database-related functionality including user authentication, and work with Emmett to finish the Map View functionality.
- Emmett will work with Jacob to continue getting the Map View functionality working and good to go. Lots of authentication/database-related issues with this.
- Trishia will work on getting started with the social/multi-player aspect of the application. Once Jacob has gotten the user authentication working, Trishia will implement Searching for Users functionality.
- Pranav to work mostly on refactoring everything from the Part 3 milestone and manage making sure our code is coherent.
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav
- Mostly a work session, get up to speed with what everyone is working on.
- What are we doing with CI?
- Try to get all stories that are being worked on/are in progress done by the end of the day.
- Raymond got the CarouselPicker working but performance is lagging? Might have to consider refactoring how we have our VibeFactory.
- Jacob and Emmett got the Map View functionality done!
- Mohammad says no more CI, and is looking into if we should move from using Robotium to Espresso for our UI/Intent/Integration tests because of issues with testing certain aspects of the application code.
- Mohammad will also take on doing a majority of testing - working mostly on creating black-box testing from user perspective and will continue to due QA-related activities.
- Trishia added custom toolbar and continuing to work on UI issues.
- Pranav still refactoring and finally implementing Social Situation enums.
- Got through refining all current issues related to the rest of the user requirements.
- Will need to continue refactoring as we go since the current refactoring issue is getting too big.
- Continuing planned work from last meeting.
- By next week, we want to complete Searching for Users, Viewing Profiles, implementing a Map Fragment when viewing Vibe Event details, and any other refactoring issues done.
- Towards next weekend, want all user requirement functionality completed. Following/Follower requests should be started to work on by next weekend/meeting to make sure we have at least one week of leeway time to fix any outstanding issues and refactoring that is required.
- End of work session - got all in progress stories and Part 3 Milestone issues done!
Attendees: Raymond, Mohammad, Trishia, Emmett, Jacob, Pranav
- Intend to mostly have this be work session to get all user requirement issues/stories completed.
- How will we divide up the work for refining and refactoring our code once all user functionality requirements are implemented?
- What 'Wow Factor' functionality do we want to try to work on once everything else is completed?
- All user requirement functionality has been completed.
- Pranav did some refactoring
- Trishia, Raymond, and Jacob worked on completing the follower/following and vibe event sharing functionality
- Emmett refactored and completed the geolocation/map related functionality
- Mohammad still working on tests apparently and decided we are moving to use Espresso for UI/Intent tests for ease of use and convenience.
- Mohammad finish all testing related issues and activities and is gone Thursday/Friday
- Raymond to plan out and distribute work for the week and figure out how work will be done and assist in whatever issues he can work on. Will be responsible for updating whatever documentation we need.
- Trishia to do final touches on modifying the UI and maybe updating the mockups.
- Jacob to support on working various issues relating to Firebase and assist in adding extra features we want to have as extra.
- Emmett to continue working on map related issues and finalize what needs to be done and assist in refactoring.
- Pranav to take lead on refactoring and implementing controllers in the code base to better reflect our current UML diagram.
- Want all coding-related activities and issues to be completed by Thursday and spend entirety of Friday working on documentation, finishing touches and other stuff for presentation.
Attendees:
- Prep for Demo/Presentation