Skip to content

Commit 00a1aab

Browse files
gregorrieglerNateHermanblaisepMichaelRWolfnitsanavni
committed
. d Session notes (for FizzBuzz dojo in Cojure part 2)
Co-Authored-By: Nathaniel Herman <nathaniel.herman@gmail.com> Co-Authored-By: Blaise Pabon <blaise@gmail.com> Co-Authored-By: Gregor Riegler <rieglerg85@gmail.com> Co-Authored-By: Michael R. Wolf <MichaelRWolf@att.net> Co-Authored-By: Nitsan Avni <nitsanav@gmail.com> Co-Authored-By: Joel Silberman <42779942+jcs-instructor@users.noreply.github.com> Co-Authored-By: 4dsherwood <4dsherwood@users.noreply.github.com>
1 parent 509b0be commit 00a1aab

File tree

5 files changed

+234
-3
lines changed

5 files changed

+234
-3
lines changed

‎docs/backlog.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
- Review the Ideas section of the [previous session notes](../session-notes/_previous-session-notes.md)
55
- Everyone: turn on mob timer sounds 📣
66
- Before Retro: Update the Backlog
7+
- Consider a 10 minute mid-session retro
8+
- Thumbvote feedback on the mid-session retro
79

810
## Working Agreements
911

‎session-notes/_previous-session-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
/workspace/mob-programming-rpg/session-notes/session-notes-2023-11-23.md
1+
/workspace/mob-programming-rpg/session-notes/session-notes-2023-12-07.md

‎session-notes/_todays-session-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
/workspace/mob-programming-rpg/session-notes/session-notes-2023-12-07.md
1+
/workspace/mob-programming-rpg/session-notes/session-notes-2023-12-14.md

‎session-notes/session-notes-2023-12-07.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,4 +81,18 @@ What to do next? Vote on Proposals:
8181
- 1. spending less time deciding on what we're doing (more time coding)
8282
- 2. shared leadership, dedicated facilitation
8383
- 3. consider a checklist for newcomers (was a discussion about this)
84-
- 4. consider items in the backlog (reminders, what are we working on, etc.)
84+
- 4. consider items in the backlog (reminders, what are we working on, etc.)
85+
86+
# Approximate timings of prior session:
87+
88+
Itemized:
89+
- Discuss/decide: 50 min.
90+
- Coding: 55 min.
91+
- Retro 1: 25 min.
92+
- Coding: 35 min.
93+
- Retro 2: 15 min.
94+
95+
Summary:
96+
- Coding: 50% (90 min.)
97+
- Discuss/Decide: 28% (50 min.)
98+
- Retros: 22% (40 min.)

‎session-notes/session-notes-2023-12-14.md

