-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Planning v1 #111
Comments
Meeting November 27, 2022We discussed that status of the product by means of the investigation @lvanvugt and record it in #114. In this we focussed on the bugs. These will be our first focus (from top to bottom). StatusBugs
GoalWe are targetting to get these fixed before 31st of January 2023. After that we are going to pick up the in-scope enhancements. Next meetingDecember 8, 2022, 08:00. |
Meeting December 22, 2022
StatusSolved
Needs testing
Open (bugs)NewGoalWe are still targetting to get these fixed before 31st of January 2023. After that we are going to pick up the in-scope enhancements. Test automation@DavidFeldhoff and @lvanvugt will sit down on January 18, 2023 (17:00) to discuss what ATDD tests could be implemented as backend tests. Next meetingJanuary |
After a very long period of silence today we had a re-kickoff call with @martonsagi, @DavidFeldhoff and @lvanvugt. Goal was to brainstorm on where we (think we) are and where we want to move to.
Based on the brain varts of each we have come to the following "plan":
Next
To determine what is needed to get v1 completed we will have a demo session on November 27, 2022, 10AM.
At the end of this session a pair-programming session will be planned by @martonsagi and @DavidFeldhoff
Focus:
Note
With this we close the beta phase #22.
The text was updated successfully, but these errors were encountered: