Subscribe: Eric Gunnerson's Compendium
Added By: Feedage Forager Feedage Grade B rated
Language: English
agile theory  agile  code test  code  constraints –  constraints  development team  part  theory constraints  theory  – part   
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Eric Gunnerson's Compendium

Eric Gunnerson's Compendium

Last Build Date: Fri, 12 May 2017 04:16:51 +0000


Agile and the Theory of Constraints: Part 4–The Inner Loop

Thu, 11 May 2017 15:32:49 +0000

In this post, I’m going to talk about what I’m calling the inner loop, what some people call “Ring Zero”; it is basically the simple act of writing code and validating it, over and over. It is focused on a single developer. Code/Test/Code/Test/Code/Test/Code/Test Before I dig into things, I have a bit of pre-work for...

Agile and the Theory of Constraints – Part 3: The Development Team (3)

Tue, 18 Apr 2017 15:08:17 +0000

Finally, we make our way to the heart of the development team and the design & code phase.   That is the top part of this diagram. The design/review/finish and code/review/finish chunks are very similar. The developer does some work, submits it for review, perhaps does rework based on the review, and then finally finishes...

Agile and the Theory of Constraints – Part 3: The Development Team (2)

Thu, 30 Mar 2017 15:13:56 +0000

In the last post, I asked you to put some numbers on the red (aka “rework”) arrows on the diagram. There are two ways to express these numbers; either the percentage of the time a specific path is taken, or the number of times the path is taken on average. I’ve chosen the latter because...

Agile and the Theory of Constraints – Part 3: The Development Team (1)

Thu, 23 Feb 2017 15:31:51 +0000

(Note: The first version of this was a very random draft rather than the first part that I wrote. I blame computer elves. This should be a bit more coherant) This episode of the series will focus on the development team – how a feature idea becomes a shippable feature. A few notes before we...

Trip Report: Agile Open Northwest 2017

Tue, 14 Feb 2017 16:46:26 +0000

Agile Open Northwest uses a different approach for running a conference. It is obviously around agile, and there is a theme – this year’s was “Why?” – but there is no defined agenda and no speakers lined up ahead of time. The attendees – about 350 this year – all show up, propose talks, and...

Stop writing bad tests. Write only the tests that you can do great.

Sun, 09 Oct 2016 20:25:15 +0000

I’ve been working on a talk on ways to make unit testing easier. I has not been going well; I’d come up with an approach I liked, do most of the slides for it, come back to it, and be unhappy with what I had written. This happened – and I am not exaggerating –...

You Suck at TDD #8 – Doing fewer things

Tue, 05 Jul 2016 15:05:33 +0000

Welcome back to You Suck at TDD. Today’s code will show up in the Improvements-Phase-3 branch if you would like to follow along. In our last episode, we concentrated mostly on the Employee fetching and filtering. Things are better, but we still have a problem… Well, actually, we have a number of problems, but we’ll start...

Agile and the Theory of Constraints – Part 2: The development cycle

Tue, 17 May 2016 15:18:44 +0000

In the last post, I talked about some of the analysis used in lean. Now, let’s see how we can apply the same principles to the software world. I will start by trying to create a value-stream map. But where to start? There are three levels at which we can do the mapping: The entire organization,...

Agile and the Theory of Constraints – Part 1

Mon, 25 Apr 2016 04:52:35 +0000

I’ve been spending some time over the past few months exploring the lean side of the house and looking for things I can adapt into the agile side of the house. The most interesting thing I found was the theory of constraints. After spending some time writing this, I realized that I need to split...

Doesn’t pairing cost twice as much?

Tue, 05 Apr 2016 23:02:07 +0000

(I was recently involved in a discussion about pairing, and I think what I wrote will be of more general interest.) Many teams evaluate pairing from a simple mathematical perspective. Total work done = # of team members * amount of time spent working If you want to increase the amount of total work done, then...