Reputation
1,114
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 11
Newest
 Good Answer
Impact
~39k people reached

  • 0 posts edited
  • 1 helpful flag
  • 40 votes cast
Mar
14
comment How to get a good overview of an Agile backlog?
Agile is not a methodology
Mar
14
comment How much optimisation should one put in for slow integration test setups
@amon Integration tests are completely necessary; automating them is not. If my manual, integrated test shows a problem, I write another focused test to drive the solution. That problem won't happen again.
Mar
14
answered How much optimisation should one put in for slow integration test setups
Feb
8
awarded  Good Answer
Aug
12
answered What is the point of an Expr in vanilla F#? How can it be applied?
Aug
5
awarded  Informed
May
16
awarded  Yearling
Apr
16
comment How to unit test a top level method
Delete the function, write a failing test, then write the function again following strict TDD. Even if it's just an exercise, it will force you to write testable code.
Jan
8
answered TDD and Writing Tests for File Processing
May
16
awarded  Yearling
May
16
awarded  Yearling
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
If your mockup is really complex, perhaps that's an argument for moving their design inside the agile process so that they are kept as simple and as close to the original problem as possible?
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
@nwinker I've worked with your second approach in the past. The problem I found was that there was a large backlog of pre-requisite work being done that was either wasted if the story was changed or never accepted, or created a pressure to accept a story because this work had been done. Does this happen with you? Like you say, Kanban might be better suited, and the more I've worked with it, the more I like it.
Apr
4
answered Do your stories include tasks across disciplines? How do you do capacity planning?
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
Separating stories into "Account Screen UI" and "Account Screen Dev" strikes me as a very bad idea. These aren't stories - they are tasks that are part of a story, but the story is either delivered or it isn't. A story delivers business value and what value to the customer is developing the wireframe? None at all. If you separate stories like this it makes it very difficult to prioritize them in order of business value since, as well as the issues of dependency that you mentioned, you simply cannot evaluate the value to the business of a task.
Apr
4
answered Logging to database: Log first or action first?
Mar
26
awarded  Good Answer
Mar
21
awarded  Nice Answer
Mar
21
answered Why do relational databases only accept SQL queries?
Mar
20
answered What problems can be solved using Generics?