Category: Strawberries

I want to muse today about Small Steps and how they affect me. I owe GeePaw Hill a pat on his cute little head for helping me focus on them.

My mistakes make me laugh. I greet them as old friends. How do yours make you feel?

I think about screen layout. I look at the list of things to do. It's the Jira Trap!! It all seems so reasonable ... until it isn't.

The Invaders team has encountered a troubling issue, and have been making some troubling decisions. We need to explore this and deal with it at its root. Spoiler: It's not the programmers. People over process.

Why do we work as we do? How might we improve? We look back at our process and practices in the large. We accidentally invent "Agile".

A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.

A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.

A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.

A periodic republishing of habits that I would like to have. New items at the top, but each issue includes all prior items.

I'm going to start keeping track of the 'resolutions' I make as I program. I'm sure some of these are generally applicable but I'm working in Kotlin as I start this list.

When we make two changes at once, there are four possible outcomes, and three of them are bad!

Here, some thoughts raised by yesterday's Agile Alliance Zoom thing.

Kent Beck is writing about 'tidying'. It's a whole patch of delicious strawberries, and I highly recommend them.

Can we make our programming life immediately easier with this one simple trick? The answer may surprise you.

Agile Software Development is about people working together. For that to happen, it helps to be kind, respectful, and helpful. Let's talk about that.

TDD is too big a lump to be a good strawberry. Today I'm playing with TDD to try to find a bite-sized goodie. I expect not to accomplish that.

Technical Practices, Craft, Excellence, Improvement, Ease, Joy. What ARE you talking about??

Let's consider the implications of small-step development on our three shadow views of the program. (Includes Sarlacc.)

Yes, short feedback cycles are good. But is the trick of the trade 'small', rather than 'short'? The answer will not surprise you.

Working software is at the core of success with agile methods. Let's remind ourselves about that.

GeePaw Hill is workin on an idea. I urged him to publish his thoughts because I knew it would help him to make things concrete. Also I wanted to comment here.

I know what you're thinking: 'Is this four rules or only one?' Well, to tell you the truth, in all this excitement, I kind of lost track myself. You've got to ask yourself one question: 'Can I use this?' Well, can you?

We're here to replace raspberry jam with strawberry jam. We need those delicious nodules of flavor and value.

It's not the method. It's not the framework. It's your unique assemblage of innumerable small things that work together toward success. And some larger things: the people.

It's Wednesday. At last night's Friday Zoom Ensemble, we talked about Jam. I am inspired to put down some thoughts. Bottom line: On-line strawberry, not raspberry. (Updated, more links.

This article expresses, in written form, the talk that Chet Hendrickson and I gave at the deliver:Agile conference.

The above was the title of my talk with Chet Hendrickson at deliver:Agile. I'll update this with a link to the talk when it is published. Meanwhile, here are some thoughts.