GridIron meeting 4_11_2024

[choir241]

Attendees: Chris, Jason, Mia, Mia, Shashi, Carlos, Corina, Em, Jayna, Ryan, Richard

GridIron Meeting 4-11-2024

Introduce Mia to the entire team and her background

Talk about scheduling for the upcoming set deadline

For example, Chris is going on vacation, so there are no expectations to do any work during that time. Carlos would do more work in that case and anyone who can do cross platform like Jason or Richard will help where needed

Since there was no set deadline up until now, there was no sense of prioritization. Wanted to make it feel like a real project, like we’re working for a real company. That way, we can experience the company process, the stress, etc

• Shashi - Q: Was it a good idea to have a deadline?
• Mia - A: It was good to have a sense of urgency
• Jason - A: Whether it’s close or far, it applies positive pressure and gives the project a sense of direction
• Chris - A: It gives a specific target, which gives us something tangible to work towards. He also encourages everyone to think about what we’re really capable of doing and communicate what our realistic expectations are for what we can accomplish in respect to our own schedules and lives.

Shashi and Jayna have worked under tight deadlines in companies that were umbrellas of the software field(s), and they understand how big communication is, but this is the first experience for the majority of us. He wanted to give grace to everyone and allow team members to accomplish tasks when they were able, but on the flip side it slowed down the pacing of the project.

Keeping the deadline and amount of resources available within the project and team in mind, you shift the resources around. For example, if someone is working on a task that isn’t a high priority and they’re available, you can ask them to help you.

What can we make to reach that deadline? If we add something but we can’t reach the deadline, that is no good. But if we aim lower, finish early, and add other features, that’s a bonus for us. On a technical and security standpoint, we need to know what’s being pushed out to the public eye.

By the team members being honest and the project having no deadline, Shashi was able to quickly observe the efforts and work ethics for each team member. Any manager can easily see your efforts. Because Shashi is an engineer, and there will be other managers like this as well, he knows how long a task should take.
There was grace being given to provide opportunities to learn. If a manager starts to see there is some slack occurring for a task or something is occurring in their life, the manager will reach out to confirm the reasoning behind this occurrence, and they will be able to fully understand the reason behind the task not being completed on time.
If there is a skill gap or you’re struggling with something, communicate about that. There are no expectations to know everything, gather all the questions that you have when you’re struggling with something and ask clarifying questions. Ask with the intention of understanding all the details of the task one hundred percent. If something is not clear about a certain task, ask and clarify about that task.

Being able to identify and communicate that even after going over something with someone else and you still don’t truly understand 100%, it’s important to completely understand the task at hand and ask further question(s).

• Mai - Q: What is the recommended threshold? Ie. Didn’t know what logging classes were, but didn’t want to ask right away. Wanted to do some research and learn about it first before asking. How long would you recommend waiting until you ask (a) question(s)?

• Shashi - A: If the task is completely unknown to you, ask right away. If you understand the task, but don’t fully understand it 100%, you can research it and work on it. Until you feel blocked or are confused about something, then you ask for help. Prefers us not to ask other people because it will be a lot of contact switching and you potentially could have saved a lot of time by just asking him.

• Mia - A: More expensive with more people involved; time is money. Instead, you could ask one specific person for efficiency.

• Corina - Q: realizes she has to learn how to slice/silo zoom in on something. On the other hand, if she has time, she will look into something further because she just happened to have the time to do it, and because she is unaware what her future availability will be.

• Shashi - A: The goal is to save time in the long term and prevent us from re-doing what we have already accomplished when going too far because other things aren’t ready yet.

• Corina - Q: Wants to understand and learn more about a specific tech/tool/library like Playwright and Appwrite, but doesn’t want to overwhelm the channel with those questions.

• Shashi - A: Can post the question in the technical-help channel, but there is no wrong way to approach asking questions. Free to ask questions there or in the football-survivor channel.

  • Junior devs think their question is ‘basic’ or ‘dumb’ , but it is not. There is bound to be someone else that has the exact same question, or similar questions. Ie. Carlos and Shashi had no idea that Appwrite has integrated user models with email and password on installation.

• Jason - Q: His ticket was more in-depth than he anticipated. Should he remove everything related to Supabase including the pages, and add the Appwrite login?

• Shashi - A: Only remove the unused Supabase imports

• Chris - Q: Talked with Carlos on the backend, should it be made public? Can shashi set up a sub domain?

• Shashi - A: Yes to both.

Sprint Planning

Switch Richard to backend during Chris’s vacation. Richard should disregard SASS for now because it will take time to complete.

A team member should only have one task in progress at a time, never more. When you move a task to the in review column, take the first non-blocked task in the queue in the to-do column, assign yourself to the task, and move it to the in progress column.

• Ryan - Q: should he move a ticket to the in progress column if he’s already assigned to a task but hasn’t started it yet?

• Shashi - A: Yes. But if you’re unassigned, don’t move it to in progress until you intend to actually work on it.

• Mia - Q: Is there a channel to show the availability for all members during that current week so she knows who to contact when they are actually available during the day?

• Shash -A: No, but this is a really good idea that we should definitely do. There is a free app that does this as well.

• Shashi -Q: What do you think about the board organization?

• Jason- A: Feels fomo because he wants to do more and participate more when it comes to the project

• Em- A: loves the board, but tagged shashi and didn’t get a response

• Shashi -R: Recommends to double-dip and message him/@ him on discord due to volume of emails

Extending and basing components like a button off ShadCN and creating our own UI component library.

• Shashi - Q: Is it helpful to see what everyone is working on and what their progress is?

Closing remarks

Set your schedule and your boundaries, your family, your health and career is your priority