Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

I. Context, data, and highlights 🏅

II. Successes and achievements 🏅

III. We should keep ✅

  • [Jenna]: Propose that we keep Product ownership of the “master” test spreadsheet, and continue to flesh out regression tests

  • [Jenna]: Propose that we keep the monthly meeting to track features slated for Sumac (can start again in August

IV. What didn’t we do so well, and what could we have done to do better ❌

  • [Jenna]: How can we tighten the lead time between the code cutoff and having the testing sandboxes ready? For Redwood, there was about a week in between. How can product help in defining which features should be enabled, etc?

  • [Jenna]: Only having 3 weeks for testing ended up feeling tight. What what would it look like to try a 6 week testing period between code cut and release, especially if we can shorten the lead time on the sandboxes?

  • [Jenna]: Redwood was feature-packed. How can we scale back and still have a meaningful set of capabilities/features in Sumac, without over-committing?

VI. Action Items for Sumac release 📈

  • No labels