Using the work log in Daily Standups
Using the review workflow in Daily standups
Using the Daily Update in Daily standups
Summary and recap
For further information, see Daily Standups.pdf.
How is the Daily update report most commonly used in Standups?
- To help the team quickly surface discussions around code-level blockers.
- To find team collaboration patterns.
- To visualize commit, ticket, and PR activity in one unified view.
What does the Review workflow report show?
- A visualization of team work patterns over time.
- A unified view of all the team’s open PRs over the selected time period.
- A set of metrics that give a high-level view of how the team is leveraging the code review process.
What are the defining characteristics of high-activity pull requests?
- PRs that are seeing a lively discussion, likely with a number of reviewers participating, but the discussion has continued for a while and doesn’t seem to be driving toward a resolution.
- PRs that are larger in size, with a higher level of Review coverage.
- PRs that have a higher than average number of follow-on commits.
What are the defining characteristics of long-running pull requests?
- PRs that were submitted near the end of a sprint after the main PR was approved.
- PRs that have been open for a while, where there was some back-and-forth discussion between team members that was followed by silence.
- PRs that have been open for a while but haven’t received any comments or an approval.
See LC M3_ Standups.pdf for correct answers.
If you need help, please email email@example.com for 24/7 assistance.