Timeline for How to deal with teams that deliberately make their negligence hard to document/track?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2021 at 4:59 | comment | added | Drudge | As far as incomplete garbage, as long as Team Alice is in full control of the project that shouldn't be an issue: they can document every defect and present it to the exec team. Though this is very hard when Team Bob has ownership, can lie, and then it's on Team Alice to fully investigate and irrefutably prove every little defect on top of their actual allocated work | |
| Jun 29, 2021 at 4:52 | comment | added | Drudge | Team Bob wanted to own the product development & relegate only the actual implementation to Team Alice, so Team Alice could not take full ownership of the project. You're right though, this would have been a good option had it been available. No risk of blame game when Team Alice is point of contact. | |
| Jun 28, 2021 at 21:32 | comment | added | Noel | I'd mention the use of a ticketing system to track any issues in the back end code from Team Bob. They would still 'own' the back end, but not be responsible for driving the schedule. They would still be on the hook for any blocking issues. | |
| Jun 28, 2021 at 15:04 | comment | added | Daniel R. Collins | I feel there's a risk here: degenerate Team Bob might claim completion of the backend work, but hand over broken incomplete garbage, and then have Team A on the hook to deal with the fallout. | |
| Jun 28, 2021 at 10:29 | history | answered | B. Ithica | CC BY-SA 4.0 |