DRs/Epic
Grooming
Miscellaneous
Customer Bug
Jira
100

This person holds the mighty power to set the fix version for a Dependency Request (DR)

Engineering Manager

100

When is it time to wave the "global impact" flag on an epic, and who’s responsibility to make it official?

The time the epic is committed

100

How often Droplets release their monthly releases.

Soft Release:  Last Thursday of the previous month

Bug fixes for next 2 weeks

Final Release: 2nd Thursday of the  month

100

What is the understanding of customer bug, and who raises the customer bugs

GCS team raised the customer bug

100

How often an epic marked for a release requires update?

When ever there is an update on epic.

200

When another team drops a new DR on our doorstep, this team’s job is to strategically solve, sweat, and maybe sigh.

Development Team

200

What is the meaning of Epic/DR committed?

Epic/Dr has a fixed version field decided.

200

What’s the most popular ‘debugging tool’ that we all secretly rely on every day?

Googling the error message and praying someone else had the same issue!

200

What is the timeline to react to P1/P2/P3 customer bugs?

P1/P2/P3 any customer bug, as soon as possible reaction is required

200

What is the timeline to update JIRA for P0/P1/P2 bugs.

whenever there is progress. Or update if there is no progress.

300

This robust component library delights developers with a steady stream of innovation, boasting 12 annual releases. What is the name of this library known for keeping the UI fresh and developers on their toes?

Droplets

300

Mention 3 points from Dev Outlook And QA Outlook those are required as part of grooming exercies.

Dev Outlook

Clarifications with PM, Dependencies Identification , T-Shirt estimate, Solution Overview Wiki , Design Doc, Design review with PM, UI, QA, UX, Doc, COGS Approval, UX Screens , Stories Creation , Code Completion , Developer Demo

QA Outlook

Share P0 tests with Dev , Story Creation , STS Review Internal (with QA), STS Review External (with PM, Dev, UI, Doc) , QA Track and Zephyr Upload , Upgrade Impact , Automation , Feature Demo , Cross-Team impact? Need to create DR's , Review Dev Unit tests , Review Dev Integration tests:

300

Who should be responsible for initiating the conversation on EBF

Engineering Manager

300

As an individual contributor how to decide the priority to work on a P2 customer bug OR a P1 release bug

Manager decides the priority

300

What is the main purpose to provide the Jira comment?

To communicate progress of epic/story to stakeholders.

400

In the realm of project management, when faced with another team's reluctance to accept a Delivery Requirement (DR) for a high-priority epic from the platform team, what is the advised protocol to ensure resolution, emphasizing persistent action until the matter is conclusively settled

Escalate the issue to a higher level continuously until closure is achieved

400

Grooming needs to be done at epic level or story level.

Epic level grooming

400

What is the criteria for giving signoff on a staging environment?

No more functional validation happens, only pod validation and ui pages loading. Run zdt tests and pipeline testing

400

This is what you call the feeling when your code works perfectly on local but fails spectacularly in production.

Developer’s Optimism

400

What are the things envolved in your daily activity need not be tracked in Jira? And when they become eligible to get tracked in Jira.

Upto you

500

In project management, if an Epic or DR has a fix version assigned but cannot be addressed due to shifting priorities or unforeseen challenges, what action is permissible to formally manage scope adjustments and project timelines?

Ask for Change Control Request (CCR)

500

How often we should do the grooming of epics in a release?

Whenever there is a requirement. Because sometimes we do have late entries of epics.

500

What is the timeline to deliver an ebf

As soon as possible

500

What is the process to close a customer bug

Same process like a normal bug

500

Whose responsiblity is to get update on Jira ticket, if there is no progress?

Everyone's responsibility. Anyone in the team can ask for the update if they find no progress on ticket.