Comments for Tea-Driven Development

Comment on How much do you refactor? by Myles

Myles — Tue, 13 Aug 2013 20:34:23 +0000

I've been reading around and found some good discussions on design within agile by @scottwambler and @simonbrown

Comment on Half-arsed agile by Seb Rose

Seb Rose — Tue, 13 Aug 2013 10:43:29 +0000

Yes! (Did you see http://www.halfarsedagilemanifesto.org ?)

Another major reason for wildly fluctuating velocity is oversized user stories that limp, half done, from sprint to sprint. All the good technical practices in the world won’t give you a regular velocity if your stories can’t be delivered within the sprint.

Comment on Half-arsed agile by @joshbuddy

@joshbuddy — Tue, 13 Aug 2013 09:20:37 +0000

Are you sure the reason you see a slow down isn't because the code base is increasingly complex to maintain and add features to?

Comment on Awesome Acceptance Testing by Matt Wynne On Using Cucumber - SitePoint

Matt Wynne On Using Cucumber - SitePoint — Tue, 13 Aug 2013 06:29:21 +0000

[...] there; Iâ€d just read his book. Dan North was there also. Dan and Joe Walnes did this talk called Awesome Acceptance Testing. It was all about the kind of acceptance tests they were writing â€“ I think they were both working [...]

Comment on Half-arsed agile by a fellow developer

a fellow developer — Tue, 13 Aug 2013 02:17:18 +0000

Your lucid post really hit the spot. I hope my team reads and appreciate your pragmatic first-hand point of view. Thank you!

Comment on Half-arsed agile by David Lowe

David Lowe — Mon, 12 Aug 2013 18:23:16 +0000

Nice post Matt. Glad you raise the point that starting TDD will result in a down-turn in output. In fact, the same will have happened when they first started Scrum - if only they could remember that far back.

Comment on Half-arsed agile by Andy

Andy — Mon, 12 Aug 2013 15:55:34 +0000

100% agree

Comment on How much do you refactor? by Myles

Myles — Wed, 24 Jul 2013 19:49:28 +0000

Yeah 3:1 Matt!
Ummm dare i say it but does this raise an argument to do more thinking/design upfront?!
can you drill into a few of the refactors and see if they would or wouldn’t have been captured earlier?
It’d be a shame to think you’re in a product innovation team and 3/4 of your time is refactoring, no?

Comment on How much do you refactor? by Mike

Mike — Wed, 24 Jul 2013 15:55:46 +0000

Umm, 76:24 is closer to 3:1! Which feels about right.

Comment on How much do you refactor? by Jim Gay

Jim Gay — Wed, 24 Jul 2013 15:16:51 +0000

This is great insight, Matt!
It makes me think of this http://www.infoq.com/presentations/Technical-Debt-Process-Culture;jsessionid=EA22BC6DF3B87E9E7C75DC9773887074 which talks about the cost of not spending the time on refactoring.