Skip to content
Alexander Mathieu edited this page Jul 1, 2019 · 1 revision

Project: Brownfield of Dreams

Group Member Names: Alexander Mathieu, Brennan Ayers, Brian Plantico

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?): Alexander - Individual - Learn best practices to consume an API, working with an existing codebase. Team - Goal to finish the project and learn while adhering to good version control/workflow. Measure success based on project completion. Brennan - Individual - Oauth. Team goal to AT LEAST complete base fucntionality well, then worry about extensions. Brian - Individual - Testing, consuming an API. Team goal - Base functionality that is polished at least, extensions if we have time.

Team strengths & collaboration styles (consider discussing your Pairin qualities here): Brennan has prior experience with API's, including some indirect testing of API returns. We're all open to getting the set up done together and then can be more flexible about working together vs solo.

How we can use our strengths to overcome obstacles:

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Hard cut off at 7:00pm to leave Turing so we're not here really late, otherwise we're all open and felxible for working after school. 4th of July we are planning to take off.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Slack and face-to-face. Slack group is already set up for the project. Mobile phones as a last resort if needed.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Brian - Abilities: AR/SQL, process. Growth Expectations: Testing, refactoring Brennan - Abilities: exposure to stubs/doubles/spies but do want more experience with these ( a true understanding). Alex - Abilities: "When you get it, don't forget to .take it.", AR, testing, process. Growth Expectations: Writing more flexible code (more inheritance, optional arguments for queries so code is DRY).

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Locked master branch on Github that requires one code review with comments. HoundCI ConveyorBelt Pry

Expectations for giving and receiving feedback: Kind, actionable, specific feedback which keeps intent/impact in mind. DIRECT but kind.

Project management tools we will use: GithubProjects Daily standup after class/before starting project worst.

Day 1 Agenda: DTR Deploy to Heroku Install HoundCI Diagram DB

Additional Notes: Re-DTR on Wednesday PM

Clone this wiki locally