6.5. Reflection Checkpoint

Key Takeaways

• GitHub Projects is a flexible planning layer that can pull items from multiple repositories and display them as a board, table, or roadmap — the same items, viewed different ways.
• Labels categorize items, milestones group them toward a target with an automatically calculated completion percentage, and Project workflows automate field updates in response to events.
• Assignees own seeing an issue or pull request through to completion; reviewers are specifically asked to evaluate a pull request's changes — the two roles aren't interchangeable.
• Project insights chart a Project's own status-field history (velocity, bottlenecks), separate from repository-level Insights covered in Phase 3.

Connecting Forward

Phase 7 shifts from planning to protecting: how accounts are secured, how access is controlled at the repository and organization level, and what Enterprise Managed Users and org-wide policy add on top.

Self-Check Questions

• Why does representing a Project's layout as a "view" rather than the data itself matter when a team wants both a board and a table for the same work?
• If a milestone shows 100% completion, what does that guarantee — and what does it not guarantee — about the quality of the work inside it?