Projects: Agile Delivery — Assessment

1. A sprint ends with three tasks unfinished. What happens when you complete the sprint?

The three tasks are carried back to the backlog automatically The sprint cannot be completed until they are finished The three tasks are deleted The three tasks are marked done to keep velocity high

2. Where does the burndown chart get its data?

Manually entered remaining-work figures Computed on the fly from task completion timestamps An external analytics service A nightly snapshot job that must be scheduled

3. Do sprints use a separate set of "agile items" distinct from tasks?

Only on the Enterprise plan Only if the project has custom statuses Yes — you re-create each task as an agile item No — a sprint organises the same tasks, so metrics and project progress agree

4. How is velocity calculated?

Hours logged during the sprint Completed story points per finished sprint, plus a rolling average The project owner's manual estimate The number of tasks created during the sprint

5. A team's sprints keep carrying a lot of work back to the backlog. What does that most likely indicate?

A bug in the burndown calculation The team is over-committing at planning — an honest planning signal Carry-over should be disabled The tasks are too small

Your details for the certificate

This is the name that will appear on your certificate.

Full name

Email

We email your result to this address with a link to confirm it is yours. If you are signed in, or once you confirm, the administrators of an organisation this email belongs to on AWRA OpsHub can see your attempts and certificate. Your name is as you type it here; only the email is confirmed.

Graded server-side. No peeking at answers in the page source.