Bugfest - Lotus - Retro

Owned by Dilshod_Khusanov
Last updated: May 20, 2022

Below is a list of Lotus Bugfest items that Kitfox identified during a retro session.

Went bad

  1. need to improve the org. process
  2. Kitfox was responsible to triaging BF tickets which was not very appropriate.
  3. missing steps in Bugfest Action Plan
  4. Unclear state of fixing fse-create-tenant-backend Jenkins job
  5. module releases very late
  6. poorly tested modules spoiled and delayed the env. readiness
  7. Bugfest snapshot contains inconsistent data which had to be fixed manually
  8. insufficient resources for some modules
  9. Insufficient rights of POs and other stakeholders to access bugfest logs and monitoring metrics
  10. POs were bouncing tickets back to Kitfox without much clarification of the issue
  11. Lack of automation tools on Bugfest management
  12. too optimistic deadlines in Bugfest action plan
  13. Kitfox had to overtime in order to meet the deadlines
  14. Heterogeneous env. on Bugfest and community
  15. Communication issues


Went Well

  1. BF - finished BF issues
  2. Started Bugfest on time
  3. All stakeholders were ready to support the activity and spent enough time to resolve the issue


To Improve

  1. Set up a KT among teams before the start


Action Items

  1. Create KT pages in Confluence