Build and Documentation

Manual

Protocol for Agile Meetings: Group ASD-Morning-4

---

Planning Meeting: Sprint 1

ASD: Morning 4 - Meeting #1

• Date: 18.03.2020
• Time: 08:00 - 10:30
• Type of meeting: Planning, Setup Github Workflow, Label Issues/Sprints
• Attendees: All
• Tools used to conduct the meeting: WhatsApp, Slack and Teamspeak

Purpose

• Discussed the tools we’ll use for remote work.
• Discussed the technology to use for the project.
• Development environment setup for every colleague.
• Planning: Labeling and rating all issues and assigning issues for Sprint 1.

Meeting Protocol

We decided to use the following software/tools:

• Teamspeak for Voice Calls
• WhatsApp, Slack and Teamspeak chat for messaging
• Teamviewer for Pair Programming.
• Java Spring Boot with Thymeleaf, Hibernate and MySQL.

Commitment

• Everyone did a test commit to ensure the workflow is guaranteed and working.

---

Sprint 1 Work Progress Meeting

ASD Morning 4 - Meeting #2

• Date: 25.03.2020
• Time: 08:00 - 09:00
• Type of meeting: Planning
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• Helping Teammates with the Framework.
• Setting up the Framework for every colleague who had issues.
• Creating the user stories and setting the goals for Issues.

Meeting protocol

Troubleshooting

• Solving common problem with SQL and Springboot.

• Setting as maven build after pulling.

• MySQL: Timezone-problem.

Planning

• Setting goals for Sprint 2

• Issues 003 - 007

• Organizing pair-programming Teams

• Teamviewer is used for this point

• Started implementing next issues

• Unit Tests.

Clarification

• Discussion about Issues.

• How to rate issues accordingly?

• Which issues are related to one and another?

• Discussion about using branches per issues and git workflow.

Commitment

• First Prototype implemented, issues closed: LANG_000, LANG_001, LANG_002

---

Sprint 1 Review Meeting

ASD Morning 4 - Meeting #3

• Date: 01.04.2020
• Time: 08:00 - 09:50
• Type of meeting: Sprint Review, The Retrospective
• Attendees: All
• Tools used to conduct the meeting: Teamspeak, Teamviewer

Purpose

• Asking Questions:

  • What is TODO in next Sprint?
  • Are we in time?
  • What to Improve?

• Recap of last Sprint

• Did the Group communicate enough? (especially given the circumstances of COVID) Meeting Protocol

@Issue 000 Development environment is working fine and we think we made a great choice with the technology (Spring Boot, Thymeleaf, Hibernate, Bootstrap, MySQL).

@Issue 001 Database is also running. We can start to implement next Issues (since we are ahead of time):

• things that go well according to all members:

  • all closed issues are working well
  • Framework is perfect for our implementation

• things to improve:

  • focus more on branches
  • focus more on the agile workflow
  • pay attention to naming conventions in GitHub
  • pay attention to the "coding standard"

Also:

• code should be easy to read
• use more comments on parts that are not obvious.

Agreed deadline for Sprint 2: 29.04.2020 11:00

Designated Pair Programming Groups:

• Unit Testing Hieß & Wartinger
• LANG_003 Loitzenbauer & Ranftl
• LANG_004 Prüll & Weinhandl
• LANG_005 Beinhunder & Prüll
• LANG_006 (open)
• LANG_007 Felgitscher & Weinhandl

Commitment

• Sprint 1 was released.
• Added LANG_004 implementation of Study Interface.

---

 

Planning Meeting: Sprint 2

ASD Morning 4 - Meeting #4

Date: 22.04.2020 Time: 08:00 - 11:00 Type of meeting: Daily Meeting, Code Review Attendees: All Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• Discussions Updates.
• How far are the Issues implemented?
• Does anyone need help?
• Starting to use Code reviews.
• Discussing Feedback

Meeting Protocol

• The Pair programming worked out fine.
• Issues are almost done.
• No one needs help for now.
• Always Codereview asynchrone for pull requests. (Person not part of the Pair-Programming team)
• Synchronous reviews are done with Pair-Programming.
• After every Sprint, critical parts of the Code will be reviewed with the Once-In-A-While code review method.
• Weinhandl did the first Once-In-A-While code review for the last sprint in retrospective. Taking Feedback from Tutors into account. More focus on agile events and practices!

Commitment

• Added Junit and Mockito Tests.

---

Review Meeting: Sprint 2

ASD Morning 4 - Meeting #5

• Review Meeting : Sprint 2
• ASD Morning 4 - Meeting #4
• Date: 29.04.2020
• Time: 11:30 - 12:00
• Type of meeting: Review Meeting
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

###Purpose

• Help wanted?
• How far are the Issues implemented?
• Are there critical bugs?
• Ideas for better interaction.

###Meeting Protocol

• Only minor issues are present.
• Most Issues are finished.
• No bugs, we know of yet.
• One minor (size 5) Issue was not completed.
• This gets bigger priority next Sprint
• Interaction is not highest priority as of now.
• Code Documentation needs to be updated!
• Commitment
• Closed all Issues that we worked on in Sprint 2

---

Planning Meeting: Sprint 3

