Timeline for How to make realistic long term time estimations when adopting Agile methodology?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 30, 2014 at 3:01 | review | Close votes | |||
Dec 1, 2014 at 3:04 | |||||
Nov 26, 2014 at 14:44 | answer | added | knightgoggles | timeline score: 1 | |
Nov 24, 2014 at 18:25 | answer | added | Ashok Ramachandran | timeline score: 6 | |
Nov 23, 2014 at 17:06 | review | Close votes | |||
Nov 23, 2014 at 18:35 | |||||
Nov 23, 2014 at 16:48 | comment | added | Todd A. Jacobs♦ | Please ask one question per post. If your question is put on hold as Too Broad or for any other reason, feel free to edit it, and ask to have it re-opened. | |
Nov 23, 2014 at 15:09 | history | tweeted | twitter.com/#!/StackProjects/status/536536930100723712 | ||
Nov 23, 2014 at 1:01 | comment | added | mettjus | @PéterTörök With relatively small experience (7 years) I agree. But I want to figure out if I can improve my team's ability of prediction. I'm in the web-design industry and sometimes the minimum valuable product looks like the completed website. So as I have many in the works at the same time I need a tool to be able to have an updated overall picture of expected delivery times, to be eventually able to comunicate in advance to the client if a product is going to come out late or re-prioritise work depending on client needs (fairs or similar). | |
Nov 22, 2014 at 22:27 | answer | added | Tiago Cardoso | timeline score: 5 | |
Nov 22, 2014 at 20:27 | comment | added | Péter Török | "How to make realistic long term time estimations when adopting Agile methodology?" - in software development you can't, it's as simple as that - with or without Agile. The difference is that Agile acknowledges this and is totally honest about it, while the "traditional" way is to try and pretend the opposite as long as possible. | |
Nov 22, 2014 at 18:45 | history | asked | mettjus | CC BY-SA 3.0 |