September data added

app.py

@@ -4,8 +4,7 @@ from pathlib import Path
 import gradio as gr
 from llama_index import VectorStoreIndex, StorageContext, download_loader, load_index_from_storage
 
-dataFiles = ["RetroAug", "RetroJune", "Mattel_06_23_Open_Gen", "mattel_06_23_gen", "OnCall", "RetroMay", "RetroApril", "RetroMarch", "Snowflake", "Datadog", "Databricks", "SplunkProducts",
-             "SplunkEnterprise"]
+dataFiles = ["RetroSep", "RetroAug", "RetroJune",  "OnCall", "RetroMay", "RetroApril", "RetroMarch"]
 
 cache = {}
 
@@ -68,7 +67,7 @@ loadData()
 iface = gr.Interface(fn=chatbot,
                      inputs=[
                          gr.Dropdown(dataFiles,
-                                     type="value", value="RetroAug", label="Select Pulse Data"),
+                                     type="value", value="RetroSep", label="Select Pulse Data"),
                          gr.Textbox(lines=7, label="Ask any question", placeholder='What is the summary?')],
                      outputs=gr.Textbox(lines=13, label="Response"),
                      title="NLP Demo for Chat Interface")

index_v2/RetroSep/docstore.json

@@ -0,0 +1 @@
+{"docstore/metadata": {"eadff1db-bc7f-4aff-b6a5-222c86754a4c": {"doc_hash": "1778b0dd95ac83138c079d085828924635f73e0ebcb527648185da3f38f6fc09"}, "9e32df02-1517-4364-bb5c-1f40b75ade5c": {"doc_hash": "15b9506f884218a64b16954b39557bbed395a4c50d98ddaf36680a168a913f36", "ref_doc_id": "eadff1db-bc7f-4aff-b6a5-222c86754a4c"}, "2447cc8c-ce73-4b77-8349-d31ce3f9fb14": {"doc_hash": "697489a25209505572af9638a7d67b43688e4c5fb1b5fdb7097392b41a2b7fb9", "ref_doc_id": "eadff1db-bc7f-4aff-b6a5-222c86754a4c"}, "9e41b425-af5c-4d8f-ac26-23a810864e37": {"doc_hash": "99c44c953b375a00831e913e01a9d7668749040b2fad872505923c515f521992", "ref_doc_id": "eadff1db-bc7f-4aff-b6a5-222c86754a4c"}, "d0e5b301-ffbb-49d6-8fe3-2b30eda93c38": {"doc_hash": "a866301dcbe301f1754b688359931c82f700c382496cf9f07f1006811d1f1a8e", "ref_doc_id": "eadff1db-bc7f-4aff-b6a5-222c86754a4c"}}, "docstore/data": {"9e32df02-1517-4364-bb5c-1f40b75ade5c": {"__data__": {"text": "<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Moderate\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Moderate\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Good\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., Thanks to UX team for all the detailed designs and covering almost all the possible scenarios. Makes life a lot easier while developing the feature.\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., nan\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., nan\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., In addition to excel that alex maintains, what we lack sometimes is a list of laundry list of items that PM is tracking for a release as sometimes the minor items could be under an epic but might be important\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., In earlier days, we used to maintain features on the Wiki page. We are using a spreadsheet, but this spreadsheet covers only some things. We need to maintain a master list of product features for each release. We need to include all user-facing features in this list. We need to make it available for everyone to update it. It will provide constant visibility and allow review until the release readiness meeting.\nPlease comment on requirement", "doc_id": "9e32df02-1517-4364-bb5c-1f40b75ade5c", "embedding": null, "doc_hash": "15b9506f884218a64b16954b39557bbed395a4c50d98ddaf36680a168a913f36", "extra_info": null, "node_info": {"start": 0, "end": 4069, "_node_type": "1"}, "relationships": {"1": "eadff1db-bc7f-4aff-b6a5-222c86754a4c", "3": "2447cc8c-ce73-4b77-8349-d31ce3f9fb14"}}, "__type__": "1"}, "2447cc8c-ce73-4b77-8349-d31ce3f9fb14": {"__data__": {"text": "visibility and allow review until the release readiness meeting.\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., nan\nPlease describe what went didn't go well in this release., Definitely some delays on my side in getting clarity wrt to Pulse Improvements, which might have made it into this release had I been more proactive\nPlease describe what went didn't go well in this release., nan\nPlease describe what went didn't go well in this release., nan\nPlease describe what went didn't go well in this release., It would have been nice if backend APIs were available for UI a little earlier, we could have had more time for Dev testing.\nPlease describe what went didn't go well in this release., Few bug fixes and features are not QA-Ready even after the branch cut is done\nPlease describe what went didn't go well in this release., 1. When there are many smaller items/enhancement (usually post a major feature release), sometime we are loosing track of what needs to be done.  \n2. Editing of UX post \"ready for dev\" also causes some confusion. Most of the time it is conveyed , but smaller items are sometimes getting overlooked only to resurface at the end.\nPlease describe what went didn't go well in this release., - Deltas remain fairly high, which means our plans are not super reliable\nPlease describe what went didn't go well in this release., Some critical features, like \"sending email notifications,\" surfaced in the last days of the release. If it has been added to the PM list lately, it is probably not a big concern, but if it is in the master list but not appropriately tracked, then it needs to be fixed.\nPlease describe what went didn't go well in this release., * AWS event bridge issues\n* Need to fix action creation in retro tenant, we were running into a few issues as we don't support user action without vendor integration.\n* Some back and forth on tracking dependency call - swanly/confluence, need to get it fixed for 0.9.16\n* Grafana Billing issue - spike in cost (~$82)\nPlease describe what went didn't go well in this release., - Still need lot of work on data migration and prompt testing framework\nPlease describe what went didn't go well in this release., There was a lot of undefined scope during the start of this sprint due to product capacity being low. This resulted in a number of projects getting pushed out into the next release.\nPlease describe what went didn't go well in this release., nan\nPlease describe what went didn't go well in this release., Though we were able to complete the dev testing just in time before the branch cut I think we were a little bit late on it. Probably happened this time as there were small changes in multiple areas and we had to dev test all of them together which made it heavier towards the end.\nPlease describe what went well in this release., Good level of proactive communication from the Eng team regarding: specs that needed clarification, status of UI work, and issues identified during the QA process that needed additional UX input.\nPlease describe what went well in this release., * Dashboard enhancements, MVP+1\n* AWS - cost metrics, great job by Prashant\n* Sprint retro setup for all teams\n* Selenium web-driver issue: thanks to Anu for finding the root cause. \n* Script to automate engagement creation for EA\nPlease describe what went well in this release., We had a very good cross team collaboration for CXO dashboard mvp+1 release.\nProposed enhancements from product management sounds exciting in terms of business as well as product flexibility.\nUX is getting better.\nPlease describe what went well in this release., This release mostly included enhancing and revamping existing functionalities and the small changes in multiple features has improved the UI/UX a lot as a whole. Enjoyed working on different areas throughout the release, got to learn a few new things.\nPlease describe what went well in this release., - Thorough design discussions and requirements clarification with PM for jira integration which will hopefully minimise churn when the feature is built\n- Got a good chunk of pulse improvements related backend in the release\nPlease describe what went well in this release., NLP platform refined and ask ai responses improved", "doc_id": "2447cc8c-ce73-4b77-8349-d31ce3f9fb14", "embedding": null, "doc_hash": "697489a25209505572af9638a7d67b43688e4c5fb1b5fdb7097392b41a2b7fb9", "extra_info": null, "node_info": {"start": 3987, "end": 8277, "_node_type": "1"}, "relationships": {"1": "eadff1db-bc7f-4aff-b6a5-222c86754a4c", "2": "9e32df02-1517-4364-bb5c-1f40b75ade5c", "3": "9e41b425-af5c-4d8f-ac26-23a810864e37"}}, "__type__": "1"}, "9e41b425-af5c-4d8f-ac26-23a810864e37": {"__data__": {"text": "what went well in this release., NLP platform refined and ask ai responses improved \n\nPlease describe what went well in this release., Development of new Participants Tab in Pulse results tab.. POC for pulse digest email template with the help of Ritu and Seshan. \u00a0Lot of MVP+1 improvements. \n\nPradeep helped with clarifying lot of questions and doubts for MVP+1 improvements. \n\nLastly bug fixes.\nPlease describe what went well in this release., nan\nPlease describe what went well in this release., nan\nPlease describe what went well in this release., We improved the quality of AI summaries and chat responses with code changes and tuning prompts. \nWe need to balance precision, recall and performance. It is not complete but we are making progressive improvements for our design.\nPlease describe what went well in this release., System test coverage wrt scoring \n\nPlease describe what went well in this release., Writing integration tests for AskAI\nPlease describe what went well in this release., - Discussions around class/instance for metrics, alerts/notification\nPlease describe what went well in this release., - Significant improvements in overall askai platform -  timeline summary and chat response \n- code coverage/unit tests for askai platform\nPlease describe what went well in this release., Metrics library  related Development, Attention on aws Infra cost , gamification .\nPlease describe what went well in this release., - Slightly higher per-capita completion compared to 9.14 (27 vs 27.2)\n- Far fewer problems in deployment\nPlease suggest a few improvements to improve our execution., * we need to setup monitoring or cost thresholds on 3rd party integrations where we might leak some $'s eg. Grafana.\n* Attach/review #sos summary generated in sos update for individual teams, it might help us validate quality of summary\nPlease suggest a few improvements to improve our execution., 1. We are doing this already but need to make sure that we discussion even smaller items and related dependencies with defined owner in dependency call.\nPlease suggest a few improvements to improve our execution., nan\nPlease suggest a few improvements to improve our execution., 1. Though Demos in sos are good place to get feedback we need to find a way to get this feedback sooner if possible.  some options we are trying/can try.\na. Based on sos discussion, Tag all the teams in user facing threads so that interested people could go through the mocks/specs and give suggestions if any.\nb. Demo the changes from ui even though the backend is not integrated with mock data wherever possible.\nPlease suggest a few improvements to improve our execution., nan\nPlease suggest a few improvements to improve our execution., We should get back to dev testing the individual features as soon as they are ready instead of doing it collectively at the end of release.\nPlease suggest a few improvements to improve our execution., - Need to include performance tests in our dev & QA cycles. Apps could look at fan outs, UI at page load times and backend services could look at query logs - all proactively without a serious issue being reported. QA could take this up in the week after prod deployment.\nPlease suggest a few improvements to improve our execution., Product capacity issues aren't ideal but are temporary (we are actively hiring for PM + UX roles). Ideally we'd have some high priority projects (potentially eng/infra projects)  that are agreed upon during sprint week 1 and available in case the Product capacity is running behind. The goal would be to be able to get a meaningful update for customers (e.g. performance improvement, significant reduction of bug backlog, etc.) even if we cannot get a new feature in.\n\nAlso we are getting better at utilizing jira/confluence as the documentation center but need to keep reminding ourselves to log decisions on scope/changes there. We will benefit in the future when we want to look back and will create good hygiene going forward for us to operate more autonomously (with less meetings to resolve disconnects).\nPlease suggest a few improvements to improve our execution., nan\nWere the requirements clear when you started working on your tasks?, Very clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on", "doc_id": "9e41b425-af5c-4d8f-ac26-23a810864e37", "embedding": null, "doc_hash": "99c44c953b375a00831e913e01a9d7668749040b2fad872505923c515f521992", "extra_info": null, "node_info": {"start": 8291, "end": 12639, "_node_type": "1"}, "relationships": {"1": "eadff1db-bc7f-4aff-b6a5-222c86754a4c", "2": "2447cc8c-ce73-4b77-8349-d31ce3f9fb14", "3": "d0e5b301-ffbb-49d6-8fe3-2b30eda93c38"}}, "__type__": "1"}, "d0e5b301-ffbb-49d6-8fe3-2b30eda93c38": {"__data__": {"text": "working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, None of these apply\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Very clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, 50-50\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, None of these apply\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, 50-50\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, None of these apply\nWere the requirements clear when you started working on your tasks?, Mostly clear\nWere the requirements clear when you started working on your tasks?, Very clear\nWere the requirements clear when you started working on your tasks?, Very clear\nWere the requirements clear when you started working on your tasks?, None of these apply\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Moderate\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Moderate\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, None of these apply\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Very Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good\nWhat is your overall happiness rating?, Good", "doc_id": "d0e5b301-ffbb-49d6-8fe3-2b30eda93c38", "embedding": null, "doc_hash": "a866301dcbe301f1754b688359931c82f700c382496cf9f07f1006811d1f1a8e", "extra_info": null, "node_info": {"start": 12617, "end": 16106, "_node_type": "1"}, "relationships": {"1": "eadff1db-bc7f-4aff-b6a5-222c86754a4c", "2": "9e41b425-af5c-4d8f-ac26-23a810864e37"}}, "__type__": "1"}}, "docstore/ref_doc_info": {"eadff1db-bc7f-4aff-b6a5-222c86754a4c": {"doc_ids": ["9e32df02-1517-4364-bb5c-1f40b75ade5c", "2447cc8c-ce73-4b77-8349-d31ce3f9fb14", "9e41b425-af5c-4d8f-ac26-23a810864e37", "d0e5b301-ffbb-49d6-8fe3-2b30eda93c38"], "extra_info": {}}}}

