Jeff Miller (orange hatband)Mar 6
#aonw Opening Circle. April Jefferson with a reminder and an introduction to
Open Spaces, 5 Principles, 1 Law; butterflies, honeybees, ...and how to pull sticky notes without curling.
Show threadJeff Miller (orange hatband)Mar 6
Elevator pitches for Open Spaces topics at AONW. 4 corners of the gym, 2 spaces in each of 2 classrooms, the library, and "wherever".
Show threadJeff Miller (orange hatband)Mar 6

perpetual retrospective space on the large landscape decorated board - ok to put stickies.

colored balloons marking gathering spaces in larger rooms (2x or 4x)

#aonw

Show threadJeff Miller (orange hatband)Mar 6
For session notes, see LinkedIn under the hashtag #aonw2026 . (AONW org: https://www.linkedin.com/company/agile-open-northwest )
AGILE OPEN NORTHWEST | LinkedIn

AGILE OPEN NORTHWEST | 397 followers on LinkedIn. AONW is an annual conference about agile practices and techniques. | AONW is an annual conference about agile practices and techniques. Using Open Space, the participants themselves make the conference they want to attend. Come prepared to share your latest ideas, challenges, hopes, experiences and experiments!

Show threadJeff Miller (orange hatband)Mar 6
Topics for the sessions are moderately heavy on LLMs and agentic techniques.
Show threadeighteyesMar 6
i'm curious what agile means in a world of solo teaming. i'm doing product and engineering at my job, which would have been 6-8 people in the before times. the bottleneck isn't pre-ship planning, it's post-ship review. my sprint cycle is daily. there's no sense in the time overhead of ceremony.
Show threadJeff Miller (orange hatband)Mar 6
@eighteyes "Theory of Constraints" is showing up for me as a place to refer processes. It specifically looks at constraints and how they suggest what to do when they change or are different from what were present when a process was described or designed.
Show threadJeff Miller (orange hatband)Mar 6
@eighteyes The other reference that surprised me (okay I am a little slow) as increasingly relevant was automated code analysis. When coding isn't the bottleneck in development, other parts take more stress, and may need to change.
Show threadeighteyes
@jmeowmeow my experience with automated analysis is it is prone to miss things if you're applying it broadly. everyone working with llms should know about context rot and the need to combine mechanical with inference based approaches. for example. i just tackled a list of 50 bugs in my software project. giving the whole list to the ai in one bunch, only solved about 10 of them, the easy ones. by forcing it to iterate, fix then validate ( using tooling ), to think about each one as an isolated unit, was much more successful.
Mar 6 at 7:57pmWeb
Show threadJeff Miller (orange hatband)Mar 6

@eighteyes Small tight iterative slices, each one verified, appear to be a useful pattern for agentic augmented coding.

Lada Kesseler had a post about patterns and antipatterns in augmented coding which I appreciated.