-
Notifications
You must be signed in to change notification settings - Fork 1
Docs
Write a brief, one paragraph summary of the teams activities and accomplishments for the day. Remember to hit the "Save Page" at the bottom of this page when you are complete.
- Decisions:
- Concerns:
- Changes:
- Next Steps:
- Update provided by:
Updated daily log. Brainstormed other docs to do. Research possible awards to apply for.
- Decisions: Next week, there will be a progress report.
- Concerns: Submitted awards - FIRST Dean's List, Woodie Flower's Award, Entrepreneurship Award. Non-submitted awards - Industrial Design Award, Excellence in Engineering Award, Innovation in Control Award, Creativity Award.
- Changes:
- Next Steps: Finalize rest of design
- Update provided by: vickyjjj
Finalized some design aspects of robot.
- Decisions: Tank tread type chassis/drive. Piston shooter for high goal (by modifying low goal intake draft).
- Concerns: Finalize rest of design.
- Changes:
- Next Steps: Finalize rest of design
- Update provided by: vickyjjj
Continued to maintain the progress log.
- Decisions:
- Concerns: Need to include additional documents - e.g., robot design iterations.
- Changes:
- Next Steps:Continue to update and maintain documentation.
- Update provided by: mkobrin
Finalized the WIKI pages for the daily team updates. Six WIKI pages created (Hardware, Software, Field Elements, Documentation, Wiring and templates). Expectation is that a team member will edit the pages daily to provide a simple update. Updated the high level milestones on GitHub to align with the project timeline. Transcribed the daily team updates to date into GitBook for the formal team update.
- Decisions:
- Concerns:
- Changes:
- Next Steps: Ensure all team members have GitHub and Slack accounts. Train team members to provide daily documents.
- Update provided by:mkobrin
Determined the appropriate team tools for documenting the development process, tracking milestone and issues and team collaboration/communication. Initiated development of WIKI pages for daily team updates.
- Decisions: Github/Huboard will be used for tracking milestone and issues; Slacker will be used for team collaboration/communication and
- Concerns:
- Changes: N/A
- Next Steps: Train the team members on the tools and daily requirements
- Update provided by: Mkobrin