Timeline for Agile method for a non-technical product owner + one developer
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2011 at 14:46 | comment | added | Michael Shaw | We seem to be missing point. For the type of environment the Q described, that process and tool set would be sufficient and not overly restrictive. What defines agile development is a very different question | |
| Nov 2, 2011 at 14:37 | comment | added | Michael Shaw | My experience of waterfall processes are from 15 years ago. At that time, source control was not ubiquitous, never mind CI | |
| Nov 2, 2011 at 13:06 | comment | added | maple_shaft♦ | Waterfall does not do sprints but most do some form of iterative process that resembles an Agile sprint. My argument about CI is that Agile doesn't require CI, proper software development process requires CI. Nothing about Waterfall contraindicates CI either. | |
| Nov 2, 2011 at 12:43 | comment | added | Michael Shaw | That is not true. Waterfall methodology does not do sprints and does not require continous integration. | |
| Nov 2, 2011 at 11:02 | comment | added | maple_shaft♦ | I am sorry but nothing you described in your answer can't also be said as necessary for Waterfall development. What you describe are key things for ANY software development project regardless of methodology. | |
| Nov 2, 2011 at 9:39 | history | answered | Michael Shaw | CC BY-SA 3.0 |