Steve Bement @stevebement

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

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.

Don’t call it technical debt… call it productivity drain. “We’ve really got to take care of this productivity drain in our code.”

Your business agility is constrained by your technical agility. #LeSSWorks #TechnicalExcellence

It occurs to me that the term Agile Release Train is an oxymoron.

I wonder, @jwgrenning , if they have good unit test coverage for this. thepointsguy.com/news/boeing-an… so they know the fix is not breaking something else.

Finished our sound check at Safeco Field. #Followtheprophet

Another good reason, from @gojkoadzic , why we should stop using the term "sprint". gojko.net/2018/08/30/spr… "Running unsustainably is a perfect strategy for sprint racing, but a total disaster for software work."

#xp2018legacycode Getting ready for a good workshop.

Don't empower teams. Create a culture where teams are powerful and stop giving away that power. Teams own their destiny.

#mywsustory Go Daddy!!!!

#mywsustory Congrats Craig!!

#mywsustory Way to go Craig baby! Graduating from Wayne State this morning with a masters degree. Marianne loves you.

When we begin a pair or mob programming session, we are declaring that we are now entering into intentional, focused work. When working alone, by contrast, I often get interrupted and feel randomized.

Cockburn says: The speed of the project is limited by the speed at which information moves between people. So very true!

Experiencing the unpredictability when working on legacy code. Stories go either much faster or much slower than expected. Not surprised.

Kids learn to add & subtract before using calculators. Teams should learn to use stories & boards before using Jira

Everything in the backlog is negotiable. The team's practices are not. So don't put things about "how" in the backlog.

The product backlog is about "what" not "how". The team owns "how". The practices they choose to follow don't belong in the backlog.

HA! RT @j_c_fitz Running electricity through a pencil with completely predictable results.