Updated for Aug retro

app.py

@@ -4,7 +4,7 @@ from pathlib import Path
 import gradio as gr
 from llama_index import VectorStoreIndex, StorageContext, download_loader, load_index_from_storage
 
-dataFiles = ["RetroJune", "Mattel_06_23_Open_Gen", "mattel_06_23_gen", "OnCall", "RetroMay", "RetroApril", "RetroMarch", "Snowflake", "Datadog", "Databricks", "SplunkProducts",
+dataFiles = ["RetroAug", "RetroJune", "Mattel_06_23_Open_Gen", "mattel_06_23_gen", "OnCall", "RetroMay", "RetroApril", "RetroMarch", "Snowflake", "Datadog", "Databricks", "SplunkProducts",
              "SplunkEnterprise"]
 
 cache = {}
@@ -68,7 +68,7 @@ loadData()
 iface = gr.Interface(fn=chatbot,
                      inputs=[
                          gr.Dropdown(dataFiles,
-                                     type="value", value="Mattel_06_23_Open_Gen", label="Select Pulse Data"),
+                                     type="value", value="RetroAug", 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/RetroAug/docstore.json

@@ -0,0 +1 @@
+{"docstore/metadata": {"42181642-806c-459c-b707-23e9a19fd373": {"doc_hash": "671e329adaf97ebb2cc32a096ccf937b710c0a4e6de84f151660deebee1d1aa8"}, "a0c577d2-767e-4354-954f-2157674c7992": {"doc_hash": "83932dc9cb12c454ca9df83278278bd9299a71419640929408fe6fa27bf57a46", "ref_doc_id": "42181642-806c-459c-b707-23e9a19fd373"}, "1d0f674e-a609-4a33-aa2f-647c4eed5cc2": {"doc_hash": "23edb23c2d2630b024aea0febdb867f65c0cec6b8092f025d638f972e5237d27", "ref_doc_id": "42181642-806c-459c-b707-23e9a19fd373"}, "9f8b606e-2bb0-44da-90d6-a45c179fcfff": {"doc_hash": "a214f817bd823d9b23a07304c5e86090737cab370c03f2d9a9f8a05a769112b0", "ref_doc_id": "42181642-806c-459c-b707-23e9a19fd373"}, "6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9": {"doc_hash": "531ddb2e770871f381f39605e6c45dd8e36d7732bbdcf5d287ec9cb58b2c42d8", "ref_doc_id": "42181642-806c-459c-b707-23e9a19fd373"}}, "docstore/data": {"a0c577d2-767e-4354-954f-2157674c7992": {"__data__": {"text": "Were the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went didn't go well in this release., - Deployment recipes and some of the handoff aspects need more care and follow-through\nPlease suggest a few improvements to improve our execution., - Code reviews should not be pass throughs. Need to force ourselves to force ourselves to ask questions\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\nPlease describe what went didn't go well in this release., Went well:\n1. Massive release with lot of changes\n2. Early branch cut and release to stage helped in identifying some infra issues and address them before prod deployment\n3. Service registry browser work from Bharat \n4. Kudos to sys_test team for building EA demo dashboard\n\n\nDidn't go well:\n1. Some sections in deployment dependency could have been more descriptive. \n2. Configuration issues causing delay in deployment to stage\nPlease suggest a few improvements to improve our execution., For complicated deployment steps (out of ordinary) being attempted for first time if we can record a demo loom video or have a meeting with platform team and explain the steps involved it might help reduce the friction during deployment.\n\nWhenever we are doing something manually in integration during development please create a task immediately to update CDK / update deployment dependency document if it cannot be automated (external dependency/AWS cdk limitation) .\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., Well documented CISO flows for Demo  and E2E flows \nMost of the CISO testing completed in INT env\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., CISO dashboard!\nCompletely echo on what Ritu has mentioned in kudos channel.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went didn't go well in this release., - Testing in bits and pieces lead to longer integration and regression cycle and few major bugs at the end\n- Few back end features had UX issues but had to let go as it will be addressed in upcoming releases/enhancements. \n- Lack of clarity of what is planned as an enhancement of a feature or for next release\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., - keeping in line with reducing load times parallelization work in platform and fanout in apps was good\n- design documentation, and review for permissions replication provided valuable feedback.\n- testing out of policies for managing the indexes in our systems\nPlease describe what went didn't go well in this release., - ran into a issue with routing feature where the access of data took place even before replication could take place, preventing rollout of this to production\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these", "doc_id": "a0c577d2-767e-4354-954f-2157674c7992", "embedding": null, "doc_hash": "83932dc9cb12c454ca9df83278278bd9299a71419640929408fe6fa27bf57a46", "extra_info": null, "node_info": {"start": 0, "end": 4262, "_node_type": "1"}, "relationships": {"1": "42181642-806c-459c-b707-23e9a19fd373", "3": "1d0f674e-a609-4a33-aa2f-647c4eed5cc2"}}, "__type__": "1"}, "1d0f674e-a609-4a33-aa2f-647c4eed5cc2": {"__data__": {"text": "SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Moderate\nWere the requirements clear when you started working on your tasks?, Very clear\nPlease describe what went well in this release., Successful delivery of CISO Dashboard MVP Phase. Performance optimization of a few APIs in apps layer.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., Cleared a lot of pending tech debt ( aws batch, es, scheduler service )\nPlease suggest a few improvements to improve our execution., A healthier backlog of items to pick from, if the team has bandwidth.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\nPlease describe what went well in this release., Great cross team collaboration upfront validated by the minimal bugs identified during development and sys test cycles\nPlease describe what went didn't go well in this release., Need to look for opportunities to  put new features behind feature flag where ever possible as there were a few misses\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., CISO dashboard work was a smooth overall. On metrics part, things were properly planned and designed so there were very little to no surprises.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, None of these apply\nPlease suggest a few improvements to improve our execution., One change I would like is to see the backlog for each team to be loaded up so that the per capita story points can be consistently better. Right now even though its loaded up during the early part of the sprint / release, we kinda loose some momentum there.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went didn't go well in this release., nan\nPlease suggest a few improvements to improve our execution., nan\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., - AskAi features completion along with happy path \n- AskAi platform improvements - observability , logging , scaling \n- production deployment of AskAi platform went with out any hassle\nPlease describe what went didn't go well in this release., - good scope for improvements in the generated summary as well as chat responses\n- stage deployment cyclic dependency\n- Need to", "doc_id": "1d0f674e-a609-4a33-aa2f-647c4eed5cc2", "embedding": null, "doc_hash": "23edb23c2d2630b024aea0febdb867f65c0cec6b8092f025d638f972e5237d27", "extra_info": null, "node_info": {"start": 4193, "end": 8491, "_node_type": "1"}, "relationships": {"1": "42181642-806c-459c-b707-23e9a19fd373", "2": "a0c577d2-767e-4354-954f-2157674c7992", "3": "9f8b606e-2bb0-44da-90d6-a45c179fcfff"}}, "__type__": "1"}, "9f8b606e-2bb0-44da-90d6-a45c179fcfff": {"__data__": {"text": "as well as chat responses\n- stage deployment cyclic dependency\n- Need to do improve unit/integration tests plus prompt testing framework\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\nPlease describe what went well in this release., - Excellent team work\n- Good amount of dev testing\n- Iterative development\n- Better planning\nPlease describe what went didn't go well in this release., - Lesser backlog to continue\n- We could have released early to prod as longer lead items like AskAI+Summary are feature flagged anyways. They could have been pushed separately.\n-\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., nan\nPlease describe what went well in this release., Almost everything\nPlease describe what went didn't go well in this release., nan\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Moderate\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease describe what went well in this release., There is a lot of progress in building an NLP platform to harvest all our comments to support future use cases like generating summaries, extracting topics, generating follow-up questions, generating insights, passive sentiment collection, etc.\nPlease describe what went didn't go well in this release., Due to the overlap of the platform and feature work, learning for new team members, there is much spillover from the last release. Very few UI-facing features are available in the current release. For future releases, we need to improve the accuracy and relevance of the data generated from NLP.\nPlease suggest a few improvements to improve our execution., We need to explore more ways to determine the metric for our execution. Currently, we are using story points. Sometimes even people spend late night hours cranking a lot of work, reporting very few story points. In some cases, even if many story points are burned, there is no significant output due to the nature of the exploratory work and sometimes personal issues.\nI don't have any alternate solution but I just want to bring this topic so we can think about it.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Good\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Good\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, None of these apply\nPlease describe what went didn't go well in this release., We did do a challenging release where we put a lot together all at once. That being said, a fair number of edge cases could have been better documented by PM and UX to ensure more consistency in functionality and expectations across the team.\nPlease suggest a few improvements to improve our execution., Rely more on confluence and", "doc_id": "9f8b606e-2bb0-44da-90d6-a45c179fcfff", "embedding": null, "doc_hash": "a214f817bd823d9b23a07304c5e86090737cab370c03f2d9a9f8a05a769112b0", "extra_info": null, "node_info": {"start": 8500, "end": 12844, "_node_type": "1"}, "relationships": {"1": "42181642-806c-459c-b707-23e9a19fd373", "2": "1d0f674e-a609-4a33-aa2f-647c4eed5cc2", "3": "6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9"}}, "__type__": "1"}, "6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9": {"__data__": {"text": "suggest a few improvements to improve our execution., Rely more on confluence and documentation for keeping edge cases tracked.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Very Good\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Mostly clear\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., The \"MVP Demo Checklist / QA list\" product document clearly outlined what was coming up in the next release. Alex helped UX prioritize and stack rank items to allocate our bandwidth.\nPlease describe what went well in this release., Eng team were very responsive, participating in reviews and surfacing constraints/considerations ahead of time.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Good\nWere the requirements clear when you started working on your tasks?, Very clear\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, None of these apply\nWhat is your overall happiness rating?, Very Good", "doc_id": "6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9", "embedding": null, "doc_hash": "531ddb2e770871f381f39605e6c45dd8e36d7732bbdcf5d287ec9cb58b2c42d8", "extra_info": null, "node_info": {"start": 12825, "end": 13995, "_node_type": "1"}, "relationships": {"1": "42181642-806c-459c-b707-23e9a19fd373", "2": "9f8b606e-2bb0-44da-90d6-a45c179fcfff"}}, "__type__": "1"}}, "docstore/ref_doc_info": {"42181642-806c-459c-b707-23e9a19fd373": {"doc_ids": ["a0c577d2-767e-4354-954f-2157674c7992", "1d0f674e-a609-4a33-aa2f-647c4eed5cc2", "9f8b606e-2bb0-44da-90d6-a45c179fcfff", "6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9"], "extra_info": {}}}}

index_v2/RetroAug/index_store.json

@@ -0,0 +1 @@
+{"index_store/data": {"c203c5b6-a84a-4754-a587-f9cf7ed592ae": {"__type__": "vector_store", "__data__": "{\"index_id\": \"c203c5b6-a84a-4754-a587-f9cf7ed592ae\", \"summary\": null, \"nodes_dict\": {\"a0c577d2-767e-4354-954f-2157674c7992\": \"a0c577d2-767e-4354-954f-2157674c7992\", \"1d0f674e-a609-4a33-aa2f-647c4eed5cc2\": \"1d0f674e-a609-4a33-aa2f-647c4eed5cc2\", \"9f8b606e-2bb0-44da-90d6-a45c179fcfff\": \"9f8b606e-2bb0-44da-90d6-a45c179fcfff\", \"6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9\": \"6f19dc6e-9d16-440e-80f0-5f67fa9b2fe9\"}, \"doc_id_dict\": {}, \"embeddings_dict\": {}}"}}}

raw/RetroAug.csv

@@ -0,0 +1,150 @@
+"question","response"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went didn't go well in this release.","- Deployment recipes and some of the handoff aspects need more care and follow-through"
+"Please suggest a few improvements to improve our execution.","- Code reviews should not be pass throughs. Need to force ourselves to force ourselves to ask questions"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Please describe what went didn't go well in this release.","Went well:
+1. Massive release with lot of changes
+2. Early branch cut and release to stage helped in identifying some infra issues and address them before prod deployment
+3. Service registry browser work from Bharat 
+4. Kudos to sys_test team for building EA demo dashboard
+
+
+Didn't go well:
+1. Some sections in deployment dependency could have been more descriptive. 
+2. Configuration issues causing delay in deployment to stage"
+"Please suggest a few improvements to improve our execution.","For complicated deployment steps (out of ordinary) being attempted for first time if we can record a demo loom video or have a meeting with platform team and explain the steps involved it might help reduce the friction during deployment.
+
+Whenever we are doing something manually in integration during development please create a task immediately to update CDK / update deployment dependency document if it cannot be automated (external dependency/AWS cdk limitation) ."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","Well documented CISO flows for Demo  and E2E flows 
+Most of the CISO testing completed in INT env"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","CISO dashboard!
+Completely echo on what Ritu has mentioned in kudos channel."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went didn't go well in this release.","- Testing in bits and pieces lead to longer integration and regression cycle and few major bugs at the end
+- Few back end features had UX issues but had to let go as it will be addressed in upcoming releases/enhancements. 
+- Lack of clarity of what is planned as an enhancement of a feature or for next release"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","- keeping in line with reducing load times parallelization work in platform and fanout in apps was good
+- design documentation, and review for permissions replication provided valuable feedback.
+- testing out of policies for managing the indexes in our systems"
+"Please describe what went didn't go well in this release.","- ran into a issue with routing feature where the access of data took place even before replication could take place, preventing rollout of this to production"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Moderate"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Please describe what went well in this release.","Successful delivery of CISO Dashboard MVP Phase. Performance optimization of a few APIs in apps layer."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","Cleared a lot of pending tech debt ( aws batch, es, scheduler service )"
+"Please suggest a few improvements to improve our execution.","A healthier backlog of items to pick from, if the team has bandwidth."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Please describe what went well in this release.","Great cross team collaboration upfront validated by the minimal bugs identified during development and sys test cycles"
+"Please describe what went didn't go well in this release.","Need to look for opportunities to  put new features behind feature flag where ever possible as there were a few misses"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","CISO dashboard work was a smooth overall. On metrics part, things were properly planned and designed so there were very little to no surprises."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"Please suggest a few improvements to improve our execution.","One change I would like is to see the backlog for each team to be loaded up so that the per capita story points can be consistently better. Right now even though its loaded up during the early part of the sprint / release, we kinda loose some momentum there."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went didn't go well in this release.","NA"
+"Please suggest a few improvements to improve our execution.","NA"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","- AskAi features completion along with happy path 
+- AskAi platform improvements - observability , logging , scaling 
+- production deployment of AskAi platform went with out any hassle"
+"Please describe what went didn't go well in this release.","- good scope for improvements in the generated summary as well as chat responses
+- stage deployment cyclic dependency
+- Need to do improve unit/integration tests plus prompt testing framework"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"Please describe what went well in this release.","- Excellent team work
+- Good amount of dev testing
+- Iterative development
+- Better planning"
+"Please describe what went didn't go well in this release.","- Lesser backlog to continue
+- We could have released early to prod as longer lead items like AskAI+Summary are feature flagged anyways. They could have been pushed separately.
+-"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","None"
+"Please describe what went well in this release.","Almost everything"
+"Please describe what went didn't go well in this release.","None"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Moderate"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please describe what went well in this release.","There is a lot of progress in building an NLP platform to harvest all our comments to support future use cases like generating summaries, extracting topics, generating follow-up questions, generating insights, passive sentiment collection, etc."
+"Please describe what went didn't go well in this release.","Due to the overlap of the platform and feature work, learning for new team members, there is much spillover from the last release. Very few UI-facing features are available in the current release. For future releases, we need to improve the accuracy and relevance of the data generated from NLP."
+"Please suggest a few improvements to improve our execution.","We need to explore more ways to determine the metric for our execution. Currently, we are using story points. Sometimes even people spend late night hours cranking a lot of work, reporting very few story points. In some cases, even if many story points are burned, there is no significant output due to the nature of the exploratory work and sometimes personal issues.
+I don't have any alternate solution but I just want to bring this topic so we can think about it."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Good"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Good"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","None of these apply"
+"Please describe what went didn't go well in this release.","We did do a challenging release where we put a lot together all at once. That being said, a fair number of edge cases could have been better documented by PM and UX to ensure more consistency in functionality and expectations across the team."
+"Please suggest a few improvements to improve our execution.","Rely more on confluence and documentation for keeping edge cases tracked."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","Very Good"
+"What is your overall happiness rating?","Very Good"
+"Were the requirements clear when you started working on your tasks?","Mostly clear"
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","The ""MVP Demo Checklist / QA list"" product document clearly outlined what was coming up in the next release. Alex helped UX prioritize and stack rank items to allocate our bandwidth."
+"Please describe what went well in this release.","Eng team were very responsive, participating in reviews and surfacing constraints/considerations ahead of time."
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Good"
+"Were the requirements clear when you started working on your tasks?","Very clear"
+"<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release","None of these apply"
+"What is your overall happiness rating?","Very Good"