Content Comparison

...

What went well? What should we continue to do?

• Bugs were quickly identified by QA and addressed by Dev team

• Quick UAT Feedback from George and team

• Stories were well organized and cleanly separated

  • Developers helped lead this conversation & communication

• Labeling helped to identify all issues related to work

YSB: Close all 4.2 tasks -

Status
colour Green title Complete

...

What went well? What should we continue to do?

• Communication and team meetings

• Raising a hand when issues are taking longer than expected

• UAT Documentation sent on time

FRMS: 3.0 Release-

Status
colour Green title Complete

...

What went well? What should we continue to do?

FAS: Ingest Release 1/16 -

Status
colour Green title Complete

...

• Taking advantage of asynchronous development opportunities

• Work was able to be completed ahead of schedule because of communication between developers

• Clear goals around allocation and prioritization

Lesson Learned:

• Ask more questions in refinement about specifics in implementation

  • Example: “Search all text” - is this grant entity only, or all entities?

  • Took several iterations to find desired functionality

Question: When is the right time to ask more questions about implementation?

Backlog refinement is the designated time to really dig into ticket language, acceptance criteria, sub tasks, approach, etc and ensure the team is on the same page.

Also: Don’t worry about pinging Kim if she’s not in the meeting - she holds Refinement time for questions.

FAS: Ingest Release 1/16 -

Status
colour Green title Complete

What went well? What should we continue to do?

CEA: Finish Print View -

Status
colour Red title INCOMPLETE

...

CUS-14899 - PDF Export Truncating data -

Jira Legacy
server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-14899

Closed, work continued on other tasks.

...

Dev Subtask

...

Planned

...

Actual

...

• Documentation provided by Kim helped Dev to arrive at correct solution

  • Ex “Like”, “Contains”

• Communication with the Client - getting formal signoff on all factors

• Providing detailed diagrams to client helped us arrive at proper solution

• Endpoint access for Kim significantly sped up process and improved communication

• Nico is a very helpful and responsive colleague (thumbs up)

Lessons Learned

• Client may not use vocabulary and nomenclature used internally

• Communicating and understanding the WHY with the client.

• Involve other technical collaborators during initial planning phase, specifically around system architecture

  • IE, Data Services

• Versioning must be a part of all development moving forward to help with individual deployments

• Impromptu deployments need to be documented, go through the change process, and signed off on internally before communicated to the client.

Possible Jira Enhancement

• Add mandatory check box for code review tickets that reflect documented standards

  • OutSystems vs. Web Development

CEA: Finish Print View -

Status
colour Red title INCOMPLETE

...

What can we do better next time?

• Developers use Mac, Testers use Windows (Edge)

• Issue is system and browser dependent

  • Code review can include review across browsers

• QA and Dev could include system/browser specifics in bugs/defects

• More in depth acceptance criteria could help limit defects/enhance code review

• Browser Stack for testing cannot allow for downloaded Mac files

• Screen size and standard screen resolutions must be standardized & documented for testing and Devs

• Team needs to document standards and practices around PDFs

• Is there a point at which we have spent “enough” time on bugs or defects?

• Team needs additional accessibility training and collaboration with Accessibility team

• Accessibility planning should be part of planning from the initial development

• Inheriting applications will cause additional defects and bugs because they do not meet our initial team standards

  • PDFs, Accessibility, Visual Design

SDF: Close all Maintenance Tasks-

Status
colour Red title INCOMPLETE

...

What can we do better next time?we do better next time?

• Need to be prioritized appropriately

• How can we make it clear who “owns” a ticket in its current state?

• QA Analysis missing on certain tasks

FMP: FMS Med3 Upgraded -

Status
colour Green title Complete

...

What went well? What should we continue to do?

• Making stories smaller that have tasks that can be finished

• Lots of prep work for the work ahead of time led to success

Issues In To-Do

What happened?

• How do we know what should be removed from the sprint?

• Should we have deadlines for specific tasks?

  • If things haven’t been stated by X date, should they be removed?

• All team members are responsible for looking at these tasks & bringing them up

Key Takeaways to improve team accountability:

• Goals and tickets are a team commitment