Timeline for What framework or methodology would you recommend for a Data Science team?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2020 at 11:22 | vote | accept | user32613 | ||
| Nov 26, 2020 at 21:27 | comment | added | Barnaby Golden | My suggestions would be: Drop estimating for now, instead focus on how the team members can help each other out in a sprint. e.g. "If Sam finishes her research on Tuesday she can help me out with the proposal doc." Try and think about ways to break your work items down as small as possible. This will be challenging at first, but the team will get better at it. The small work items will make it easier for you to get them to 'done' inside a sprint. It also gives you something to show your stakeholders in sprint reviews. | |
| Nov 26, 2020 at 7:40 | comment | added | user32613 | Thanks for reply. It's maybe asking a bit much, but if you happen to have some free time, would you mind expanding your answer to give high level steps of how you would approach this problem assuming we kept Scrum e.g. how you would tweak all ceremonies and education or just generally your approach | |
| Nov 25, 2020 at 18:03 | comment | added | Barnaby Golden | You make a good point, I hadn't really thought about it in the time sense. | |
| Nov 25, 2020 at 16:15 | comment | added | nvogel | Your first two sentences are perhaps a bit ironic since Jeff and Ken only removed the requirement to do estimates from the new version of the Scrum Guide a few days ago. That's a welcome change but perhaps the OP's company is going by what the Scrum Guide said last week! | |
| Nov 25, 2020 at 11:03 | history | answered | Barnaby Golden | CC BY-SA 4.0 |