Timeline for How to get started with Scrum when the team is bad at generating ideas?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2017 at 18:31 | comment | added | Chris Pratt | Backlog refinement, while not actually part of scrum, has become sort of a recommended best practice. Usually, you'll want to devote some time about once a week for the dev team and product owner to go through the backlog and try to flesh stuff out. This helps ensure that you have a good set of PBIs to choose from during your sprint planning. It should be done concurrently with your sprints, though, you shouldn't stop your sprints to do this. | |
| Jul 31, 2016 at 23:30 | vote | accept | user3002473 | ||
| Jul 25, 2016 at 19:05 | audit | Suggested edits | |||
| Jul 25, 2016 at 20:10 | |||||
| Jul 24, 2016 at 2:46 | history | tweeted | twitter.com/StackProgrammer/status/757044258188689408 | ||
| Jul 19, 2016 at 12:22 | comment | added | yatima2975 | "from what I've read it sounds like the time between Sprints is usually between one to two weeks": most Sprints are between 2 to 4 weeks, so half that inbetween is a lot! Refining PBIs should usually be done during a Sprint, or maybe during Sprint Planning when an item is dredged up from the bottom of the backlog for some reason. | |
| Jul 19, 2016 at 12:02 | comment | added | candied_orange | The team is absolutely supposed to come up with ideas. The product owner is supposed to filter those ideas. Sorry but customers don't know what they want. They know what they like. Formal or not, whoever is providing money for the team is the customer. | |
| Jul 19, 2016 at 8:07 | comment | added | Luc Franken | This is a management issue. I you want to activate them they need to understand why they are doing it. See examples like: ted.com/talks/… which explains the difference. If you only talk about what should be done they will not initiate things by themselves. Just starving without leading won't go anywhere, they still have no clue on where to go. | |
| Jul 19, 2016 at 7:56 | comment | added | gnasher729 | The team isn't supposed to come up with ideas. That's the product owner's job. If you don't have a product owner then you are stuck. | |
| Jul 19, 2016 at 7:47 | comment | added | JᴀʏMᴇᴇ | I don't understand why you're trying to shoe-horn a methodology into a situation that won't welcome it. I can't stand people flying the 'agile' and 'scrum' flag when it simply doesn't suit every situation/team. They respond well under a waterfall methodology - please explain why you'd choose to ignore the things that help your team perform best. | |
| Jul 19, 2016 at 7:07 | answer | added | Dan1701 | timeline score: 5 | |
| Jul 19, 2016 at 7:02 | answer | added | Vladimir Stokic | timeline score: 6 | |
| Jul 19, 2016 at 7:02 | comment | added | guillaume31 | The lack of a product owner / committed domain expert is a much more serious impediment than the one with the team, IMO. The team will eventually get up to speed with Scrum (or you will find another methodology that suits them better). | |
| Jul 19, 2016 at 3:36 | answer | added | candied_orange | timeline score: 2 | |
| Jul 19, 2016 at 1:14 | review | Close votes | |||
| Jul 23, 2016 at 3:03 | |||||
| Jul 19, 2016 at 0:06 | history | asked | user3002473 | CC BY-SA 3.0 |