Skip to main content

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*

3
  • 2
    I don't recall reading anything about user stories in the Agile Manifesto... be careful not to confuse common agile practices with what you must do to "do agile." Being agile is about promoting practices that allow change and maximizing value. In an outsourcing scenario such as this, sometimes extra structure can create greater opportunities for agility. Commented Jan 2, 2013 at 4:23
  • @Michael Agile Manifesto is not a software methodology. It is...a manifesto. FYI Agile methodologies existed long before this manifesto was written. Be careful not to confuse thinking how agile you are when, in fact, you are not following any formal methodology. You are just hacking stuff. That's not Agile. Commented Jan 2, 2013 at 12:18
  • we're in total agreement on that point. No process is... no process no matter what label you put on it. The main problem I have with your answer is in the idea that "SRS is a no-go in Agile" and "in agile, requirements are specified as User Stories." You can still be perfectly Agile and not use user stories. This is wrong and distracting an otherwise good answer. Commented Jan 2, 2013 at 16:01