Added Retro June Data

.idea/checkstyle-idea.xml

@@ -3,6 +3,7 @@
   <component name="CheckStyle-IDEA" serialisationVersion="2">
     <checkstyleVersion>10.3.2</checkstyleVersion>
     <scanScope>JavaOnly</scanScope>
+    <option name="thirdPartyClasspath" />
     <option name="activeLocationIds">
       <option value="0357db59-51a7-49e6-a960-58a5b3ef052c" />
     </option>

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 = ["Mattel_06_23_Open_Gen", "mattel_06_23_gen", "OnCall", "RetroMay", "RetroApril", "RetroMarch", "Snowflake", "Datadog", "Databricks", "SplunkProducts",
+dataFiles = ["RetroJune", "Mattel_06_23_Open_Gen", "mattel_06_23_gen", "OnCall", "RetroMay", "RetroApril", "RetroMarch", "Snowflake", "Datadog", "Databricks", "SplunkProducts",
              "SplunkEnterprise"]
 
 cache = {}

index_v2/RetroJune/docstore.json

@@ -0,0 +1 @@
+{"docstore/metadata": {"304c1252-9fea-4462-8a6b-6002fd53dc91": {"doc_hash": "51b1883c443465a7e4dd1ece0c5d634bd5a8cd9bda616e42f87b6bd82b59dba1"}, "0292904a-9a5f-4118-b5f3-3964d7a5966e": {"doc_hash": "c934e50d811d33a769693f66128e1b51b5cbe342bfc2d1cd9e2f4e35977b0995", "ref_doc_id": "304c1252-9fea-4462-8a6b-6002fd53dc91"}, "f0ec211f-f7a0-451c-a2d3-970129b26c47": {"doc_hash": "19e80f465854a3e59c4b02232deef823a28396e0deab3f9d2e419d3c9ec4f6c0", "ref_doc_id": "304c1252-9fea-4462-8a6b-6002fd53dc91"}, "61112791-f659-45bc-9e32-e4d76ae8afce": {"doc_hash": "80341fa55e423e18539ba3d962346f01946a21cf9e6a05830ee1e639a6f68aff", "ref_doc_id": "304c1252-9fea-4462-8a6b-6002fd53dc91"}, "a2c5f2d6-ecfb-42e7-acac-e77e098a9271": {"doc_hash": "ef83e8222ab4173c4032b8f1729111e97b62b87c1306ce904cb36ac3ce8cb0f5", "ref_doc_id": "304c1252-9fea-4462-8a6b-6002fd53dc91"}}, "docstore/data": {"0292904a-9a5f-4118-b5f3-3964d7a5966e": {"__data__": {"text": "Were the requirements clear when you started working on your tasks?, Very clear\nPlease describe what went well in this release., * Design discussions for CISO dashboard\n* Overall implementation pace across teams, special kudos to UI and Apps teams we had a working demo ready within hours of sharing backend API for ownership\n* Stage aurora migration completed for all services in just 4 days \n* Tighter integration with VPN\nPlease describe what went didn't go well in this release., * Planning and tracking for CISO dashboard is a bit challenging as across the board we had multiple changes happening in parallel.\n* comparatively more meetings during planning\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., Increased systest coverage ,\nAutomating long pending onboarding flow task\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 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., nan\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, Very Good\nWhat is your overall happiness rating?, Very 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?, 50-50\nPlease describe what went well in this release., Increased systest coverage (Contributions by Dev and QA)\nPlease describe what went didn't go well in this release., Lack of clarity on what goes as part of 0.9.13 and 0.9.14. Was not able to plan QA cycles or tasks easily.\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\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., CISO -> Some minor confusion regarding product types but overall the new designs were pretty clear (great job by Product and UX team I think). Also, technical discussion before starting on the feature helped to understand a few things better (thanks to Ritu, Guru and Pradeep).\nPlease describe what went well in this release., The pace at which everyone worked and coordinated was excellent. We were able to demo both the CISO dashboard and Metrics Library in consecutive weeks.\nPlease describe what went didn't go well in this release., Due to time constraint, couldn't test the features developed till now end to end as thoroughly as we usually do. But I believe we can cover the overall dev testing in the coming sprint.\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?, Very clear\nPlease describe what went well in this release., Cross team coordination, planning ( thanks to Anil for driving this effort )\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", "doc_id": "0292904a-9a5f-4118-b5f3-3964d7a5966e", "embedding": null, "doc_hash": "c934e50d811d33a769693f66128e1b51b5cbe342bfc2d1cd9e2f4e35977b0995", "extra_info": null, "node_info": {"start": 0, "end": 4235, "_node_type": "1"}, "relationships": {"1": "304c1252-9fea-4462-8a6b-6002fd53dc91", "3": "f0ec211f-f7a0-451c-a2d3-970129b26c47"}}, "__type__": "1"}, "f0ec211f-f7a0-451c-a2d3-970129b26c47": {"__data__": {"text": "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 didn't go well in this release., some confusion regarding CISO dashboard, had to keep searching confluence to see if any new concepts/requirement has been added\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\nPlease describe what went well in this release., Enjoyed the design activity  on metrics-library end\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?, 50-50\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., Needed few meetings with PM and UX to get clarity on what needs to be done.\nPlease describe what went didn't go well in this release., UI was developed in parallel to backend/apps with mock json files to make some progress and not get entirely blocked on backend. mock pages were available in int environment to get a feel of how things might look. \nWhile the UX was changing over a period of time while we got clarity we could accommodate the changes and hope this reduces once we have more clarity over next releases.\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., Major chunk of backend changes for multi instance got merged. Also data team onboarding was good\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 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., CISO Dashboard : It was great to see entire UI team working on dashboard simultaneously.\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?, 50-50\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., Definition of timeline summary vs trendlyne summary was hazy - It would have been great of we have detailed spec from pm along with figma\nPlease describe what went well in this release., #NAME?\nPlease describe what went didn't go well in this release., #NAME?\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Very Poor\nWhat is your overall happiness rating?, Moderate\nWere the requirements clear when you started working on your tasks?, Hazy, needed to work with PM for clarity\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., For CISO, we had lot of sessions with PM/Design to narrow down and get clarity required for MVP.\nPlease describe what went well in this release., #NAME?\nPlease describe what went didn't go well in this release., We weren't able to deliver 0.9.13 as a release since the changes for CISO are everywhere.\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?, Very clear\nPlease suggest a few improvements to improve our", "doc_id": "f0ec211f-f7a0-451c-a2d3-970129b26c47", "embedding": null, "doc_hash": "19e80f465854a3e59c4b02232deef823a28396e0deab3f9d2e419d3c9ec4f6c0", "extra_info": null, "node_info": {"start": 4165, "end": 8429, "_node_type": "1"}, "relationships": {"1": "304c1252-9fea-4462-8a6b-6002fd53dc91", "2": "0292904a-9a5f-4118-b5f3-3964d7a5966e", "3": "61112791-f659-45bc-9e32-e4d76ae8afce"}}, "__type__": "1"}, "61112791-f659-45bc-9e32-e4d76ae8afce": {"__data__": {"text": "you started working on your tasks?, Very clear\nPlease suggest a few improvements to improve our execution., Use zeplin to track any new UX changes\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?, Mostly clear\nPlease describe what went well in this release., Team work. How we shared and executed the work in Frontend. Good code reviews and  feedbacks thanks to Amit. \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?, 50-50\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., Awesome  PRD written by Aryan and Anandhi . CIXO  dashboard taking good shape .\nPlease describe what went didn't go well in this release., Few extra iterations around metrics services (CSV structure , API request/response ) .\nPlease suggest a few improvements to improve our execution., Great PRD but one end to end CISO dashboard example(Happy flow) could have helped .\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., Teams re-aligned and swarming to complete the CISO dashboard work.\nPlease describe what went didn't go well in this release., Not enough clarity about release plan, confusion about releasing mock version.\nPlease suggest a few improvements to improve our execution., It is important to consider this release as a unique situation that aligns with our specific goals, rather than adopting it as a standard practice. While emphasizing one feature in a single release can have benefits in terms of alignment and focus, it is crucial to acknowledge that it can also introduce potential challenges related to quality and efficiency\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., This sprint, I mostly worked on the CISO dashboard, and the way we(UI team, Pradeep) planned, prioritized, and executed CISO dashboard-related changes was fantastic. \n\nThanks to apps/disc teams for providing the majority of the APIs on demand.\n\nAlso, thanks to Meaghan for answering any UX-related questions.\nPlease describe what went didn't go well in this release., There were few things about the CISO dashboard that were unclear, or we made a few changes during development, such as the score tooltip design and a couple of UI changes that required some re-work.\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Good\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, 50-50\n<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release, Good\nWhat is your overall happiness rating?, Very Good\nWere the requirements clear when you started working on your tasks?, Very clear\nPlease comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear., CISO Dashboard PM specs were fairly clear on features that were required. We had a couple of follow-ups around sequencing, trade-offs to make the MVP more lean, etc. but this process was overall smooth and easy to follow.\nPlease describe what went well in this release., #NAME?\nPlease suggest a few improvements to improve our execution.,", "doc_id": "61112791-f659-45bc-9e32-e4d76ae8afce", "embedding": null, "doc_hash": "80341fa55e423e18539ba3d962346f01946a21cf9e6a05830ee1e639a6f68aff", "extra_info": null, "node_info": {"start": 8420, "end": 12666, "_node_type": "1"}, "relationships": {"1": "304c1252-9fea-4462-8a6b-6002fd53dc91", "2": "f0ec211f-f7a0-451c-a2d3-970129b26c47", "3": "a2c5f2d6-ecfb-42e7-acac-e77e098a9271"}}, "__type__": "1"}, "a2c5f2d6-ecfb-42e7-acac-e77e098a9271": {"__data__": {"text": "in this release., #NAME?\nPlease suggest a few improvements to improve our execution., PM, UX, and Eng executing at the same time which leads to occasional bottlenecks. As the team scales and we get more bandwidth, I'd encourage us to find methods to sequence this out more\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": "a2c5f2d6-ecfb-42e7-acac-e77e098a9271", "embedding": null, "doc_hash": "ef83e8222ab4173c4032b8f1729111e97b62b87c1306ce904cb36ac3ce8cb0f5", "extra_info": null, "node_info": {"start": 12662, "end": 13307, "_node_type": "1"}, "relationships": {"1": "304c1252-9fea-4462-8a6b-6002fd53dc91", "2": "61112791-f659-45bc-9e32-e4d76ae8afce"}}, "__type__": "1"}}, "docstore/ref_doc_info": {"304c1252-9fea-4462-8a6b-6002fd53dc91": {"doc_ids": ["0292904a-9a5f-4118-b5f3-3964d7a5966e", "f0ec211f-f7a0-451c-a2d3-970129b26c47", "61112791-f659-45bc-9e32-e4d76ae8afce", "a2c5f2d6-ecfb-42e7-acac-e77e098a9271"], "extra_info": {}}}}

index_v2/RetroJune/index_store.json

@@ -0,0 +1 @@
+{"index_store/data": {"0801c011-eb9a-45f8-acc0-a6a02b4675b3": {"__type__": "vector_store", "__data__": "{\"index_id\": \"0801c011-eb9a-45f8-acc0-a6a02b4675b3\", \"summary\": null, \"nodes_dict\": {\"0292904a-9a5f-4118-b5f3-3964d7a5966e\": \"0292904a-9a5f-4118-b5f3-3964d7a5966e\", \"f0ec211f-f7a0-451c-a2d3-970129b26c47\": \"f0ec211f-f7a0-451c-a2d3-970129b26c47\", \"61112791-f659-45bc-9e32-e4d76ae8afce\": \"61112791-f659-45bc-9e32-e4d76ae8afce\", \"a2c5f2d6-ecfb-42e7-acac-e77e098a9271\": \"a2c5f2d6-ecfb-42e7-acac-e77e098a9271\"}, \"doc_id_dict\": {}, \"embeddings_dict\": {}}"}}}

raw/RetroJune.csv

@@ -0,0 +1,133 @@
+question,response
+Were the requirements clear when you started working on your tasks?,Very clear
+Please describe what went well in this release.,"* Design discussions for CISO dashboard
+* Overall implementation pace across teams, special kudos to UI and Apps teams we had a working demo ready within hours of sharing backend API for ownership
+* Stage aurora migration completed for all services in just 4 days 
+* Tighter integration with VPN"
+Please describe what went didn't go well in this release.,"* Planning and tracking for CISO dashboard is a bit challenging as across the board we had multiple changes happening in parallel.
+* comparatively more meetings during planning"
+<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.,"Increased systest coverage ,
+Automating long pending onboarding flow task"
+<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 comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",
+Please describe what went well in this release.,
+Please describe what went didn't go well in this release.,
+Please suggest a few improvements to improve our execution.,
+<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?,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?,50-50
+Please describe what went well in this release.,Increased systest coverage (Contributions by Dev and QA)
+Please describe what went didn't go well in this release.,Lack of clarity on what goes as part of 0.9.13 and 0.9.14. Was not able to plan QA cycles or tasks easily.
+<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
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","CISO -> Some minor confusion regarding product types but overall the new designs were pretty clear (great job by Product and UX team I think). Also, technical discussion before starting on the feature helped to understand a few things better (thanks to Ritu, Guru and Pradeep)."
+Please describe what went well in this release.,The pace at which everyone worked and coordinated was excellent. We were able to demo both the CISO dashboard and Metrics Library in consecutive weeks.
+Please describe what went didn't go well in this release.,"Due to time constraint, couldn't test the features developed till now end to end as thoroughly as we usually do. But I believe we can cover the overall dev testing in the coming sprint."
+<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?,Very clear
+Please describe what went well in this release.,"Cross team coordination, planning ( thanks to Anil for driving this effort )"
+<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?,Very 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.,"some confusion regarding CISO dashboard, had to keep searching confluence to see if any new concepts/requirement has been added"
+<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
+Please describe what went well in this release.,Enjoyed the design activity  on metrics-library end
+<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?,50-50
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",Needed few meetings with PM and UX to get clarity on what needs to be done.
+Please describe what went didn't go well in this release.,"UI was developed in parallel to backend/apps with mock json files to make some progress and not get entirely blocked on backend. mock pages were available in int environment to get a feel of how things might look. 
+While the UX was changing over a period of time while we got clarity we could accommodate the changes and hope this reduces once we have more clarity over next releases."
+<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.,Major chunk of backend changes for multi instance got merged. Also data team onboarding was good
+<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 comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",NA
+Please describe what went well in this release.,CISO Dashboard : It was great to see entire UI team working on dashboard simultaneously.
+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?,50-50
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.",Definition of timeline summary vs trendlyne summary was hazy - It would have been great of we have detailed spec from pm along with figma
+Please describe what went well in this release.,#NAME?
+Please describe what went didn't go well in this release.,#NAME?
+<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release,Very Poor
+What is your overall happiness rating?,Moderate
+Were the requirements clear when you started working on your tasks?,"Hazy, needed to work with PM for clarity"
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","For CISO, we had lot of sessions with PM/Design to narrow down and get clarity required for MVP."
+Please describe what went well in this release.,#NAME?
+Please describe what went didn't go well in this release.,We weren't able to deliver 0.9.13 as a release since the changes for CISO are everywhere.
+<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?,Very clear
+Please suggest a few improvements to improve our execution.,Use zeplin to track any new UX changes
+<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?,Mostly clear
+Please describe what went well in this release.,Team work. How we shared and executed the work in Frontend. Good code reviews and  feedbacks thanks to Amit. 
+<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?,50-50
+<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.,Awesome  PRD written by Aryan and Anandhi . CIXO  dashboard taking good shape .
+Please describe what went didn't go well in this release.,"Few extra iterations around metrics services (CSV structure , API request/response ) ."
+Please suggest a few improvements to improve our execution.,Great PRD but one end to end CISO dashboard example(Happy flow) could have helped .
+<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.,Teams re-aligned and swarming to complete the CISO dashboard work.
+Please describe what went didn't go well in this release.,"Not enough clarity about release plan, confusion about releasing mock version."
+Please suggest a few improvements to improve our execution.,"It is important to consider this release as a unique situation that aligns with our specific goals, rather than adopting it as a standard practice. While emphasizing one feature in a single release can have benefits in terms of alignment and focus, it is crucial to acknowledge that it can also introduce potential challenges related to quality and efficiency"
+<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.,"This sprint, I mostly worked on the CISO dashboard, and the way we(UI team, Pradeep) planned, prioritized, and executed CISO dashboard-related changes was fantastic. 
+
+Thanks to apps/disc teams for providing the majority of the APIs on demand.
+
+Also, thanks to Meaghan for answering any UX-related questions."
+Please describe what went didn't go well in this release.,"There were few things about the CISO dashboard that were unclear, or we made a few changes during development, such as the score tooltip design and a couple of UI changes that required some re-work."
+<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release,Good
+What is your overall happiness rating?,Very Good
+Were the requirements clear when you started working on your tasks?,50-50
+<ONLY PM SHOULD ANSWER THIS QUESTION> Please rate the payload of this release,Good
+What is your overall happiness rating?,Very Good
+Were the requirements clear when you started working on your tasks?,Very clear
+"Please comment on requirement clarity, more so if the requirements were NOT mostly clear or very clear.","CISO Dashboard PM specs were fairly clear on features that were required. We had a couple of follow-ups around sequencing, trade-offs to make the MVP more lean, etc. but this process was overall smooth and easy to follow."
+Please describe what went well in this release.,#NAME?
+Please suggest a few improvements to improve our execution.,"PM, UX, and Eng executing at the same time which leads to occasional bottlenecks. As the team scales and we get more bandwidth, I'd encourage us to find methods to sequence this out more"
+<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