Timeline for How to handle 'external' dependencies in scrum?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2018 at 17:12 | history | edited | ChrisF | CC BY-SA 3.0 | typo + more info |
| Feb 21, 2014 at 11:48 | comment | added | Jamie Clayton | So in Project Management, this is Risk discussion. | |
| Oct 5, 2011 at 8:36 | vote | accept | TygerKrash | ||
| Oct 3, 2011 at 13:39 | comment | added | Adam Lear♦ | @JeffO I wouldn't fake an API in isolation, but you could see about agreeing on a common interface that you can code against. Even when the third-party components come in, protecting your code against directly calling them is not a bad idea. | |
| Oct 3, 2011 at 13:30 | comment | added | ChrisF | @JeffO - well that depends. If you need the real results then it could be a problem and API's have been known to change. | |
| Oct 3, 2011 at 13:28 | comment | added | JeffO | Would you ever suggest 'faking' the API if it's not too much trouble? | |
| Oct 3, 2011 at 12:42 | history | answered | ChrisF | CC BY-SA 3.0 |