Project:
Teacher Achievements
Group Member Names:
- Chris Basham (BE Role)
- Eric Meldrum (FE Role)
- Lacy Rudd (FE Role)
- Tyler Schaffer (BE Role)
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
- Chris: Main goal is to gain confidence in ability to pick a new language, learn it, and implement it in 2 weeks. (Python is language of choice)
- Eric: Quality product that is polished for resume.
- Lacy: Demo comp. Tight MVP -- clean workflow. Scalable processes.
- Tyler: Python on resume. Capstone project that I can be proud of.
How we can use our strengths to overcome obstacle(s):
- Chris: Jack of all trades, master of none. Ternaries. Strength is overcoming obstacles. If I say I will do something, it will be done.
- Eric: Flexibility, Jack of all trades, master of none. Leader or step back. Ideas.
- Lacy: Communication. Designs. UI/UX.
- Tyler: Attention to detail. Format consistancy, no minor errors, edge cases.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- ALL: NO EXPECTATION OVER THE HOLIDAYS. // But online communication loosely open for PRs. // ride your own struggle bus
- Chris: Colorado Springs so preference to work remote, ok on slack with paired. Prefer to divide and conquer. Develop questions. (VA appointment every Tuesday) Leave early to beat traffic
- Eric: Colorado Springs, commute some days -- not every day -- remote work. Like to pair until clear goals are in sight, and then divide and conquer. Prefer working from home or remote. NOT TURING. (Gone next wednesday) Leave early to beat traffic
- Lacy: In person /out of turing/ , remote okay with communication, prefer to front load heavily. (2 weeks in Texas). (mentor meeting Sundays at 1pm)
- Tyler: Rather have time to think through things on my own, then come back together.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Group: Slack channel for team stuff, but github for code, daily standup for goals, and standup for end of day -- goals reached.
Abilities & Growth Expectations (Stretch Goals):
- BE: Python, Django, AWS -maybe-
- FE: Vue / typescript (still debating, not set in stone)
Workload Expectations (What features do we each want to work on?):
( will update when mvp is more defined )
- Chris: BE
- Eric: FE
- Lacy: FE / design / wireframes /
- Tyler: BE
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Overall team dependent, PR template, Travic CI, user-story based tickets, updating tickets as we go.
Expectations for giving and receiving feedback:
Open, honest, direct, specific - ACTIONABLE - kind
Project management tools we will use (GitHub projects or Github projects are popular tools):
Github Projects
Day 1 Agenda:
- DTR
- Define MVP
Additional Notes:
- Learn frameworks
- Draft User Stories
- Project Board
- Draft designs
- 11 am Sunday for remote call --
- Execution planning