{"index_struct": {"__type__": "tree", "__data__": {"index_id": "cfeed0f7-92db-4500-9a14-af5939be59ea", "summary": null, "all_nodes": {"0": "29bd4833-4f9b-4160-ad23-2e8ce64037ab"}, "root_nodes": {"0": "29bd4833-4f9b-4160-ad23-2e8ce64037ab"}, "node_id_to_children_ids": {"29bd4833-4f9b-4160-ad23-2e8ce64037ab": []}}}, "docstore": {"docs": {"29bd4833-4f9b-4160-ad23-2e8ce64037ab": {"text": "Primary User, Were the requirements clear at the time you picked up your tasks?, nan\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, * Amazing work from data team in topic identification, summary generation for reports\n* Teams retro looks really cool terrific work by ui/ apps and collab team\n* Setting up VPN and updating code to re-route calls - this was a long pending task\n* Research in multi instance deployment\nPrimary User, What didn't go well in this release?, * Couldn't address all pabot related issues due to active changes happening in int \n* Lots of research topic for platform team this time (expected) - we should be closing on some these tasks in upcoming sprints\nPrimary User, To improve our execution what should we add?, * Tracking system tests and alerts in int and stage\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, Design specs really good with fast and clear communications. Ritu was very helpful with resolving any issues I found with APIs quickly.\nPrimary User, What didn't go well in this release?, Difficulty maintaining a proper development environment in parallel with one for dev testing for the teams unified experience meant that I did not have time to finish dev/ux review work satisfactorily before the branch cut. The result was having to work in a compromised way and under time pressure late in the day. I was under the impression that if a feature was not ready we were not going to push for it to be in.\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan\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., The requirements were again very clear for this release, specially for the apps tasks. Already had an overview of the features we were going to implement in this release as these were discussed previously.\nPrimary User, What went well in this release?, I think the inter-team dependencies were handled pretty nicely in this release. The data APIs to be consumed by apps were ready even before the release started (thanks to Seshan) and we were able to deliver the APIs to be consumed by UI before end of Sprint 3.\n\nThe bug bash sessions were again very successful and helped us to catch a lot of bugs and fix them in the dev cycle itself. Also, great idea by Ritu to use Slack Posts feature for creating E2E testing docs for various features which can be edited by everyone.\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, 1. We could completed dev testing for most of the features and fixed most of them fixed also that are being delivered in 0.9.9.\n2. Lesser # of major bugs in dev testing\n3. Two features in iFrame being worked on by 2 devs in Parallel.\n4. zero merge conflicts when merging main to develop in 0.9.9\nPrimary User, To improve our execution what should we add?, One of things we identified this release was slack post which can be edited by multiple people in the team. This is a good way to collaborate/track list of live items which are light weight and don't need jira/wiki. (Thanks Ritu for finding this option).\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What didn't go well in this release?, Nothing\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, Sentiment-analysis using with chatGPT , copilot .\nPrimary User, What didn't go well in this release?, Nothing\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, 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., Mostly clear for the current release but a bit hazy for the next release. We need to define rough roadmap for the next release also.\nPrimary User, What went well in this release?, This release as usual packed with full of features. Most of the features tested before branch cut. Our UI fit and finish and overall quality improved significantly compared to few old releases.\nPrimary User, What didn't go well in this release?, We started discussing improved error handling for our customer onboarding but only a little progress in overall improvement. We must invest more time in this to enable anyone to do onboarding without going through a very complex wiki page of steps with lots of if conditions.\nPrimary User, To improve our execution what should we add?, Most of the time, we face issues with feature builds deployed in INT. If multiple developers need to work on the same service, that is even more complicated. We need to start planning a better solution to accommodate this internal requirement. Until then, we need to follow the best practices like keep rebasing and changing the builds after testing is done etc.\nPrimary User, To improve our execution what should we DROP?, We must eliminate manual steps as much as possible in all places, specifically deployments and onboarding. For the data team, we need to automate the Druid schema management. Every time there is a schema change, deployment is not going smoothly due to this manual step.\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\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 complete the collab changes to support unified teams experience and teams retro surveys. Completed the implementation for the template driven actions and its slack support.\nResolved quite a few tech debt items from collab board.\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., We have a definite template, process and clean designs in place when we plan or start test cycle\nPrimary User, What went well in this release?, - Major features wrapped up early and dev tested before delivering to QA\n- Automated tests for ongoing release features\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, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, Delivered all the planned items with minimum spillover\nPrimary User, What didn't go well in this release?, nan\nPrimary User, To improve our execution what should we add?, we can do a little more dogfooding to uncover issues around usability. e.g actions / brokering between PMs and dev teams\nPrimary User, To improve our execution what should we DROP?, nothing\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., Had some last minute changes for Retro. Nothing major.\nPrimary User, What went well in this release?, Multiple features got implemented (unified exp, retro, addr book, action templates) - good release overall.\n\nTeam meet was good - had a few productive technical discussions\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\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, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, Tasks related to lambda VPC integration\nPrimary User, What didn't go well in this release?, Lambda testing takes a lot of time right now as we don't have unit tests. Basically you have to wait for two pipelines to pass (libs and lambda function) and then wait for the deployment to happen before you can detect any sort of bug\nPrimary User, To improve our execution what should we add?, Unit tests for lambdas\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan\nPrimary User, What went well in this release?, Quite a few features were delivered in this release despite the fact that a few engineers were unavailable (on PTO).\nPrimary User, To improve our execution what should we add?, I would perhaps like to see more ownership from each and everyone for the features they are working on and think through the story they are working on even though the spec doesn't have all the details\nPrimary User, To improve our execution what should we DROP?, Nothing\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, UX reviews of Qualitative comments(Topics), very quick response by @meaghan during reviews. \nMerge strategy instead of rebase helped merge HFs and Develop branch real quick. \nTeam Outing :)\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, Were the requirements clear at the time you picked up your tasks?, Mostly clear\nPrimary User, What went well in this release?, - Good progress on OpenAI topics and summarization\n- Lots of learnings - Prompt Engineering , llamaindex , langchain\nPrimary User, What didn't go well in this release?, - druid issues  like joins , schema refresh -  had to add workarounds to bypass the issue\n- missed out on druid spec sync issues between environments during deployment\n-\nPrimary User, To improve our execution what should we DROP?, 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?, High level progress view is missing I guess now. So EPICs tagging will help here\nPrimary User, Were the requirements clear at the time you picked up your tasks?, Crystal clear\nPrimary User, What went well in this release?, Focussed effort on making existing features more robust along with shipping of new features like Retro and Address Book\nPrimary User, What didn't go well in this release?, - Identified a few scale related issues with use cases around pulse delivery and adding users to PVT\n- Identified some bad patterns in the way DB tables are queried without the right constraints\nPrimary User, To improve our execution what should we add?, - Focus on onboarding improvements and error messaging\n- More attention to system test regressions\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 collaboration across teams, user facing channel threads are helpful \n- Getting faster response on UX, thanks & kudos to Meaghan\n- Dev testing is coming as a very helpful exercise. Though we are spending time to come together and test but these are really fruitful sessions to align all the teams on the same page.\nPrimary User, What didn't go well in this release?, - There are few pockets of time in the sprint when apps/ui cannot proceed as we have backend dependency or some pending answers from UX/Product. We need to keep other minor task preplanned for such time period. This falls back to planning better.\nPrimary User, To improve our execution what should we add?, - More detailed decomps\nPrimary User, To improve our execution what should we DROP?, - None\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan\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?, -\nPrimary User, What didn't go well in this release?, -\nPrimary User, Were the requirements clear at the time you picked up your tasks?, nan", "doc_id": "29bd4833-4f9b-4160-ad23-2e8ce64037ab", "embedding": null, "doc_hash": "0c17c6ec2e952e172dfaa5c397e5ef71937584e96c782473ec02d2ae41d8df90", "extra_info": null, "node_info": {"start": 0, "end": 13334}, "relationships": {"1": "885b63ff-1776-4a2d-a399-e641c0af75cc"}, "__type__": "1"}}, "ref_doc_info": {"885b63ff-1776-4a2d-a399-e641c0af75cc": {"doc_hash": "0c17c6ec2e952e172dfaa5c397e5ef71937584e96c782473ec02d2ae41d8df90"}, "29bd4833-4f9b-4160-ad23-2e8ce64037ab": {"doc_hash": "0c17c6ec2e952e172dfaa5c397e5ef71937584e96c782473ec02d2ae41d8df90"}}}}