blob: 440c14e509da2c19f1f141c0fa1c44de35829e33 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
#+TITLE: Retrospective Workflow
#+DESCRIPTION: How to run a retrospective after major problem-solving sessions
* When to Run a Retrospective
Run after:
- Major debugging/troubleshooting sessions
- Complex multi-step implementations
- Any session where significant friction occurred
- Sessions lasting more than an hour with trial-and-error
* The Process
** 1. Trigger the Retrospective
Either party can say: "Let's do a retrospective" or "Retrospective time"
** 2. Answer These Questions (Both Parties)
*** What went well?
Identify patterns worth reinforcing. Be specific.
*** What didn't go well?
Identify friction points, mistakes, wasted time. No blame, just facts.
*** What behavioral changes should we make?
Focus on *how we work*, not technical facts.
- Good: "Confirm before rebooting"
- Not behavioral: "AMD needs firmware 20260110"
*** What would we do differently next time?
Specific scenarios and better approaches.
*** Any new principles to add?
Distill lessons into short, actionable principles for retrospective/PRINCIPLES.org.
** 3. Copy and Update retrospectives/PRINCIPLES.org
Copy the template retrospectives/PRINCIPLES.org.
Using the copied template, add new behavioral principles learned. Keep them:
- Short and actionable
- Focused on behavior, not facts
- Easy to remember and apply
** 4. Create Retrospective Record
Save to =docs/retrospectives/YYYY-MM-DD-topic.org= with:
- Summary of what happened
- Answers to the questions above
- Link to detailed session doc if exists
** 5. Commit Changes
Commit PRINCIPLES.org updates and retrospective record.
* PRINCIPLES.org Structure
#+BEGIN_SRC org
,* How We Work Together
,** Principle Name
- Bullet points explaining the principle
- When it applies
- Why it matters
,* Checklists
,** Checklist Name
- [ ] Step 1
- [ ] Step 2
#+END_SRC
* Integration with Session Startup
Add to project's protocols.org or session startup:
- Check if PRINCIPLES.org was updated since last session
- Review any new principles before starting work
* Example Principles (Starters)
** Sync Before Action
- Confirm before destructive or irreversible actions
- State what you're about to do and wait for go-ahead
** Verify Assumptions
- When something "should work" but doesn't, question the assumption
- Test one variable at a time
** Clean Up After Yourself
- Reset temporary changes before finishing
- Verify system is in expected state
|
