| Branch | Build |
|---|---|
| main |  |
Starter code for the Contemporary Software Development CA2
This is the online repository for the Contemporary software development Assignment 2 - 2021/22.
Week 1: Oisin Keeney - okeeney.. +
- Oisin Keeney - okeeney
- Daniel Moffatt - Daniel-Moffatt-LYIT
- Ronan Farrell - ronanj2
- Emeka Okereke - L00170359@student.lyit.ie
- David Curtin - David-Curtin
- Anish Kanhai - [Gopaal108] (https://github.com/Gopaal108)
Friday 25th of February 2022 at 22:00.
Weekly team meetings will occur every Monday online at 20:30 UTC or after CSD class using Microsoft Teams.
The order that people give their updates will be based on alphabetical order of those present at the meeting.
Updates will be in the form: What I've done, Impediments, What I plan to do.
Please add and update items within the project board prior to each meeting.
Points raised during the meetings will be noted and posted on the MS Teams channel by the product owner that week.
Come prepared to meetings.
Be on time for any scheduled other meetings.
Everyone has equal voice and valuable contribution.
Keep your language and tone professional at all times.
Be honest and respectful.
MS Teams is the preferred method of communication.
Communication in this order: MS Teams and email.
MS Teams communications anytime but reply is not expected late nights and early mornings.
Raise a problem as soon as you see it.
Respect each other and understand differences in knowledge.
There are no silly questions, if you don’t understand, ask.
Share success stories.
Focus on the positives.
Don’t make assumptions.
Don’t interrupt and cut another person off while they are talking.
Listen when someone is talking, don’t interject.
Zero tolerance for bullying.
Demonstrate agility at all times.
If are assigned a job, take ownership of it and keep it up to date.
Stick to your agreed working patterns. Let the team know when you are going to be late or early.
Keep the GitHub Project board updated at all times.
Don't be afraid to ask team members for help.
Don't be afraid to give constructive criticism, as long as it is constructive.
Solve roadblocks within the team. If the impediment can’t be solved within the team bring it to the attention of the module coordinator.
- Complies with Google's Java coding style guide.
- Free from compiler warnings or errors.
- Analysed using relevant code analysis tools.
- Tested prior to commit.
- Minimum of 1 reviewer.
- Merged into main.
- Correct, comprehensive and consistent.
- Reviewed, followed and executed by Reviewer.