-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint and Scrum Logs
Katriona Angel, Adam Ashford, Marc Chapman, David Calloway, Dary Conway, Chelsey Cox, Ryan Wooton.
- Research into projects carried out; rapidjson selected.
- Roles set – programmers: Marc and Kat, testers: Adam, David and Daryl, designers: Chelsey and Ryan. 1st sprint scrum master: Kat.
- Sprint sessions – 2 hours Monday 9-11am, 2 hours Tues/Weds ad-hoc.
- Tools set up – Slack for out of hours’ communications and Trello for recording stories.
- Rough burn chart created. Story point system 100 points = approx. 1 hour worth of work. Story points assigned to issues on Trello.
- Sprints – 1 week long, can extend to 2 weeks in case of schedule slip. 6x1 week sprints or 3x2 week sprints.
(extended edit: Marc)
It was discussed briefly, that since the group entered into the project at a midpoint (Established and fully functional product, with bugs and extensibility requests as github issues) it would be best if issues were selected that could be started on by all role-groups (design, test, dev). These should merge into correct workflow from Iteration 2-3 so that the process flow passes from one roe to the next as expected.
Scrum Master
- Week 1 - Kat
- Week 2 - Marc
- Week 3 - Ryan
- Week 4 -
- Week 5 -
- Week 6 -
- Programmers – issues 849 and any other progress on issues selected for this sprint.
- Testers – testing story for 849 and other rapidjson issues.
- Designers – UML and use cases for listed enhancements within the system.
- Current blockers – understanding the code, understanding role requirements. Discuss overlapping roles with John Murray in future/via email?
- Carry on work on assigned issues outside of class. Converse with ‘partners’ via Slack and update story points/issue cards on Trello. Report completed issues so the burndown chart can be updated.
- Programmers
- Done: Issue #849.
- Todo: Issues #798 #825 #852
- Testers
- Done: Test Case for #849.
- Todo: Test Fix for #849.
- Designers
- Done: #810, #671.
- Todo #836.
- Blocks
- Ongoing unfamiliarity with a complex codebase.
- No specified Product Owner.
- Testers are currently uncoordinated
- Lack of current iteration markers in trello.
- Programmers
- Done: ( ).
- Todo: Issues #798 #825 #852
- Testers
- Done: Test Fix for #849.
- Todo: Test Cases for #798, #825, #852
- Designers
- Done: ( ).
- Todo #836.
- Blocks
- Ongoing unfamiliarity with a complex codebase.
- Blocks Fixed
- No specified Product Owner
(Marc has arbitrarily taken ownership until objections are logged) - Testers are currently uncoordinated
(In an attempt to stop Daryl stealing all the work for himself, he has been given delegation responsibilities by the current overlord) - Lack of current iteration markers in trello.
(Fixed, also better trello working practice improved overall workflow understanding cross team)
- No specified Product Owner
NOTE: Internet access was down during the day of the sprint, severely hindering progress, also one of the testers (David) was absent due to health issues.
What has been done: Completed task given last week and uploaded the designs. What is being done today: Look at tasks that needs doing and assign tasks to each other, create UML graphs. What is to be done during the week: Continue with the above.
What has been done: Issue #798 shelved due to potential complexity of a fix. Issue #917 fixed and documented on issue page on GitHub. What is being done today: Re-reading the code to better understand it, continue with working on solutions for other tasks. What is to be done during the week: Continue working on other tasks, if the task is completed begin work on a new task.
What has been done: Everything they were tasked with doing. What is being done today: Nothing, as the aforementioned lack of internet access means they cannot access the program to formulate tests. What is to be done during the week: Additional review work to account for the work that could not be done today.