1. Retrospect Meeting April 21 Sprint Personalized and Clarifying Functionality: April 18 21
Review of Sprint: Summary of Goals for Next Sprint: April 24 - 28
- Break down larger sprint tasks into smaller tasks
- Create more product tasks when further revisions to content, links or 'clean up' is needed
- Consider time for review of code when alloting time for tasks
- Clarify Validation work to be done and by whom
Notes:
Alex: It would be good if the larger Sprint tasks were broken down into smaller tasks Remember to self assign tasks. Helpful if consistent vocabularly is used eg. modal and lightbox.
Paula
- What do we do about items in the task that require further work eg. links that need to be updated etc.
- Reviewed content. How do we support/maintain the quality of the content.
Answers:
- Determine whether it's a code task or content task Create a new ticket in the Sprint (if is related to the ongoing Sprint task)
- Determine the priority of the revision based on the purpose and context of the content. Add a task to the product backlog if necessary.
Brad
Some tasks were overestimated but this left time for development and review of other tasks. Important that the review process be considered/given time so that both Alex and Brad can review the code. Process seems fluid.
Kathreen
The Sprint week was a great success. Lots of work completed in 4 days! Will work on the Validation phase so that Paula is more informed when tasks are to be reviewed. Will work on communicating what validating work has been done and self assign tasks where necessary.