Ads API Sprint Runbook + E2E Development Process

A detailed illustration of a software development sprint planning meeting with team members discussing sprint tasks, whiteboards filled with project plans, and a focus on Agile methodologies.

Ads API Sprint Runbook Quiz

Test your knowledge and understanding of the Ads API Sprint Runbook and E2E Development Process. This quiz is designed to help you reinforce your learning and ensure you grasp the best practices involved in sprint planning, task management, and implementation.

Features of the quiz:

12 engaging questions
Covers a wide range of topics related to sprint planning
Immediate feedback on your answers

12 Questions3 MinutesCreated by StrategizingCoder92

Which statement best reflects how secondary oncall should do sprint planning:

Secondary oncall should prioritize being available for urgent issues, including scheduled production deploys and major inbound bugs.

Secondary oncall should take on tasks from the groomed non-project backlog and avoid project tasks that may put projects at risk if the task is not completed during the sprint.

Secondary oncall should plan for a normal sprint, but make themselves available to help any urgent issues as needed.

What is the best practice when handling shepherding tasks? Select all that apply.

Shepherding tickets should be tracked as sprint tasks with an epic assigned to the parent project.

Shepherding requests should always be prioritized to unblock product engineering teams.

Unplanned requests should be routed to the team's office hours.

Shepherding work shouldn't be accounted for in sprint planning.

When estimating story points for a task, it is best to account for:

Just core engineering work.

Core engineering work + testing.

Core engineering work + testing + documentation.

What does 'SPADE' mean? Select all that apply. (hint: there are no wrong answers)

A tool primarily for digging consisting of a long handle and blade, typically with the blade narrower and flatter than the common shovel.

Revenue Platform and Developer Experience

$ Platform and Developer Experience

A trick-taking card game devised in the United States in the 1930s.

One story point = an ideal developer day. What is an ideal developer day as defined in the sprint guidelines doc?

The average amount of time per day that an engineer typically spends on focused work.

An 8 hour day.

A day with no meetings, escalations, or bug fixes.

A Saturday.

The purpose of standups is to (select all that apply):

Provide a status update.

Ensure everyone on the team has the support they need to complete their sprint work.

Create a daily checkpoint to raise blockers, unexpected tasks, and ask questions.

Create accountability and keep top of mind the tasks and goals we set out for that sprint.

What are some best practices when making changes to a sprint (select all that apply):

Ensure with the EM/TL and requester that new work cannot be deferred to the next sprint.

When adding Story Points, remove tasks that are the same number of Story Points.

When removing a task that can no longer be done, check if team members need help with tasks and if there's not a place to help, add task(s) of equivalent size.

As you progress through a task, update the task story points to reflect the remaining work.

Of the following options, which is NOT a project lead responsibility.

Ensure that only one person is working on a given project at a time.

Provide milestones, and target/actual dates for milestones in JIRA epic.

Have epics tasked out in JIRA and sequenced for a few upcoming sprints

On Friday prior to sprint planning, add tasks for the project to next sprint

Define the main sprint deliverable(s) to add to sprint goals in JIRA and to share with the team.

Of the following, what should come first when a product eng team is building on Ads API?

Ensure your project has factored in resources from Ads API Eng, QE, and Partner Engineering by filing epics using go/jira/adsapi, go/jira/ctatd and go/jira/ape. Attach these tickets to your project.

Clone and fill in the template design document (go/ads-api-design-review-doc).

Verify the correct rate limits are configured for new API endpoints.

What should be considered in the design review process? Select all that apply.

Small changes/updates with minimal scope of impact will be discussed, resolved and approved async via document comments.

If anyone believes the project deserves deeper discussion a design review meeting will be scheduled. These take place during Ads API Office Hours.

Design doc iteration, further discussion through comments or follow up design review meetings may be required for large projects with wide scope of impact.

The assigned partner engineer will be responsible for formally communicating review status (e.g., Approved) via email or Jira, as well as communicating follow up action items.

In the implementation phase of Ads API endpoint development, what should the SWE lead do? Select all that apply.

Add the review committee to the diff, so that they are exposed to the code change.

Update the design doc to include any remaining work to be completed. For example: feature improvement, code refactor, removing deciders.

For externally available APIs, verify the endpoints are accessible with non-TOO app tokens. For internal only APIs, verify they are not.

Verify app privileges and account features are controlling access as expected.

Ads API Sprint Runbook + E2E Development Process

Ads API Sprint Runbook Quiz

More Quizzes