ASD Morning 4 - Meeting #6

• Date: 06.05.2020
• Time: 08:00 - 08:45
• Type of meeting: Planning Game
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• Forming new Pair Programming Groups
• Declare Issue size
• distribute Issues
• Assign Sprint
• Planning ahead for future Sessions

Meeting Protocol

• New Ping-Pong Groups are formed.
  • Kristiana + Christoph
  • Alex + Simon
  • Jan + Andi
  • Sophie + Carina
• Issue sizes changed
• Testing mode got High Priority duo to Issue 8 and 9
• UnitTesting needs updates!

Commitment

• Hotfix for ds store!

• Updating some documentation!

• Starting to code Issues.

Daily Standup : Sprint 3

ASD Morning 4 - Meeting #7

• Date: 13.05.2020
• Time: 08:00 - 08:45
• Type of meeting: Daily Standup
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpos

• Forming some Pair Programming Groups
• Sync Team about Issues
• Help needed?

Meeting Protocol

• New Ping-Pong Groups are formed.
  • Kristiana + Carina
  • Sophie + Christoph
• UnitTesting, How, When, What!
• Who did What, where am I?:
  • Andreas + Jan Implementing Unittests
  • Alex + Simon Working on issue 10
  • Last Week:
    • Kristiana + Christoph -> Rating
    • Sophie + Carina -> Testing mode
• How to handle CSV Export and Import

Commitment

Keep coding Issues

Daily Standup : Sprint 3

ASD Morning 4 - Meeting #8

• Date: 20.05.2020
• Time: 08:00 - 08:30
• Type of meeting: Daily Standup
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpos

• How far are the Issues implemented?
• Discussion about further ToDos
• Help needed?
• Fixing Bugs

Meeting Protocol

• Still working on issues
• Implement some usability.
• Need to split Testing mode.
• Backup is split up in two separate issues -> CSV Export and Import

Commitment

Keep coding Issues

Review Meeting : Sprint 3

ASD Morning 4 - Meeting #9

• Date: 20.05.2020
• Time: 11:30 - 12:00
• Type of meeting: Daily Standup
• Attendees: Felgitsch, Hiess, Loitzenbauer, Prüll, Wartinger, Weinhandl
• Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• Help wanted?
• How far are the Issues implemented?
• Are there critical bugs?
• Ideas for better interaction.

Meeting Protocol

• Closed issues in sprint 3: Rating, Export vocabulary, Change interface language A, Interface-navbar, Testing mode A.
• Testing mode split into two issues
• UI implementation needs some updates.
• Edit vocabulary deletes Tag -> needs a fix
• More documentation in the code needed !!!!!
• Do not refactor code lightly.

Commitment

• Closed all Issues that we worked on in Sprint 3

Planing Meeting : Sprint 4

ASD Morning 4 - Meeting #10

• Date: 27.05.2020
• Time: 08:00 - 08:40
• Type of meeting: Planning Meeting
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• How far are the Issues implemented?
• Discussion which features are almost finished
• Speak about problems, errors or obstacles
• Prioritize issues that must be implemented

Meeting Protocol

• Most issues are finished
• We have set the "testing mode_b" to “size 40”.
• We have assigned a lower priority of "size 0" to the share function (LANG_011 Share).
• Due to a lack of time and technical difficulties, this feature cannot be implemented as of now. The basics are already done though.
• The focus of the fourth sprint is also on finalizing the unit tests.

Commitment

Closed all Issues that we worked on in Sprint 4.

Morning Meeting : Sprint 4

ASD Morning 4 - Meeting #11

• Date: 03.06.2020
• Time: 08:00 - 08:30
• Type of meeting: Daily Standup
• Attendees: All
• Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• Organizational matters (presentations)
• Prioritization of the remaining user stories
• Writing a final release document
• Concluding meetings
• Discussion which features can be finished for the last release
• Speak about problems, errors or obstacles
• Prioritize issues that can be done today
• What about Testing?

Meeting Protocol

• We agreed on a timeslot for the presentations.
• In our last meeting we discussed together in the team which last features could still be implemented.
• We have therefore prioritized the product backlog again due to time constraints. A missing feature (the boundary tests) could be inserted for basic methods.
• It is also necessary to continue working on the testing mode.
• Finally, further unit tests can be implemented for the CSV writer.
• Testing Mode still needs rework. Probably won’t be done at the end of the sprint
• Testing Mode would get database implementation.
• Language change will be finished for this Sprint
• Adding some tests today.

Commitment

Implement the most important features to complete the project.

Review Meeting : Sprint 4

ASD Morning 4 - Meeting #12

• Date: 03.06.2020
• Time: 11:00 - 12:00
• Type of meeting: Sprint review Meeting
• Attendees: All *Tools used to conduct the meeting: Slack and Teamspeak

Purpose

• What is finally implemented?
• What did not work as planned?
• How can we improve?
• Can we communicate better?

Meeting Protocol

• Most important features are implemented.
• Sadly Testing Mode is still in a beta Phase. Not enough time on our hands.
• Couldn’t finish all Issues
• Learning more “theory” outside of Coding-Blocks
• Communication felt good. Usually everyone was in picture of the process.

Commitment

Finishing Files for Sprint 4