Date/Location: 21-April-2020 at 4:30 in Collaborate Ultra

Information Updates/Reminders

• Last week was about converting and documenting the code
• This week we will use a DAD process over two weeks to fix bugs and extend the project. (No bug fixing or extensions yet!)
• Help from an external consultant can be provided to help get the code converted and working if that was not done. (Ask our tutor.)
• Everyone should have used toggl.com to track their time last week. Also track time on tasks this week with Toggl.
• Tutor must be added to GitHub and Trello.
• Slack will be used to show the changes in the Trello board during the iteration

General Items

• The Trello board needs to be updated ready for the planned iteration. In particular columns for project backlog and iteration backlog will be needed.
• Create and link the team slack so that we can be notified and have a nice record of the Trello updates.
• The project backlog needs to be created and gets the product owner’s approval. Use the existing bugs and features we have documented, and convert to the required format. The project backlog has to be entered into Trello (today).
• Project backlog tasks need to be prioritised and their time estimated. (Today)
• The new iteration backlog needs to be pre-selected ready for discussion and approval with the product owner. (Today)
• Once the iteration has started, hold a daily stand-up. (Can happen today or during the week)

Product review.

o What has the team accomplished in terms of code conversion, build and run? Our team has been able to successfully convert from VB to C#, build and run the new version of battleships so we can begin working on fixing bugs and adding new features.

o What has the team accomplished in terms of code analysis and documentation? We analysed all code files within the original program and created a summary of them all so we can further understand what they do and reference them anytime we need. We also checked the files for preexisting documentation, we found they were already very heavily documented and we did not need to add any extra.

o Have these achievements been discussed with and demonstrated to the product owner (tutor)? Yes

Process retrospective.

o What (process) worked well in the last iteration? All of our meetings and discussions that we had went very well and we were able to conduct meetings and a timely and professional manner.

o What could be improved in the next iteration? Using our time more wisely during the week when we are supposed to be finishing our tasks. A lot of tasks were pushed to the end of the week and done fairly quickly.

o Have these been discussed with the tutor and get their approval? Yes