(Apr 24, 2017)
Based on our Scrum Gathering 2017 Keynote, we discuss the impact on real software development of growing focus on the 'enterprise'.
(Feb 19, 2017)
I've been trying to learn a 3D drawing program. Yesterday I noticed that I was working but not learning.
(Oct 17, 2016)
Possibly not the best stance to take on, if you can manage it.
(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?
(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?
(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 6, 2015)
Some tweets inspire me to write a bit about management in Agile.
(Nov 25, 2015)
Bob Martin has published the Programmer's Oath. What do I think about that? The answer may surprise you.
(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 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.
(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 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.
(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 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 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 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 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 2, 2015)
Many people assert that Scrum fails often. They say it's Scrum's fault. I'm still trying to understand.
(May 22, 2009)
Scrum's job ends with the problem. Your job begins with the problem.