April 12, 2019
- The team met at 11:00 AM to discuss our project plan
- Erin (our SCRUM master) went over what she'd recently learned about using the built-in Github projects kanban board; how assigning tasks works, how we might connect them to different repos, etc.
- Erin shared a great template for our team communication plan that some of her previous Code Fellows project teams had used
- We discussed each area in this template together and agreed on what to include in the formal plan. Areas discussed included the following:
- basic info about our role on the team, contact information, and our availability.
- general communication goals
- a conflict plan
- naming conventions / file structures
- project management tools
- a git workflow plan - we're following a strict git workflow
- Our team also completed the daily lab assignment together. It involved deploying three separate repositories of a message queue application to different hosting service providers.
- Our API server was deployed with Heroku
- Our queue server was deployed with AWS
- Our logger was deployed with Azure
- We were able to get each of these pieces to connect and communicate with one another properly. It was good practice for how we'll deploy our midterm project—SlackLackey—and a chance to become familiar with the different developer consoles in each service.
A UML diagram for our deployment lab