Lines changed: 215 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,215 @@
1+
# Session Date: 2023-12-14
2+
## Facilitated by
3+
- Joel Silberman
4+
5+
## Active Co-Authors
6+
Co-Authored-By: Nathaniel Herman <nathaniel.herman@gmail.com>
7+
Co-Authored-By: Blaise Pabon <blaise@gmail.com>
8+
Co-Authored-By: Gregor Riegler <rieglerg85@gmail.com>
9+
Co-Authored-By: Michael R. Wolf <MichaelRWolf@att.net>
10+
Co-Authored-By: Nitsan Avni <nitsanav@gmail.com>
11+
Co-Authored-By: Joel Silberman <42779942+jcs-instructor@users.noreply.github.com>
12+
Co-Authored-By: 4dsherwood <4dsherwood@users.noreply.github.com>
13+
14+
# Agenda
15+
16+
## Bond (15 min.)
17+
18+
- Try a [warmup exercise](../docs/warmup-exercises.md)
19+
20+
## Discussing Mid Session Retro 15min
21+
...
22+
## Work the Backlog (75 min.)
23+
24+
### Items we could do
25+
1. Review Pull Request from Michael
26+
2. Continue Commit message generator
27+
3. Show and Tell instead of review Michaels Pull Request
28+
4. Align backlog and readme (overall doc) to reflect what we are doing (4)
29+
5. Kata and record it and publish it
30+
6. Continue Kata from last week (6)
31+
7. Make GPT do something new
32+
33+
### We voted on // at 15:50
34+
1. Continue [kata](https://cyber-dojo.org/kata/edit/EtbGU6) from last week
35+
2. Align backlog and readme (overall doc) to reflect what we are doing
36+
37+
Everybody has 3 points give me in chat like this: Examples: 123 or 111 or 445
38+
39+
---
40+
41+
## mid session retro at 16:26
42+
43+
(change direction? open ended)
44+
45+
Blaise - no input
46+
Gregor - like the coding! and fluency of it. we have a drive, focus, getting to decisions quicker. still not very easy
47+
Diana - like the flow, the way we're conducting our work, made space for people to see and observe how we work with each other
48+
Michael - feel good about momentum. helping: Joel spoke out loud - "anybody can propose and speak, but the Talker decides. Keeps things moving.
49+
Nathen - losing focus, then regaining. appreciate how people are clear and explaining. let's keep going
50+
Nitsan - more friction than we have usual, but creating space for everybody which I like. I am ready to refactor the hell out of the code
51+
Joel - like that we tied a 10m retro, pleased with the way it's going, like that we've picked up from last time
52+
53+
54+
more notes from Diana:
55+
56+
Michael suggested:
57+
<Let's do a small step> Make a helper function that is called is-divisible-by-15
58+
Gregor: I hear the 15 suggestion and I want to just make a generic function
59+
After we did implemented the “is-divisible-by” function
60+
61+
Gregor heard Michaels suggestion
62+
And decided to go another way
63+
64+
65+
Gregor as typer said: I still have my paste buffer
66+
67+
68+
JOEL did well
69+
Tre-state the timing
70+
Do differently: make a specific request:
71+
Gregor could you please check the code in?
72+
Could be during his typing or as a sidebar
73+
74+
---
75+
76+
77+
- Consider checking the recent `git log -p`
78+
- Check the [global backlog](../docs/backlog.md)
79+
80+
## Leave Breadcrumbs (5 min.)
81+
82+
- Update the [global backlog](../docs/backlog.md)
83+
84+
## Reflect / Retro (25 min.)
85+
Format
86+
1. Practice 10-minute (1 min/person) mid-session retro
87+
2. More. Old format || fre-form. 10 minutes.
88+
89+
90+
### Round 1 - 10-minute (1 min/person) format
91+
- Nitsan - Happy about many things. Clojure+++.
92+
- Plus - Hearing all voices for decision making
93+
- Plus - Facilitation keeps us on track
94+
95+
- Nat - Continues to like TDD-talk and thought process.
96+
97+
- Gregor - Time-box retro forces prioritization.
98+
- Like - Strong facilitation. Decisions quicker.
99+
- Like - Unstructured retro allows better answers. Questions not needed.
100+
101+
- Joel -
102+
- Worked well - typing proposal first
103+
- Intersting - how we got 6 to vote on. Instead of finger voting.
104+
105+
106+
- Michael
107+
- Strong facilitation, shared leadership. Sometimes strong facilitation gets in the way, sometimes it helps.
108+
- Dont always like voting.
109+
- Sometimes prefer voices.
110+
- Happy about things going fast.
111+
112+
### Round 2 -
113+
114+
What might we do differently?
115+
116+
- Michael - Rotate facilitator (with goal of self-facilitation as a goal).
117+
- Nitsan - Plus-one for Michael's proposal for rotating facilitator. OK putting back training wheels.
118+
- Gregor - Plus-one for rotating facilitator.
119+
- Nate - Ditto
120+
- Gregor - Allowing facilitation speeds up decision making.
121+
- Michael - Yes... AND sometimes it slowed it down.
122+
- Joel - SM-like-person's goal is to grow team's abilities.
123+
- Explicit role definitions (and goals) - Talker, Typer, Facilitator
124+
125+
126+
127+
What is structure for this next few minutes???
128+
129+
# Rotating facilitator
130+
131+
As we rotate facilitatiors, we will learn and experience different styles. Will eventually "normalize". Feedback to facilitator. As goal to learn.
132+
133+
Observation - As facilitator, focus is different. Not able to focus on chat. Did focus on mob flow. Didd consensus-building.
134+
135+
Voting - Too much? (Michael - YES!). Does this imply non-alignment? Important to balance talking vs doing.
136+
137+
Observation - It is helpful to do back-to-back facilitation to learn on 2nd turn. Doing that could take a long time to roll back around.
138+
139+
Expectations of facilitator
140+
- Delegating "helper roles" (e.g. timer, researcher)
141+
142+
Actions:
143+
- Get facilitator chosen early (either in previous session, or QUICKLY at beginning).
144+
- Nitsan will step up for next week.
145+
- Inspect-and-adapt for subsequent weeks.
146+
147+
148+
# Other topics
149+
150+
- Nitsan
151+
Would this session recording have been instructive to others?
152+
153+
Observation
154+
- Recording all, then finding good segments. Good to hightlight some ideas
155+
- There are no good videos out there to get a feel for what it is (other than reading.... but that's not the same as the experience).
156+
- Pulling out segments to commett on would be helpful to others.
157+
- ... and to ourselves (like sports teams)
158+
159+
Next step:
160+
- Keep it in the backlog.
161+
- Gregor will test solution for recording.
162+
163+
164+
Joel
165+
-
166+
167+
- Gregor
168+
169+
170+
171+
172+
173+
Roles:
174+
- Facilitator
175+
- Talker
176+
- Typer
177+
- Mob
178+
179+
180+
181+
182+
### How did that feel?
183+
184+
### What worked well, we want to do more of it?
185+
186+
### Ideas
187+
188+
- Consider creating a backlog item if the idea is something we want to implement in a future mobbing session in [global backlog](../docs/backlog.md)
189+
for an idea (that was generated at this retro).
190+
191+
## Summary (Generated by ChatGPT)
192+
193+
Useful command for today's changes:
194+
195+
```shell
196+
git diff --ignore-all-space `git log --since="1 day ago" --pretty=format:%H | tail -1`
197+
```
198+
199+
Useful prompts:
200+
201+
```
202+
Here are all the changes made to the repo during a single mob programming session
203+
204+
could you please summarize what happened?
205+
what are some main points from the retro that was help at the end?
206+
```
207+
208+
```
209+
here are notes from today's mob programming session retro.
210+
Infer values of the team.
211+
212+
{
213+
$notes
214+
}
215+
```

0 commit comments

Comments
 (0)