index_v2/RetroSep/index_store.json

@@ -0,0 +1 @@
+{"index_store/data": {"52de045c-83e1-45d3-be4f-1b52e143593d": {"__type__": "vector_store", "__data__": "{\"index_id\": \"52de045c-83e1-45d3-be4f-1b52e143593d\", \"summary\": null, \"nodes_dict\": {\"9e32df02-1517-4364-bb5c-1f40b75ade5c\": \"9e32df02-1517-4364-bb5c-1f40b75ade5c\", \"2447cc8c-ce73-4b77-8349-d31ce3f9fb14\": \"2447cc8c-ce73-4b77-8349-d31ce3f9fb14\", \"9e41b425-af5c-4d8f-ac26-23a810864e37\": \"9e41b425-af5c-4d8f-ac26-23a810864e37\", \"d0e5b301-ffbb-49d6-8fe3-2b30eda93c38\": \"d0e5b301-ffbb-49d6-8fe3-2b30eda93c38\"}, \"doc_id_dict\": {}, \"embeddings_dict\": {}}"}}}

raw/RetroSep.csv

@@ -0,0 +1,154 @@
+"question","response"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Moderate"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Moderate"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Good"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","Thanks to UX team for all the detailed designs and covering almost all the possible scenarios. Makes life a lot easier while developing the feature."
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",""
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",""
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","In addition to excel that alex maintains, what we lack sometimes is a list of laundry list of items that PM is tracking for a release as sometimes the minor items could be under an epic but might be important"
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","In earlier days, we used to maintain features on the Wiki page. We are using a spreadsheet, but this spreadsheet covers only some things. We need to maintain a master list of product features for each release. We need to include all user-facing features in this list. We need to make it available for everyone to update it. It will provide constant visibility and allow review until the release readiness meeting."
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","NA"
+"Please describe what went didn't go well in this release.","Definitely some delays on my side in getting clarity wrt to Pulse Improvements, which might have made it into this release had I been more proactive"
+"Please describe what went didn't go well in this release.",""
+"Please describe what went didn't go well in this release.",""
+"Please describe what went didn't go well in this release.","It would have been nice if backend APIs were available for UI a little earlier, we could have had more time for Dev testing."
+"Please describe what went didn't go well in this release.","Few bug fixes and features are not QA-Ready even after the branch cut is done"
+"Please describe what went didn't go well in this release.","1. When there are many smaller items/enhancement (usually post a major feature release), sometime we are loosing track of what needs to be done.  
+2. Editing of UX post ""ready for dev"" also causes some confusion. Most of the time it is conveyed , but smaller items are sometimes getting overlooked only to resurface at the end."
+"Please describe what went didn't go well in this release.","- Deltas remain fairly high, which means our plans are not super reliable"
+"Please describe what went didn't go well in this release.","Some critical features, like ""sending email notifications,"" surfaced in the last days of the release. If it has been added to the PM list lately, it is probably not a big concern, but if it is in the master list but not appropriately tracked, then it needs to be fixed."
+"Please describe what went didn't go well in this release.","* AWS event bridge issues
+* Need to fix action creation in retro tenant, we were running into a few issues as we don't support user action without vendor integration.
+* Some back and forth on tracking dependency call - swanly/confluence, need to get it fixed for 0.9.16
+* Grafana Billing issue - spike in cost (~$82)"
+"Please describe what went didn't go well in this release.","- Still need lot of work on data migration and prompt testing framework"
+"Please describe what went didn't go well in this release.","There was a lot of undefined scope during the start of this sprint due to product capacity being low. This resulted in a number of projects getting pushed out into the next release."
+"Please describe what went didn't go well in this release.","NA"
+"Please describe what went didn't go well in this release.","Though we were able to complete the dev testing just in time before the branch cut I think we were a little bit late on it. Probably happened this time as there were small changes in multiple areas and we had to dev test all of them together which made it heavier towards the end."
+"Please describe what went well in this release.","Good level of proactive communication from the Eng team regarding: specs that needed clarification, status of UI work, and issues identified during the QA process that needed additional UX input."
+"Please describe what went well in this release.","* Dashboard enhancements, MVP+1
+* AWS - cost metrics, great job by Prashant
+* Sprint retro setup for all teams
+* Selenium web-driver issue: thanks to Anu for finding the root cause. 
+* Script to automate engagement creation for EA"
+"Please describe what went well in this release.","We had a very good cross team collaboration for CXO dashboard mvp+1 release.
+Proposed enhancements from product management sounds exciting in terms of business as well as product flexibility.
+UX is getting better."
+"Please describe what went well in this release.","This release mostly included enhancing and revamping existing functionalities and the small changes in multiple features has improved the UI/UX a lot as a whole. Enjoyed working on different areas throughout the release, got to learn a few new things."
+"Please describe what went well in this release.","- Thorough design discussions and requirements clarification with PM for jira integration which will hopefully minimise churn when the feature is built
+- Got a good chunk of pulse improvements related backend in the release"
+"Please describe what went well in this release.","NLP platform refined and ask ai responses improved 
+"
+"Please describe what went well in this release.","Development of new Participants Tab in Pulse results tab.. POC for pulse digest email template with the help of Ritu and Seshan.  Lot of MVP+1 improvements. 
+
+Pradeep helped with clarifying lot of questions and doubts for MVP+1 improvements. 
+
+Lastly bug fixes."
+"Please describe what went well in this release.",""
+"Please describe what went well in this release.","NA"
+"Please describe what went well in this release.","We improved the quality of AI summaries and chat responses with code changes and tuning prompts. 
+We need to balance precision, recall and performance. It is not complete but we are making progressive improvements for our design."
+"Please describe what went well in this release.","System test coverage wrt scoring 
+"
+"Please describe what went well in this release.","Writing integration tests for AskAI"
+"Please describe what went well in this release.","- Discussions around class/instance for metrics, alerts/notification"
+"Please describe what went well in this release.","- Significant improvements in overall askai platform -  timeline summary and chat response 
+- code coverage/unit tests for askai platform"
+"Please describe what went well in this release.","Metrics library  related Development, Attention on aws Infra cost , gamification ."
+"Please describe what went well in this release.","- Slightly higher per-capita completion compared to 9.14 (27 vs 27.2)
+- Far fewer problems in deployment"
+"Please suggest a few improvements to improve our execution.","* we need to setup monitoring or cost thresholds on 3rd party integrations where we might leak some $'s eg. Grafana.
+* Attach/review #sos summary generated in sos update for individual teams, it might help us validate quality of summary"
+"Please suggest a few improvements to improve our execution.","1. We are doing this already but need to make sure that we discussion even smaller items and related dependencies with defined owner in dependency call."
+"Please suggest a few improvements to improve our execution.",""
+"Please suggest a few improvements to improve our execution.","1. Though Demos in sos are good place to get feedback we need to find a way to get this feedback sooner if possible.  some options we are trying/can try.
+a. Based on sos discussion, Tag all the teams in user facing threads so that interested people could go through the mocks/specs and give suggestions if any.
+b. Demo the changes from ui even though the backend is not integrated with mock data wherever possible."
+"Please suggest a few improvements to improve our execution.",""
+"Please suggest a few improvements to improve our execution.","We should get back to dev testing the individual features as soon as they are ready instead of doing it collectively at the end of release."
+"Please suggest a few improvements to improve our execution.","- Need to include performance tests in our dev & QA cycles. Apps could look at fan outs, UI at page load times and backend services could look at query logs - all proactively without a serious issue being reported. QA could take this up in the week after prod deployment."
+"Please suggest a few improvements to improve our execution.","Product capacity issues aren't ideal but are temporary (we are actively hiring for PM + UX roles). Ideally we'd have some high priority projects (potentially eng/infra projects)  that are agreed upon during sprint week 1 and available in case the Product capacity is running behind. The goal would be to be able to get a meaningful update for customers (e.g. performance improvement, significant reduction of bug backlog, etc.) even if we cannot get a new feature in.
+
+Also we are getting better at utilizing jira/confluence as the documentation center but need to keep reminding ourselves to log decisions on scope/changes there. We will benefit in the future when we want to look back and will create good hygiene going forward for us to operate more autonomously (with less meetings to resolve disconnects)."
+"Please suggest a few improvements to improve our execution.","NA"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","50-50"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","50-50"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Moderate"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Moderate"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","None of these apply"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Very Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"
+"What is your overall happiness rating?","Good"