Steve Bement

Agile Developer/Coach

[Steve Bement @stevebement]

@jwgrenning Thanks for sharing this, James. Very good to know.

[Steve Bement @stevebement]

I thought of a more accurate acronym for SAFe: SNAPMS. It stands for Scaled Non Agile Prescriptive Money-making Scheme.

[Steve Bement @stevebement]

@TotherAlistair This isn’t so much a map, but I’ve found this most useful description of how to split a story:

https://t.co/IKm2lhAw9x

[Steve Bement @stevebement]

Hey @GoZwift could someone from the software team explain how you calculate speed? It seems very inaccurate. I’m on Kickr Rollr, so have my rear wheel (and speed sensor) still running as normal, showing my actual speed.

[Steve Bement @stevebement]

@jamesshore @jitterted And we aren't talking about line coverage here, but mutation coverage. Meaning with Nullables, more mutations were killed than with mocks.

[Steve Bement @stevebement]

@jasongorman I think what also happened is agile coaching was taken over by people who don't write software. That opening line of the manifesto is no longer true for maybe 8 out of 10 coaches.

[Steve Bement @stevebement]

@jitterted @jamesshore Makes sense. I was just thinking that the description of the pattern doesn’t prescribe details like that.

[Steve Bement @stevebement]

@arlobelshee I would like to better understand your idea of cross-over system as described here: https://t.co/q3QV0IHmEN Can you provide some details, for a system where “any code change impacts both the old and new systems” and where “every piece of code is both old and new”?

[Steve Bement @stevebement]

@jamesshore @mattwynne Oh, just found that section in your book.

[Steve Bement @stevebement]

@jamesshore @mattwynne @jamesshore During the session you made a distinction between customer tests and customer examples. Could you elaborate on that?

[Steve Bement @stevebement]

@adlenesifi @jamesshore And, as the video shows, those smaller groups don’t change as often as you might imagine.

[Steve Bement @stevebement]

@adlenesifi @jamesshore With FAST, the larger team remains stable (but much bigger then Scrum would advise, say 50 people). The subgroups may switch frequently, but I don’t think that means they start over, in the Tuckman framework. These are people they know and are used to working with.

[Steve Bement @stevebement]

@StefanW @jamesshore @jamesshore Were the teams in this example fairly fluent in XP practices? In my conversations with @ronquartel in the early days of him creating FAST I got the impression that was a prerequisite (hope I’m remembering that right, Ron). So curious what your experience was.

[Steve Bement @stevebement]

@jamesshore @mattwynne Ooh, thanks for the clarification. I’m intrigued now by the differences between the two. Will think more about that.

[Steve Bement @stevebement]

@mattwynne @jamesshore I think of hexagonal architecture mainly as a great way to follow the Dependency Rule, as described here: https://t.co/J60RQ5fGJv
I like to follow that regardless of testing approach (but yes, it makes testing easier).

[Steve Bement @stevebement]

@mattwynne @jamesshore Meaning, you can still use HexagonalArchitecture as a pattern in your production code, and use NullableInfrastructure to aid in testing. But please correct my thinking on this if I am wrong.

[Steve Bement @stevebement]

@mattwynne @jamesshore When you said "how NullableInfrastructureWrappers pattern contrasts with HexagonalArchitecture" I assumed you were going to have to choose one. But isn't your production code still using HexagonalArchitecture? I didn't think we had to make that choice.

[Steve Bement @stevebement]

@jamesshore @TotherAlistair @chethendrickson And “agile release train” is an oxymoron. The whole idea is to design teams and architectures so that teams can release independently from each other.