Timeline for Agile method for a non-technical product owner + one developer
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 3, 2011 at 9:54 | vote | accept | jgauffin | ||
Nov 2, 2011 at 14:40 | comment | added | Ian | A one man Scrum is just waterfall with a 2 week project length. | |
Nov 2, 2011 at 11:43 | comment | added | jgauffin | @ChrisF: I hadn't seen the other question and it made me clarify my question. So thanks. | |
Nov 2, 2011 at 11:24 | answer | added | maple_shaft♦ | timeline score: 0 | |
Nov 2, 2011 at 10:04 | comment | added | yannis | kelleystar's question asks for agile process concepts, as (s)he is correct in assuming that agile is team oriented. Your question may ask something a little bit different but a team of two is not that different from a solo developer when it comes to methodology: people will need to wear multiple hats at once and only a subset of the processes will make sense. IMHO still a duplicate, as it leads to same-ish answers. | |
Nov 2, 2011 at 9:49 | comment | added | ChrisF♦ | That's one reason why I only suggested it might be a duplicate. Just make it clear that you've seen the other question and it doesn't answer your problem. | |
Nov 2, 2011 at 9:47 | answer | added | Ladislav Mrnka | timeline score: 3 | |
Nov 2, 2011 at 9:45 | history | edited | jgauffin | CC BY-SA 3.0 |
added 143 characters in body
|
Nov 2, 2011 at 9:43 | comment | added | jgauffin | @ChrisF: He asks about Agile development in general. I ask for a specific documented method. (or at least that was my intention) | |
Nov 2, 2011 at 9:42 | comment | added | jgauffin | @YannisRizos: Waterfall is of course overkill. That's why I asked. | |
Nov 2, 2011 at 9:41 | comment | added | ChrisF♦ | Possible duplicate - programmers.stackexchange.com/questions/220 | |
Nov 2, 2011 at 9:39 | answer | added | Michael Shaw | timeline score: 0 | |
Nov 2, 2011 at 9:34 | comment | added | yannis | "Scrum seems to be overkill". And waterfall isn't? One core principle of Agile is that you can cut it down and adjust to your own needs (Individuals and interactions over processes and tools). There isn't one methodology that would fit your situation best, as all Agile methodologies have the same core principles. Pick one, start small and stick with it. | |
Nov 2, 2011 at 9:29 | history | asked | jgauffin | CC BY-SA 3.0 |