-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Contributing towards the delivery of a data-processing software that receives data from 16 electrodes and produces a 2D visualization. This will be done using Python and numerous Python libraries along with mathematical algorithms to translate the data to a visualization. Following Agile methodology and recognized design processes, and utilizing the GitLab DevOps platform to improve workflow via branching and CI/CD pipeline.
Communication Method:
- Microsoft Teams
Over our project, we have developed a schedule that we believe improves our productivity. This has been developed as a result of our retrospectives.
| Time | Purpose |
|---|---|
| 10am | Meet to discuss progress and next steps. Also, decide what we would like to do in the afternoon. |
| 1pm | Work on what we decided we wanted to do in the afternoon (pair programming, code reviews, discussion with coach etc.) |
| 4pm | Check in with each other if we are not in a meeting to see how everyone got on. |
Note: Other unscheduled tasks such as Code reviews and pair programming sessions can also take place throughout the week on a required basis. This also applies to urgent meetings and meetings with the customer or the coach.
During the course of a sprint, there are times where we may need to arrange a meeting to progress with the project this includes communicating with the coach, the customer, and of course additional internal group meetings. These can be found in this section.
View Standup Meetings
📅 Stand Up Meeting 1 "9/11/2021"
📅 Stand Up Meeting 2 "18/11/2021"
📅 Stand Up Meeting 3 "14/01/2022"
📅 Stand Up Meeting 4 "24/01/2022"
This section contains our customer meetings which take place at the end of each sprint(Customer Days). These are attended by our team, our customers, and a marker from the University of Glasgow.
Customer Meetings
🙇 Customer Meeting 0
🙇 November Customer Day
🙇 December-Customer-Day
🙇 January-Customer-Day
🙇 February-Customer-Day
🙇 Final-Customer-Day
Requirments
Retrospectives
🔍 Retrospective 1
🔍 Retrospective 2
🔍 Retrospective 3
🔍 Retrospective 4
Pair programming is an important technique for developing higher quality code, faster while also reducing risk and spreading knowledge. We have found it very useful in our project.
Note: All pairwise programming sessions occurred through a Microsoft Teams private chat which was highly flexible and easier for us to use due to the high volume of messages
View Paired Programming
Code Reviews are the act of consciously and systematically convening with one's fellow programmers to check each other's code for mistakes, and have been repeatedly shown to accelerate and streamline the process of software development. This was a solid strategy used by the group to successfully come up with a working solution of the eit algorithm.
Note: All code review sessions occurred through a Microsoft Teams private chat which was highly flexible and easier for us to use due to the high volume of messages
View Code Reviews
:track_previous: Code review session 1
:track_previous: Code review session 2
View Issue Trackers
View SCM Systems
View Change Management Strategy
View Handover Strategy
📑 Handover Strategy
🏷️ Handover Licensing
🛂 Documentation & Demo
Data Input
Customer Meetings Powerpoint slides
Emails
📧 Emails