What does each group member hope to get out of this project?
- "Meets expectations"
- Understand and implement modules and inheritance
- Everyone in the group can explain every piece of our code
- Enjoy working together and form strong relationships
- Utilize project management software to help stay ahead, so we have time at the end to refactor and generally improve
- Learn how to work more collaboratively on code
What do we want to achieve as a team?
- Learn how to work more collaboratively on code
- Well organized project
- Attempt to implement something resembling an agile process (not waterfall)
How will we know that we're successful?
- Pass the project
- Learn new things
- Master new skills
- If we successfully utilize our project management tool, at the end it should express that we completed all tasks
Rostam: determination and drive. Always strives to get through Iteration 4. Collaboration style is to communicate regularly. Agile in the sense of coming together daily to compare notes and move on to next task.
Michelle: great mediator, finds solutions that work for everyone. Scheduling and sticking to a scheduled meeting time.
Ross: enjoys getting things done ahead of time so can refactor at the end and get things looking clean. Collaboration style is that he is comfortable with many different working styles.
Stella: Organized and paying attention to how all the pieces fit together in bigger picture; written communication
Fantastic Four!
Obstacles we might encounter? (in project and in group work setting)
- lack of communication
- not being on time
- not meeting deadlines
- redundant work
- git merge conflicts
How we can overcome such obstacles:
- accountability
- relying on Michelle's mediation skills
- use methods and explanations that everyone is able to understand
- communicate and be open when struggling or stuck (it's okay to ask for help or say "I don't know!")
- this is a safe place and judgement free zone. If we set this up at the beginning we are all more likely to succeed together.
- understand the twofold benefit of asking for help as the other person gets to practice explaining
- clear communication, whether written or over call, will help us help each other and accomplish our goals
(Make sure to discuss the remote questions above in regards to this section)
When are we available to work together and individually?
- Rostam is available basically all the time (time zone)
- Ross and Michelle go to bed early and wake up early(ish)
- Stella is available all the time (except times below)
What constraints do we have?
- Stella is unavilable: Thursdays from 6pm-8pm, Sunday 9-11am, Sunday & Monday 7-8 pm
- Michelle: prefer to be done working on project from 6-6:30 pm. Set schedule would be helpful for scheduling mentor meetings.
- Ross: has few constraints (daily run and standing dinner date)
- Rostam: quarantined in paradise
How and often will we communicate?
- Schedule quick daily check-ins (unless we have scheduled time already on the calendar)
- Stay active on group chat (also utilize group text)
- How to handle PRs: For the time being (unless it seems overboard) everyone needs to comment on all the PRs. Comment on your own and comment on everyone else's.
How do we keep lines of communication open?
- slack and text
- over communication is better than under communication
How will we make decisions as a team?
- Inclusion is important so we come together to discuss decisions that could impact the overall project, and listen to everyone's point of view
How will we communicate about our emotional and mental well-being with each other?
- creating a safe space free of judgement is important not just for coding but for anything that could come up
- it is ok to communicate when you need to but nothing is required
- Understand and implement modules and inheritance
- Everyone in the group can explain every piece of our code
- Rostam would like to work on data visualization
- Michelle would like to improve on organizing code and keeping the big picture in mind and seeing how pieces will fit
- Ross is striving to write most efficient code and gets excited to use 1 line code
- We all want to write elegant ruby!
- utilize mocks and stubs
- Stella would like to improve ability to explain logic in code to a partner or partners (be willing to partner to improve this)
- utilize class methods rather than collection methods
- Not sure how to answer this question based on our current understanding of the project
- Ideally we will find a way to divide it into 4 parts, work separately, merge together, and then create runner together(?)
- Everyone runs their own SimpleCov on their code and tests before PR
- One person will create the Repo for everyone to use
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We are all comfortable with git workflow, branching, etc.
- We have agreed to write descriptive comments on our own code, and on one another's code
- We will wait to merge pull request once everyone has approved
- Pry and TDD for debugging
- Take one when you hit "the wall"! or before!
- Each of us regulate our own schedule, with some encouragement from teammates to remember to take poms before we go crazy.
- Be kind.
- Be open.
- Assume positive intent.
- Have positive intent.
- Ask for feedback if you need it.
- Michelle prefers direct feedback.
- We are remote.
- Be aware of this fact.
- Exchange phone numbers (on slack)
- Use GitHub projects! If we hate it, we'll reconvene and decide whether to switch or skip it altogether.
- Set up classes and get all CSV data functional as soon as possible
- get SalesEngine equivalent functional so we can start working with CSV data in 4 separate classes
Action items before meeting tomorrow at 11am:
- create Repo - Rostam
- Project in GitHub - Rostam
- share our phone numbers - everyone!
- share GitHub usernames
- everyone review iterations 1 & 2 in preparation for tomorrow and create a diagram based on our understanding
- submit DTR!