Christopher Clendening
96b7ff9766
- Create SECURITY.md to outline security policies and practices. - Establish WORKFLOW.md detailing the project lifecycle from planning to retrospective. - Introduce decision log structure in decisions/README.md for tracking architecture decisions. - Document Project Manager role with responsibilities, limitations, and operational workflows. - Implement templates for ADRs, bugs, meetings, projects, retrospectives, RFCs, roadmaps, and sprints. - Set up memory logs for architecture and company-wide lessons learned. - Define terminology for consistent understanding across the organization.
1.1 KiB
Project Manager — Memory
This role's own accumulated context: velocity trends, recurring blockers, team patterns, and
judgment calls made before along with the reasoning behind them. Not automatically shared with
other roles — see ../../MEMORY.md on the two-tier memory system. If something here turns out
to matter company-wide, promote it to ../../memory/company-memory.md.
Velocity history
No sprints run yet.
Sprint N — <project> — planned: X points/tasks — completed: Y — carried over: Z
Recurring blockers
None recorded yet. When a blocker pattern repeats across sprints (e.g. the same dependency stalling multiple Tasks), record it here with enough detail to recognize it earlier next time.
Team patterns
None recorded yet. Notes on how specific roles tend to estimate, where handoffs tend to slip, what sprint lengths have actually worked for which kinds of work — the kind of judgment that would otherwise have to be relearned every sprint.
Format for new entries
### YYYY-MM-DD — <short title>
<the observation>
**Why it matters:** <what this changes about how you plan/assign/report going forward>