Timeline for Startup - is it time to split into two teams?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2019 at 3:13 | vote | accept | djt | ||
| May 13, 2019 at 12:33 | answer | added | Barnaby Golden | timeline score: 3 | |
| May 13, 2019 at 7:41 | answer | added | maze | timeline score: 4 | |
| May 12, 2019 at 18:47 | comment | added | Bart van Ingen Schenau | Are the non-developers (UX Designer, Head of Product, Head of Marketing, etc.) also part of the team or are they working separated? Does the team have a Definition of Done that includes testing and integration? What would the response of the team be if you said "this will go live in one hour" once they report a story as done? | |
| May 12, 2019 at 18:38 | comment | added | Todd A. Jacobs♦ | It seems like you have an agile adoption problem, not a team size problem. Splitting your team before fixing the underlying issues is likely to double your integration problems rather than reduce them. | |
| May 12, 2019 at 17:30 | review | First posts | |||
| May 13, 2019 at 3:43 | |||||
| May 12, 2019 at 17:29 | history | asked | djt | CC BY-SA 4.0 |