2798 hands-on tasks to practice real job skills - earn XP, build a track record, get noticed for internships.
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Find the line that computes the wrong average.
Find why remaining work grows instead of shrinking.
Find the wrong status check.
Find the integer division bug.
Find the sort bug.
Find the date calculation bug.
Find the wrong allowed value.
Find the unit error.
Find the security vulnerability.
Find the mutable default argument bug.
Find the index bug.
Find both faulty lines.
Sum all story points.
Average the six Sprint velocities.
Find the highest velocity.
Find the lowest velocity.
Count non-empty story names.
Count stories with status Done.
Sum points of Done stories.
Subtract completed from total.
Divide completed by total.
INDEX and MATCH the largest story.
Use SUMPRODUCT.
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
Read the chart and answer every question (70% correct to pass).
See which files changed.
Stage every modified file.
Commit with the message 'US-101 add login form'.
Push the branch to the remote.
List all local branches.
Fetch and merge the develop branch.
Show history one line per commit.
Make a directory called sprint-6.
Order the steps for introducing Scrum to a traditional team.
Rank coaching interventions from earliest to latest as a team matures.
Order the steps when the Product Owner and team disagree on scope.
Order steps to introduce team metrics responsibly.
Rank quality investments for the next two Sprints.
Order coaching steps for a team that has stopped holding events.
Identify the accountable role.
Choose the correct Daily Scrum timebox.
Pick the right facilitator responsibility.
Recall the Sprint timebox.
Choose who provides estimates.
Identify why a Sprint Goal exists.
Choose the acceptance role.
Handle a change request.
Identify who helps remove blockers.
Understand estimation units.
Decide what to do when a story is not finished.
Judge the Scrum Master's role.
Identify the Increment.
Choose the recommended team size.
Choose attendees.
Choose the right event.
Reduce meeting waste.
Choose useful measures.
Lead adoption.
Align teams.
Fit governance into Scrum.
Diagnose root causes.
Clarify accountability.
Encourage learning.
Bridge planning styles.
Protect team health.
Create a new branch for story US-101.
Arrange the Scrum events in the order they occur within a single Sprint.
Rank the Product Backlog items so the highest business value is first.
Put the Sprint Planning activities in the sensible order.
Order the steps a backlog item follows during refinement.
Rank the impediments the Scrum Master should tackle first.
Order the three Sprint Planning topics as described in the Scrum Guide.
Order the stages a user story passes through in Scrum.
Arrange a typical Daily Scrum flow.
Order these stories from smallest to largest effort.
Sequence the stages of a retrospective.