| {"index_struct": {"__type__": "tree", "__data__": {"index_id": "0d8d0074-4ff8-42f7-a520-b546464346a3", "summary": null, "all_nodes": {"0": "644372cf-8289-4a35-b825-b0e39065607b"}, "root_nodes": {"0": "644372cf-8289-4a35-b825-b0e39065607b"}, "node_id_to_children_ids": {"644372cf-8289-4a35-b825-b0e39065607b": []}}}, "docstore": {"docs": {"644372cf-8289-4a35-b825-b0e39065607b": {"text": "Primary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, Edit and update sentiment feature - everything was available on time which helped to develop and give it to QA on time.\nPrimary User, What didn't go well in this release?, Nothing as such \nPrimary User, To improve our execution what should we add?, Nothing as such\nPrimary User, To improve our execution what should we DROP?, Nothing as such\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Moderate\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., Automation sprint .\nAutomate some of cust/qa found bugs.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, In this sprint, I worked on the Ask AI modal, and it went really well. \nThanks to @meaghanli for her quick UX review and for highlighting a few UX issues.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Hazy, needed to work with PM for clarity\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., Some edge cases needed more definition, as well as what would happen when certain menu options are actioned. We should move towards using Jira to outline clear acceptance criteria for all projects instead of solely relying on Figma.\nPrimary User, What didn't go well in this release?, Several features are only ready for UX review right before the end of the release, or even after the last day of the release. This makes it impossible to ensure product quality in time for the release, especially because UI needs 1 week to action UX review fixes.\nEither:\n1. Release cycles need to be longer\n2. Or we make structural changes so that items are ready for UX review AT LEAST 1\u20132 weeks before the end of the release\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Moderate\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, We could make progress on UX Redesign/Quality issues in 0.9.10. There was pause on this for few releases\nPrimary User, To improve our execution what should we add?, It would be great if we had add backlog of features/POCs to pick from incase if certain feature is deprioritized or we cant start on some feature due to dependencies. We did get UX Quality issues from Meaghan which were helpful in filing the bandwidth for 0.9.10\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, 50-50\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., Since the quarter planning also started when the release started, we had to pick some existing tech debt/spill items.\nPrimary User, What went well in this release?, - Able to pick some tech debts\n- Able to clear and pick items from backlog\nPrimary User, What didn't go well in this release?, - Quarter planning impacted the release planning\nPrimary User, To improve our execution what should we add?, - Plan ahead\n- Have a healthy backlog\nPrimary User, To improve our execution what should we DROP?, - None\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, nan\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., nan\nPrimary User, What went well in this release?, nan\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, nan\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, As a member of the product management team, please explain your choice in the previous response., nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, Good pace throughout the release. Dev testing/bug bash went really well, I think it helps to keep accountability high. UX reviews also useful for the same reasons\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Very Good\nPrimary User, As a member of the product management team, please explain your choice in the previous response., This may have been sent to me by mistake as I don't think I am a member of product management(?), but I think we hit the sweet spot between workload and time in order to deliver quality results.\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What didn't go well in this release?, Few hiccups while releasing the new slack integrator service, need to get to the cause.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., nan\nPrimary User, What went well in this release?, nan\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, nan\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, As a member of the product management team, please explain your choice in the previous response., nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, Good progress made on splitting the slack service as an independent one. Thanks to Nayan for handling this. \nNice features like Pulse retro were introduced.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., nan\nPrimary User, What went well in this release?, nan\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, nan\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, As a member of the product management team, please explain your choice in the previous response., nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., Very similar to the previous release. There were no blockers. Designs and backend APIs were ready beforehand (thanks to design and data team again). UI integrations were smooth as well.\nPrimary User, What went well in this release?, Team was able to improve code structure and optimise some APIs in the apps services. Consistency in MRs getting reviewed by multiple people, this has been good for some time now I think.\nPrimary User, What didn't go well in this release?, Had to spend some extra time on debugging issues related to pulse responses. \nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, Thought towards smart pulse survey designing and reducing AWS cost .\nPrimary User, What didn't go well in this release?, Deployment didn't go smooth this time other than that mostly things are good .\nPrimary User, To improve our execution what should we add?, Can we use chatGPT for company's knowledge base ? Means all confluence/Swagger(API details) on internal chatGPT server .\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, As a member of the product management team, please explain your choice in the previous response., nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, - chatbot poc for demo purposes\n- progress on long term chatbot design\n- good design reviews \n- SQL Replica Read support\nPrimary User, What didn't go well in this release?, - Debugging / Fixing Unplanned issues - open ai threshold breach , redis task manager issue and bugs raised as part of testing\nPrimary User, To improve our execution what should we add?, - Better alerting around cost when it crosses certain threshold (month on month) and look for optimizations\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Please comment on requirement clarity, more so if the requirements were NOT mostly clear OR crystal clear., Requirement is clear. While building proto-type nature features like chat interface there should be more clarity on to-do or not-to-do because there is a lot of back and forth.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, - SSO deployments in prod Lvsands & Haleon\n- Chat bot integration\n- Addressed/working on some major tech-debt items from platform\n- Ability to leverage read instance of aurora\n- Slack native for retro without passwordless auth: much seamless than passwordless auth\n- parallel unit test execution brought down overall build time for tenancy from ~20 mins to ~11 mins\n- Snowflake POC\nPrimary User, What didn't go well in this release?, - System tests tear down issue blocking from running system tests completely in parallel we need to resolve the interlocks\n- Issues found during branch-cut and deployment\n- aws spring library for read/read-write took some time to resolve issues\n- We need to find ways to execute flows before UI integration, if it is not possible then we can request UI team to prioritise these flows (if we can identify them) early during release cycle. We had a situation where we found that backend doesn't support a specific flow on day of branch cut. This may be an exception but evaluating such flows early might help avoiding last minute changes.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, Good\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, - First 3 sprints had better velocity compared to prior releases\n- Faster time to resolving customer issues thanks to Mohith, Sagarika, Anu and Bhavana\n- Closer to standing up slack as an independent service which will in the long run help with handling scale\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, - Bug backlog needs to be factored in along with features\n- Focus more on unit tests as that seemed to be the prominent RCA for bugs\nPrimary User, To improve our execution what should we DROP?, nan\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, We were able to clear some of the tech backlog which we weren't able to prioritise earlier\nPrimary User, To improve our execution what should we add?, Developers should add more system tests for the new features going in.\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan\nPrimary User, To improve our execution what should we add?, - Need to track and close Retro AIs more actively\n- Need to actively address failing system tests\nPrimary User, As a member of the Product Management team, how do you rate the quality and payload size of the release?, nan", "doc_id": "644372cf-8289-4a35-b825-b0e39065607b", "embedding": null, "doc_hash": "c887b232206a41195c5cf60cd00fe1bb0b7eff58ee1962b3612af232fe942f32", "extra_info": null, "node_info": {"start": 0, "end": 14279}, "relationships": {"1": "79afd613-bf19-4bfa-8ebe-75a2ee75b124"}, "__type__": "1"}}, "ref_doc_info": {"79afd613-bf19-4bfa-8ebe-75a2ee75b124": {"doc_hash": "c887b232206a41195c5cf60cd00fe1bb0b7eff58ee1962b3612af232fe942f32"}, "644372cf-8289-4a35-b825-b0e39065607b": {"doc_hash": "c887b232206a41195c5cf60cd00fe1bb0b7eff58ee1962b3612af232fe942f32"}}}} |