Skip to content

Commit 398977b

Browse files
committed
update agendas
1 parent 608b79e commit 398977b

File tree

1 file changed

+70
-33
lines changed

1 file changed

+70
-33
lines changed

management/agendas.qmd

Lines changed: 70 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -14,73 +14,110 @@ Use the following checklist to keep your agenda repository a practical, living r
1414

1515
## 1. Make the agenda your own
1616

17-
- [ ] Keep in mind: the agenda will remain a private repository, shared between you and your supervisor.
18-
- [ ] Treat the agenda as a shared but informal working document (no perfection needed).
19-
- [ ] Adapt the structure to your personal workflow.
20-
- [ ] Use it regularly as your primary planning resource.
17+
- [ ] Keep in mind: the agenda will remain a private repository, shared between you and your supervisor.
18+
- [ ] Treat the agenda as a shared but informal working document (no perfection needed).
19+
- [ ] Adapt the structure to your personal workflow.
20+
- [ ] Use it regularly as your primary planning resource.
2121

2222
---
2323

2424
## 2. Update the agenda regularly
2525

26-
- [ ] Define and revisit shared goals ([objectives and key results (OKR)](TODO)) together.
27-
- [ ] Maintain a list of major ongoing projects.
28-
- [ ] Keep a running “Items to Discuss” section.
29-
- [ ] Maintain a weekly task list:
30-
- [ ] Check off completed items.
31-
- [ ] Copy unfinished items to the next week.
26+
- [ ] Define and revisit shared goals ([objectives and key results (OKR)](TODO)) together.
27+
- [ ] Maintain a list of major ongoing projects.
28+
- [ ] Keep a running “Items to Discuss” section.
29+
- [ ] Maintain a weekly task list:
30+
- [ ] Check off completed items.
31+
- [ ] Copy unfinished items to the next week.
3232
- [ ] Share a link to meeting notes before the meeting.
33-
- [ ] Add meeting notes directly after each meeting.
33+
- [ ] Add meeting notes directly after each meeting.
3434

3535
---
3636

3737
## 3. Create a clear overview
3838

39-
- [ ] Keep orientation easy: structure before detail.
40-
- [ ] Use folders and multiple documents where helpful.
41-
- [ ] Add internal links between sections.
42-
- [ ] Link to relevant external resources (repos, docs, papers, courses).
43-
- [ ] Ensure the agenda can be understood quickly by all participants.
39+
- [ ] Keep orientation easy: structure before detail.
40+
- [ ] Use folders and multiple documents where helpful.
41+
- [ ] Add internal links between sections.
42+
- [ ] Link to relevant external resources (repos, docs, papers, courses).
43+
- [ ] Ensure the agenda can be understood quickly by all participants.
4444

4545
---
4646

4747
## 4. Maintain a timeline and planning view
4848

49-
- [ ] Create Mermaid timelines (Gantt charts).
50-
- [ ] Track contracts and important deadlines.
51-
- [ ] Keep an overview of workload / hours.
52-
- [ ] Plan development goals (topics, methods, skills).
53-
- [ ] Map current and future projects over time.
49+
- [ ] Create Mermaid timelines (Gantt charts).
50+
- [ ] Track contracts and important deadlines.
51+
- [ ] Keep an overview of workload / hours.
52+
- [ ] Plan development goals (topics, methods, skills).
53+
- [ ] Map current and future projects over time.
5454

5555
---
5656

5757
## 5. Anticipate and track key periods
5858

59-
- [ ] Note upcoming vacations.
60-
- [ ] Mark exam phases or teaching peaks.
61-
- [ ] Maintain “waiting-for” items (e.g., reviews, decisions, responses).
62-
- [ ] Maintain “upcoming” items (projects, papers, milestones).
59+
- [ ] Note upcoming vacations.
60+
- [ ] Mark exam phases or teaching peaks.
61+
- [ ] Maintain “waiting-for” items (e.g., reviews, decisions, responses).
62+
- [ ] Maintain “upcoming” items (projects, papers, milestones).
6363

6464
---
6565

6666
## 6. Document interests and ideas
6767

68-
- [ ] Keep a section for research and teaching interests.
69-
- [ ] Collect ideas for new projects.
70-
- [ ] Use this as input for strategic discussions about next steps.
68+
- [ ] Keep a section for research and teaching interests.
69+
- [ ] Collect ideas for new projects.
70+
- [ ] Use this as input for strategic discussions about next steps.
7171

7272
---
7373

7474
## 7. Document and celebrate success
7575

76-
- [ ] Record accepted/published papers.
77-
- [ ] Add positive student feedback.
78-
- [ ] Note milestones and accomplishments.
79-
- [ ] Use this as a basis for CV building and reference letters.
80-
- [ ] Regularly reflect on progress to stay motivated.
76+
- [ ] Record accepted/published papers.
77+
- [ ] Add positive student feedback.
78+
- [ ] Note milestones and accomplishments.
79+
- [ ] Use this as a basis for CV building and reference letters.
80+
- [ ] Regularly reflect on progress to stay motivated.
8181

8282
:::
8383

84+
## How We Use the Agenda in Meetings
85+
86+
### 1. Review Session (Looking Back)
87+
88+
At the beginning of each meeting, we:
89+
90+
- Review the weekly task list
91+
- Check off completed items
92+
- Reflect briefly on progress toward shared objectives
93+
- Discuss blockers or “waiting-for” items
94+
- Add short notes directly into the repository
95+
96+
The agenda is updated live during the meeting.
97+
98+
### 2. Planning Session (Looking Ahead)
99+
100+
In the second part of the meeting, we:
101+
102+
- Define or adjust objectives together
103+
- Break down larger goals into concrete next steps
104+
- Clarify responsibilities and expectations
105+
- Identify priorities for the coming week
106+
- Add new tasks directly to the weekly section
107+
108+
This ensures alignment and clear next actions.
109+
110+
### 3. Use of Issues and Links
111+
112+
To avoid duplication and keep information structured:
113+
114+
- Use GitHub issues for well-defined tasks and discussions
115+
- Link issues directly in the agenda
116+
- Link to relevant repositories, documents, datasets, or papers
117+
- Use the agenda as a coordination hub — not as a storage location
118+
119+
The agenda serves as a shared navigation layer across distributed work.
120+
84121

85122
## Template
86123

0 commit comments

Comments
 (0)