Sprint 3 - Stand Up 2

by ADMIN 22 views

Recap: Setting the Stage for Success

As we embark on Sprint 3, it's essential to reflect on the progress made so far and the key takeaways from our previous meeting. On Monday, 3/10, the team met with Zach and Dr. Riley to discuss the true deliverable of our project. After a thorough discussion, we decided that our primary focus would be on developing a CLI (Command-Line Interface) Tool. This decision was a crucial step towards defining our project's scope and ensuring everyone is on the same page.

In addition to clarifying our deliverable, we also discussed workspace logistics and rules. This was an essential step in establishing a smooth workflow and ensuring that everyone is aware of the expectations and guidelines. The team decided on a time to meet this week, which will be at 5pm on Friday, 3/14. This meeting will mark the beginning of our work on the physical component of the project.

To prepare for this meeting, the team started exploring the possibilities of parsing CAN (Controller Area Network) logs using Python libraries. Zach provided the necessary captures, and we began experimenting with different libraries to see which one would be the most suitable for our needs. This initial exploration will help us lay the groundwork for our work on the physical component and ensure that we're using the most effective tools for the job.

Roadmap: Charting Our Course

As we move forward with Sprint 3, our primary focus will be on meeting with Zach and beginning our work on the physical component. This will be a critical step in our project, as we'll be gathering information and assessing the feasibility of our design. Based on the insights we gain from this meeting, we'll be able to adjust our roadmap and make any necessary changes to ensure that we're on track to meet our goals.

In addition to working on the physical component, we'll also be starting to look into CLI tool building, specifically using Python. We'll be evaluating the argparse and click libraries to determine which one would be the most suitable for our needs. This will be an essential step in developing our CLI tool, as it will enable us to create a user-friendly interface for our project.

Roadblocks: Overcoming Challenges

As we navigate the challenges of Sprint 3, we're aware of a few potential roadblocks that could impact our progress. The first challenge is the HVAC (Heating, Ventilation, and Air Conditioning) unit, which is currently blocking the truck from being parked inside the garage. This could create logistical issues and may require us to find alternative solutions.

Another potential complication is the physical component itself. As we begin to work on it, we may encounter unexpected challenges or setbacks. This could be due to a variety of factors, including design flaws or unforeseen technical issues. To mitigate these risks, we'll be working closely with Zach and Dr. Riley to ensure that we're on the same page and that we're taking a collaborative approach to problem-solving.

Key Takeaways and Action Items

As we conclude our Stand Up 2 meeting, there are a few key takeaways and action items that we need to focus on:

  • Meet with Zach and begin working on the physical component on Friday, 3/14.
  • Start looking into CLI tool building, specifically using Python and evaluating the argparse and click libraries.
  • Be aware of potential roadblocks, including the HVAC unit and potential complications with the physical component.
  • Work closely with Zach and Dr. Riley to ensure that we're on the same page and that we're taking a collaborative approach to problem-solving.

Q: What is the primary focus of Sprint 3?

A: The primary focus of Sprint 3 is to develop a CLI (Command-Line Interface) Tool. This decision was made after a thorough discussion with Zach and Dr. Riley, and it will be the main deliverable of our project.

Q: What is the significance of the CLI Tool?

A: The CLI Tool is a crucial component of our project, as it will enable us to create a user-friendly interface for our project. This will make it easier for users to interact with our system and will provide a more seamless experience.

Q: What libraries will be used for CLI Tool building?

A: We will be evaluating the argparse and click libraries to determine which one would be the most suitable for our needs. Both libraries have their strengths and weaknesses, and we need to choose the one that best fits our requirements.

Q: What is the current status of the physical component?

A: We have started exploring the possibilities of parsing CAN (Controller Area Network) logs using Python libraries. Zach provided the necessary captures, and we began experimenting with different libraries to see which one would be the most suitable for our needs.

Q: What are the potential roadblocks for Sprint 3?

A: The potential roadblocks for Sprint 3 include the HVAC (Heating, Ventilation, and Air Conditioning) unit, which is currently blocking the truck from being parked inside the garage. Additionally, there may be complications with the physical component as we begin to work on it.

Q: How will the team overcome the potential roadblocks?

A: To overcome the potential roadblocks, we will be working closely with Zach and Dr. Riley to ensure that we're on the same page and that we're taking a collaborative approach to problem-solving. We will also be communicating regularly to ensure that everyone is aware of the challenges and the plan to overcome them.

Q: What is the next step for the team?

A: The next step for the team is to meet with Zach and begin working on the physical component on Friday, 3/14. We will also start looking into CLI tool building, specifically using Python and evaluating the argparse and click libraries.

Q: How will the team ensure that they are on track to meet their goals?

A: To ensure that we are on track to meet our goals, we will be regularly reviewing our progress and adjusting our roadmap as needed. We will also be communicating regularly with Zach and Dr. Riley to ensure that we're on the same page and that we're taking a collaborative approach to problem-solving.

Q: What is the expected outcome of Sprint 3?

A: The expected outcome of Sprint 3 is to have a functional CLI Tool and to make significant progress on the physical component. We will also have a better understanding of the challenges and opportunities associated with our project.

Q: How will the team measure the success of Sprint 3?

A: We will measure the success of Sprint 3 by tracking our progress and evaluating the quality of our deliverables. We will also be gathering feedback from Zach and Dr. Riley to ensure that we're meeting their expectations and that we're on track to deliver a successful project.