Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    Requirements always shift and to think they won't until the code is written and approved (assuming those in charge follow the rules)is just being in denile. Commented Aug 28, 2013 at 15:26
  • @JeffO I agree: changing requirement are a sought after feature of agile, for example that's why we have demos. Commented Aug 28, 2013 at 15:47
  • 1
    @JeffO If you want to nitpick, requirements do not always change, they almost always do. I'll change my wording regardless. Commented Aug 29, 2013 at 7:55
  • 1
    I find this answer to be distasteful. "Start with a story to compile the simplest possible program, then create further stories to support more and more language features." But it is likely to require 6 months of work to build a framework before even the smallest program can be built! This is not a realistic answer describing the use of an agile approach for a backend system. Commented Dec 8, 2013 at 8:07