background preloader

Agile

Facebook Twitter

Scm

Magazine. Ngourd - Google Code. NGourd is a BDD Framework written in C#. It is designed heavily influenced by the Cucumber tool from the ruby world. The intention is to create a clean separation between the intent of a specification versus it's execution. This allows developers to concentrate on the technical details while non-programmers can verify and even author specifications. Have a look at the QuickStart and AddingFeatures sample Feature: AutoSuggest Scenario: Spelling Mistake Given I am at the home page When I enter "speeling mistake" into the search box And I click Go Then I should see "Did you mean: spelling mistake"

Evidence Based Scheduling. Evidence Based Scheduling by Joel Spolsky Friday, October 26, 2007 Software developers don’t really like to make schedules. Usually, they try to get away without one. Most of the schedules you do see are halfhearted attempts. Hilarious! You want to be spending your time on things that get the most bang for the buck. Why won’t developers make schedules? Over the last year or so at Fog Creek we’ve been developing a system that’s so easy even our grouchiest developers are willing to go along with it. The steeper the curve, the more confident you are that the ship date is real. Here’s how you do it. 1) Break ‘er down When I see a schedule measured in days, or even weeks, I know it’s not going to work. This forces you to actually figure out what you are going to do. If you are sloppy, and pick big three-week tasks (e.g., “Implement Ajax photo editor”), then you haven’t thought about what you are going to do.

Setting a 16-hour maximum forces you to design the damn feature. 2) Track elapsed time. Main Page - STIQ.