(Sep 8, 2017)
Responding to a mistaken TDD flowchart.
(Sep 6, 2017)
Mike (GeePaw) Hill storified about sense of urgency and an acronym RAMPS. I like what he said and will muse upon it.
(Aug 4, 2017)
I'm wondering, today, whether the Increment could be the driver for all 'Agile' software development.
(Jul 31, 2017)
Today, let's talk about cadence. Iterations, Sprints, to have them or not, that is the question.
(Jul 26, 2017)
I was asked a question about one of today's modern approaches to Agile software development. Here are some general thoughts.
(Jul 12, 2017)
An innocent email question leads me off into wildness and chaos. What's new with you?
(Jun 26, 2017)
What if I were to create a new software development framework? I'd never do that, but if I did, what might I do? Let's find out. Let's talk today about Whole Team.
(Jun 25, 2017)
Terms seem important to me today. (Revised 2017-07-05: Techniques)
(Jun 25, 2017)
Some Notes on the theme "If I were going to create a new framework, what would it be?".
(Jun 21, 2017)
A number of tweets and posts this week point out, correctly, that if we don't think about what we're doing, Scrum and Agile won't work. Apparently people need this reminder.
(Jun 12, 2017)
A couple of things passed by my Twitter last week and I'll try to comment briefly on them. For values of 'briefly'.
(Apr 24, 2017)
Based on our Scrum Gathering 2017 talk, we discuss the impact on real software development of growing focus on the 'enterprise'.
(Oct 5, 2016)
Time was, you got a spec, got browbeaten into saying you'd do it in 6 months, then got mostly left alone for 6 months. Now, they get to **** with you every ******* day!
(Sep 13, 2016)
Good frameworks are deep. Quick-entry courses sell well. It turns out they sell TOO well.
(Sep 8, 2016)
Scrum is good, when done as intended. Otherwise it can be oppressive and dangerous to developers. Let's study: Defense Against the Dark Arts of Scrum.
(Jul 9, 2016)
A twitter conversation got me thinking about the extent to which Agile ideas are intended to support small improvement, or to disrupt things.
(Jun 27, 2016)
Some interesting tweets make me wonder: if I were creating a method today, what would it be?
(Jun 24, 2016)
A foray into Google App Engine turns into a Tibetan adventure with Bos grunniens. No real lesson is learned.
(Jun 21, 2016)
Mike Vizdos and I are starting a new Slack team and we invite you to join us.
(May 27, 2016)
Over the past few days, an ancient twitter thread accidentally revived, talking about how you don't need quality code when you're just validating assumptions. What do the ants have to say about that?
(May 24, 2016)
Tozier and I did a little work on the ants experiment. Lessons are beginning to be learned.
(May 17, 2016)
Tozier posed an interesting problem today, and we decided to work on it at the coffee shop.
(Apr 21, 2016)
I found this picture of a roulette wheel. I wonder how hard it would be to make my little game use it.
(Apr 20, 2016)
Let's finish wiring up our second pass at Jim Jeffries' roulette example, and see what we can see.
(Apr 19, 2016)
I felt I owed it to myself to do Jim Jeffries' roulette exercise, this time with more tests. You won't believe what happened next. (Sorry, I have a click-bait virus.)
(Apr 18, 2016)
Jim Jeffries (no relation) proposed a TDD exercise / challenge. I took it on. The results may surprise you. (Sorry.)
(Mar 29, 2016)
Measure teams by metrics. Because that's how you get Crappy Agile!
(Dec 18, 2015)
I was asked a question via email and liked my answer enough to write it up. I hope you like it too.
(Dec 8, 2015)
Some twitter leftovers got me comparing Scrum and [Kk]anban. Are they Agile?
(Dec 6, 2015)
Some tweets inspire me to write a bit about management in Agile.
(Nov 27, 2015)
Going too far is quite difficult to do.
(Nov 25, 2015)
Bob Martin has published the Programmer's Oath. What do I think about that? The answer may surprise you.
(Nov 23, 2015)
Just some small thoughts bordering on rants. Something here for everyone to get mad about.
(Nov 12, 2015)
It's common to tweet things objecting to high automated test coverage as if it's irrelevant, incompetent, or stupid. I suggest otherwise with a thought experiment.
(Nov 9, 2015)
In which we discuss the technical debt metaphor, clean code, and the inevitable decline of civilization.
(Nov 5, 2015)
Mistakes, I've made a few [thousand], but then again too many to take personally. – not Frank Sinatra
(Nov 3, 2015)
A Twitter thread gets me thinking about Mock objects and whether they're more than just a matter of personal taste.
(Nov 2, 2015)
Let's try this again. The previous article was not clear to all readers. I suppose this is often the case with my work but in this case I thought I'd try again.
(Oct 30, 2015)
At the time of the Agile Manifesto, we all did the best we knew. Here's something I wish we had done. (Revised)
(Oct 18, 2015)
The Backlog is an essential artifact in Scrum. It may also be the root of serious dysfunction.
(Oct 12, 2015)
Generalizing from a few results isn't proof. In this article I'm going to prove that by generalizing from a few results. Wait, what?
(Oct 9, 2015)
Let's look at what Agile-focused individuals can do to improve their own lives, and, through interacting, help their colleagues and their organizations.
(Oct 8, 2015)
In a conversation about religion, I found myself saying something that makes me think about 'Agile'. Trigger warning: includes words like 'Christian'.
(Sep 28, 2015)
I've been a bit disappointed lately by the state of Scrum in companies, and rightly so. But there's another way to look at it.
(Sep 15, 2015)
Chet and I were talking about the importance of the Increment and the Sprint Goal. Herewith, some musings.
(Sep 8, 2015)
You have to either laugh or cry. -- Wm. M. Rogers
(Sep 1, 2015)
You people could help me by doing a better job and making fewer mistaks.
(Sep 1, 2015)
One great way to remove an impediment is to replace an old idea with one that's better. Let's give that new idea a new name.
(Aug 26, 2015)
Kate and Dan estimate a new project. Or do they?
(Aug 24, 2015)
I haz one.
(Aug 24, 2015)
The Estimate-Commitment relationship stands in opposition to collaboration. It supports conflict, not teamwork.
(Aug 22, 2015)
After a lot of email and blogging, Steve McConnell and I "Came out by the same door where in we went".
(Aug 6, 2015)
Many individuals are creating new, marvelous, incredibly valuable Agile contributions. These were inspired by the Manifesto. They are not updates to the Manifesto, they're founded upon it.
(Aug 1, 2015)
In which we search for common ground and disputed ground.
(Jul 31, 2015)
Steve makes some great points. I think I'd make somewhat different ones.
(Jul 29, 2015)
If we can't build software well, all our Agile is for nothing.
(Jul 24, 2015)
A recent Twitter conversation bugged me (and bugged Clarke Ching even more). Here's why.
(Jul 22, 2015)
Privilege. No privilege. Screw it, improve your situation. Or don't. It's up to you.
(Jul 20, 2015)
OK, one more on this bowling thing: I decided I should do some tests.
(Jul 19, 2015)
Scoring bowling is Chet's and my go-to application for demonstrating pair programming and TDD. So here it is in Elixir, without either pairing or TDD. Interesting, though.
(Jul 16, 2015)
A report on building up a payroll pipeline. Twice. And still not entirely liking it.
(Jul 15, 2015)
Let's see whether we can sketch a little payroll. In Elixir. As the title suggests. Expect trouble - I do
(Jul 15, 2015)
It seems like time to experiment with something new. Will it be Elixir? Hold on, this is going to be chaotic.
(Jul 13, 2015)
Apparently the word 'estimates' is not clear. Here's what I mean and don't mean.
(Jul 11, 2015)
You keep using that word. I don't think it means what you think it means.
(Jul 9, 2015)
Slicing is easier and better than estimation for projecting done. And slicing adds value, while estimation does not!
(Jul 7, 2015)
That's all you need. You don't need no more.
(Jul 6, 2015)
A Twitter conversation got me thinking about how often teams or organizations fall away from their process, when it happens, and why.
(Jul 5, 2015)
Theory, Practice, Received Wisdom, Certification. These are not the things that make things work. Good people make things work.
(Jul 3, 2015)
Keep seeking better ways.
(Jul 2, 2015)
Deciding what kind of tests, and what tools, would be good for a payroll series, if I continue with it.
(Jul 1, 2015)
I love computers! Trying to set up Fitnesse and landing squarely on rspec.
(Jun 30, 2015)
Every minute we spend just thinking and talking, and not programming, is wasted!
(Jun 29, 2015)
Chet and I just ran an Agile Skills Workshop last week. It was great fun. We were asked for a description, and here it is.
(Jun 7, 2015)
A brief um discussion about the Increment and how it might help you change culture.
(Apr 24, 2015)
I guess today I must write about the Scrum "Definition of Done", which is neither a definition, nor done. Is it a Scrum Artifact? I'd rather not.
(Apr 23, 2015)
Someone asked about comments on this site. I don't want comments on the site, but I am happy to discuss things, so I've set up a Google Groups forum. Here's some info about the forum.
(Apr 20, 2015)
I had occasion to look at a couple of articles from 2010, and things don't seem to have changed much. Should we be concerned?
(Apr 10, 2015)
All around us, Scrum and Agile are used, misused, and abused. How should we feel about that?
(Mar 29, 2015)
For success with Scrum, we need the basics, our expertise, and to improve our culture. To improve the culture, we need the Product Increment.
(Mar 27, 2015)
Development teams need help using the product increment as a center for making lives better. I resolve to work to fix that.
(Mar 27, 2015)
We're not blaming you when we say you're doing it wrong. We're trying to help you do it right.
(Mar 27, 2015)
We need to make Scrum and Agile safe for software developers. How should we proceed? (updated)
(Mar 25, 2015)
It's not up to Scrum or "Agile" or XP to make you successful or happy. It's on you.
(Mar 25, 2015)
We don't want just a "Product Owner". We want a Product Champion!
(Mar 23, 2015)
Impediments are there to be removed, not there to be recorded for posterity. Drive them out, don't log them in.
(Mar 16, 2015)
There's not much wrong with Scrum. Or is there? It depends what the meaning of 'wrong' is.
(Mar 16, 2015)
They shipped the software, therefore what they did was best. It ain't necessarily so.
(Mar 12, 2015)
Jonathan Rasmusson wrote an interesting article. I agree. It's not about unit tests. It's about skill and understanding.
(Mar 9, 2015)
Giles Bowkett invited me to discuss another article he wrote. For some reason I'm willing to do that.
(Mar 6, 2015)
The conversion from XProgramming.com to RonJeffries.com is essentially complete. Let's look at some learnings.
(Mar 2, 2015)
Many people assert that Scrum fails often. They say it's Scrum's fault. I'm still trying to understand.
(Mar 1, 2015)
Jeff Sutherland said today that it's not done if it's not tested. You won't believe what happened next!
(Feb 24, 2015)
It is my practice to reconsider important topics. Certification certainly is such a topic. Here are today's thoughts.
(Feb 20, 2015)
Giles Bowkett has written some impassioned diatribes against Scrum on his blog. He raises some issues, which I shall try to discuss.
(Feb 8, 2015)
I was reminded by a lovely email of what happened during our SAFe training. Eliminate dependencies, don't document them or accommodate them.
(Jan 29, 2015)
Address given at the final meeting of the Agile Alliance, August 20__, by Ron Jeffries
(Jan 24, 2015)
As Tozier and I work on Scraper, I find the pairing to be quite difficult, though not unrewarding.
(Dec 8, 2014)
XProgramming will transition slowly over to ronjeffries.com. Be there or be square.
(Nov 29, 2014)
Today is a big day for people tweeting how they deplore what other people are doing. Others retweet those tweets. I think that's a fruitless behavior and suggest something different.
(Nov 22, 2014)
This is an NSFW rant regarding the whiny, mewling *bastards* who bitch, whine, and complain about Agile methods, Scrum, and similar topics.
(Sep 25, 2014)
Scrum top dogs announce combined site for Scrum definition.
(Sep 20, 2014)
XProgramming.com needs a new implementation. Want to watch?
(Sep 20, 2014)
XProgramming.com needs a new implementation. Want to watch?
(Sep 5, 2014)
Put makeup on your own pig, make it look as good as you can. Don't go around finding ugly imaginary pigs to stand it beside.
(Apr 2, 2014)
Recent Twitter conversations inspire me to pull out some of my concerns with SAFe and talk about them.
(Feb 27, 2014)
I recently took the SAFe SPC training. My bottom line assessment is that it will be a marketing success, organizations trying it will see improvement, and some will see great improvement. And I don't like it.
(Dec 31, 2013)
Don't buy a brand. Seek out good ideas, and apply them to your situation.
(Mar 27, 2013)
Robert Pirsig's protagonist "Phaedrus" said "Quality is what you like". We talk a lot about "value". My aim here is to suggest to you that value is what you like.
(Jan 3, 2011)
Alan Shalloway blogged on "Big Change Up Front", suggesting that it's not always the best thing to do. This made me think ...
(Dec 24, 2010)
"Why don't you believe in testing?" said Lanette Creamer, the Testy Redhead. Ah, but I do. I care about what, when, and at which end of the horse.
(Dec 12, 2010)
An odd anonymous article on "LearnTFS" purports to debunk Agile by moving closer to waterfall. Interesting, but not quite right.
(Dec 10, 2010)
I've had the privilege of observing He Jinbao, a martial arts master. He doesn't hurry. Maybe we shouldn't either.
(Dec 9, 2010)
Are there places where lower quality has less negative impact? Possibly. Except maybe on your soul.
(Dec 8, 2010)
No one I know can operate at their peak performance all the time. How do we know how hard to work on quality? Same way you get to Carnegie Hall.
(Dec 7, 2010)
You can always find someone to argue for cutting quality corners to "go faster". Is it possible to waste time cleaning code? Sure. Is it possible for code to be too clean? No.
(Dec 1, 2010)
Teams often want to write "technical stories" to cover things like testing and improving the design or infrastructure. There is rarely a need to do this. Here's why.
(Nov 6, 2010)
Alan Shalloway and I were tweeting about whether Scrum could be improved because it doesn't include some damn thing or other. Scrum is working as designed. We and the Alliance need to get to work.
(Oct 31, 2010)
Chet and I will be meeting with both the new and the outgoing Managing Director of the Scrum Alliance. I asked for input on Twitter, and have received some. Here, some thoughts.
(Oct 20, 2010)
"Just tell us when you'll be done with all these requirements" is not how to guide an Agile project, be it Kanban, Scrum, or XP. Not remotely.
(Aug 27, 2010)
Some people have difficulty living up to the values and principles of the Agile Manifesto. Should we improve the Manifesto? Raise your game: we meant what we said.
(Jul 15, 2010)
"His brand is bad: my brand is good." Isn't it well past time we got over that kind of thinking? I'll take a good idea from anywhere. So should you.
(Jul 13, 2010)
Should we ease into Agile, or jump in? How fond of being eaten by bears are you?
(Jun 29, 2010)
Let's consider two "dimensions" of a project, the extent to which it adheres to "Agile" values, and the extent to which it is an effective or successful project.
(Apr 11, 2010)
There has recently been another discussion of Kanban on one of the Scrum lists. Kanban has some interesting ideas, and yet it seems to conflict with Scrum in some essential ways. The problem isn't Kanban: it's the notion of "essential ways".
(Dec 21, 2009)
Agile projects very often seem to stall out after gaining perhaps twenty-five percent of the possible benefit. Why is this? What can be done?
(Dec 16, 2009)
Incremental and iterative development processes provide frequent opportunities for teams to "Inspect and Adapt". What should we inspect? How should we adapt? Is this part of the process?
(Nov 20, 2003)
Object aficionados worldwide are concerned that the procedural bowling solution presented last time is just not robust enough. They want to see how we would make it score the frames incrementally. Frankly I haven't the slightest idea.
(Nov 18, 2003)
Here's the Bowling Game again. This time I'll take a simpler approach, along the lines I usually follow when I do a Test-Driven Development demonstration. The result is strikingly simpler than the preceding 'object-oriented' solution. What does this tell us about TDD and how to use it?
(Nov 17, 2003)
TDD on the Bowling Game (article lost and now found again)