Timeline for Development process in a highly dependent environment
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:23 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:46 | history | edited | CommunityBot |
replaced http://pm.stackexchange.com/ with https://pm.stackexchange.com/
|
|
| Sep 9, 2013 at 3:16 | history | tweeted | twitter.com/#!/StackProjects/status/376906958135390208 | ||
| Sep 6, 2013 at 10:37 | vote | accept | Vivek Jain | ||
| Sep 4, 2013 at 14:33 | answer | added | Michael Shaw | timeline score: 4 | |
| Sep 3, 2013 at 9:00 | answer | added | Piotr Uryga | timeline score: 2 | |
| Sep 3, 2013 at 0:56 | answer | added | the_reluctant_tester | timeline score: 2 | |
| Sep 2, 2013 at 8:45 | answer | added | Todd A. Jacobs♦ | timeline score: 4 | |
| Sep 2, 2013 at 8:44 | comment | added | Dave Hillier | Also worth noting, I've seen this happen in other engineering industries and this causes problems too. This can be solved by the client by making sure that they have it in their contract to ensure that they can actually talk to the person who is doing the work. | |
| Sep 2, 2013 at 8:29 | comment | added | Dave Hillier | In any methodology, the communication gap causes problems, misinterpretation, mistakes, etc. The only way to overcome this is to build bridges to the real client. Typically the agencies above you don't want this - as the client might just cut them out in future. TL;DR you're a bottom feeder and that isn't a great place to be :( | |
| Sep 2, 2013 at 7:39 | history | asked | Vivek Jain | CC BY-SA 3.0 |