Projects: Agile Delivery — Assessment

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

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

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

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

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