Sprint Goals

YSB 4.3 - Code complete, QA approved, ready for 3/6 release -

Discussion Questions

• YSB 4.3 Deployment - Test and Load Test vs. Prod events/information - how can we help make testing accurate moving forward.

• Solution - be aware of this difference as we test and build moving forward.

  • What happened?

    • There were no alerts in production, while there were alerts in Test and Load Test

  • What should we do in the future? How can we present this?

    • We could remove test data from the test environment to accommodate testing

      • This is a problem - UAT, training is performed on test.

  • Question: How difficult is it to refresh the test data?

    • This is not currently something that is built into the system

    • This would also impact training performed by George and Molly

    • We don’t want to normalize deleting - Databases aren’t built for deletion.

• Possible solution: Can we create a toggle to limit or change data shown?

  • URL with Passthrough? Toggle?

    • This will be complicated and will set up more variables and involve even more remediation

• If the version in test is the same in Load, they should work the same.

  • We will not have differences in code if the versions are the same.

    • Flag: How often are we doing hot fixes on higher environments and porting them backwards?

      • This is a rare occurrence (and doesn’t happen when we follow process).

Sheel’s Bug

• Slower internet might not load dates successfully when you are refreshing multiple times.

• This is a network issue, not a bug.

  • It’s a petition to the databse

Notable PvA Tasks

Test environment for PeopleService API didn’t work

• Right now, all instances are using the same URL across environments.

Finding good data to compare results against took time

• How can we identify when this is needed and help document it?

• This was done once and an issue was discovered

  • The issue had to be addressed and the build had to be re-deployed.

  • This is why the overages were focused on the research and building subtasks.

• This type of work is infrequent for our team.

• This was performed by Luis

• Typically, if there is a higher number in code review, it reflects the need for multiple reviews - IE, devs working back and forth to fix issues found during review.

Shout outs!

• Dev and QA for communication - the team knows for a fact this communication has eliminated defects and is feeling very confident in how work has been going these days

• Michael and Kristian - Great job working on maintenance across projects!

• Chris - Mentoring Sheel and the Yale developers in new processes.

• Jesus - We couldn’t do it without you!

• Chris, Kristian, Becki - Thank you for good communication and respect

• Team - this was a great sprint with a ton of completed goals! Great job everyone!

• Sheel - Great job with your high level contributions!

• QA - Thank you for working so hard being short staffed!

YSB 4.3 - Code complete, QA Approved, ready for 3/6 release

...