Timeline for IEEE SRS documents: lightweight version when working with outside contractors?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 6, 2013 at 21:49 | review | First posts | |||
| Jan 6, 2013 at 21:53 | |||||
| Jan 2, 2013 at 16:01 | comment | added | Michael | 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. | |
| Jan 2, 2013 at 12:18 | comment | added | user42242 | @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. | |
| Jan 2, 2013 at 4:23 | comment | added | Michael | 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. | |
| Dec 31, 2012 at 16:56 | history | edited | user42242 | CC BY-SA 3.0 | added 1 characters in body |
| Dec 31, 2012 at 16:51 | history | edited | user42242 | CC BY-SA 3.0 | added 77 characters in body |
| Dec 31, 2012 at 16:45 | history | answered | user42242 | CC BY-SA 3.0 |