Skip to content

6. Sprint Summary Sustain Quality Spring September 11 to 15

Jump to bottom
kathreenriel edited this page Nov 20, 2017 · 1 revision

The theme for this week's Sustain Quality Sprint included three areas

  • Sustain Quality Code
  • Sustain Quality User Experience
  • Sustain Quality Evaluation

There were 16 tasks associated with this Sprint.

Retrospective: Friday September 15

Brad: Expressed positive perspective about the week's sprint particularly with 2 plugins that can not only be used for this project and shared with others but also for potentially useful for other projects as well.

Challenges: Some tasks took a little longer than usual. Clarification needed as to whether stop after prescribed amount of time. Kathreen recommended the priority to finish the task and if need be reduce the Sprint backlog.

Alex: Also positive about "locking down" two plugins.

Challenges: Working on organization of stylesheets and javascript files and wondering if there is a 'better' system. Saw that the scope creep of export plugin took up more time.

Paula: Sprint went well. Would like to see Location export added as an issue for future Sprints

Kathreen:

REALLY appreciates the team working through sprint issues even with when presented with a multitude of unexpected variables.

Concurred with expressed achievements of both plugins not only providing more functionality but also increasing engagement of the advisory group and general users to use the early years site with more informed intention.

Challenges: Would like to see sprint tasks that affect user experience (such as #224) as a priority for completion in future sprints.

Clint: Agreed with Kathreen about the willingness of team to work through issues that reveal complexity. Appreciates the opportunity to observe the process.

Items in Done Column will go Live Monday morning: 9:00 am

Future Considerations:

  • Messing with the Media Manager has implications! Consider parameters/technical debt for any future modifications related to the Media Manager.
  • For tasks that go longer than planned let Kathreen know so that decision can be made to reduce Sprint task items if necessary.
  • Look at User export data to ensure it follows privacy regulations.
  • Identify pattern for why drafts are being (or were) created.
Clone this wiki locally