Timeline for How do I deal with a counterproductive scrum team?
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 29, 2018 at 9:53 | history | suggested | Pang | CC BY-SA 4.0 |
Corrected spelling and wording. Improved punctuation.
|
| May 29, 2018 at 3:19 | review | Suggested edits | |||
| S May 29, 2018 at 9:53 | |||||
| Aug 20, 2017 at 19:35 | comment | added | RemcoGerlich | @Shane: but the team feels they did work pretty effectively, after all they got quite a lot done. Just not exactly what was in the sprint planning, which they already feel is useless. What is your goal when telling them they failed the entire sprint? | |
| Aug 20, 2017 at 19:07 | comment | added | jpmc26 | I gotta say that if that's your idea of a joke, I can understand why people might have trouble getting in on it. =p | |
| Aug 18, 2017 at 17:03 | comment | added | Dan Mašek | One handy thing my team did during standups was a quick triage of bugs that appeared since the previous day. That helped improve our response times tremendously. Easy things could be fixed right that day, critical brought to attention of PM, rest queued for the next full triage. The team would congregate around a big screen which had a display of the status all our builds and tests, progress status of the sprint, and important monitoring charts for all our systems. | |
| Aug 18, 2017 at 13:35 | comment | added | Marcin Raczkowski | @sashang why even bother commenting if you've obviously not read my whole post? | |
| Aug 18, 2017 at 5:45 | comment | added | sashang | 15 minutes is too long. What value does it add? Everytime i've done SCRUM the standups have been the most pointless waste of time ever. People just say 99% of the time 'working on x yesterday, same today'. | |
| Aug 18, 2017 at 5:06 | comment | added | Marcin Raczkowski | @jpmc26 You should really read a whole line ... and get in on a joke. | |
| Aug 18, 2017 at 3:07 | comment | added | jpmc26 | "Who the ... cares about the company's money?" I do, and I'm not a shareholder. But in some respects, it's because I care about me. Time wasted on poor development decisions is usually time that I have to spend redoing stuff. It's clients who are unhappy with me just as much as the rest of my team. And to some degree, it's my job. =x | |
| Aug 17, 2017 at 20:47 | comment | added | Marcin Raczkowski | Then you have astounding successes - someone finds an open source library that does exactly what you allocated 2 weeks sprint for, and what? 2 week vacations? - I wish! To deal with sprint failure you generally have following options: a) Adjust items in sprint (replanning). b) End Sprint and restart. But your comment really warrants a full question/answer to explain properly :) | |
| Aug 17, 2017 at 20:40 | comment | added | Marcin Raczkowski | You are wrong. It's definitely not all-or-nothing. Think about it, 5 men team, everyone gets their tasks done, but one person fails one task, and now what? ... You don't ship anything? Nonsense. It's perfectly fine to create a build out of features that you've finished. This is however area where Scrum has problems IMO, keep in mind that Scrum was first introduced in Manufacturing environment, so it works best for tasks and ocmpanies with low variance (eg. Wordpress shop, that produces several websites for small businesses). That's why you have concepts like Spikes that reduce uncerteinity. | |
| Aug 17, 2017 at 19:38 | comment | added | Shane |
For example: To them, Planning is just a waste of time, because we just move overflow into the new Sprint and don't complete the work anyways, so why bother. This is afaik the exact opposite of how to do things. In your sprint planning you plan everything you are going to get done. If you don't get it all done, you don't throw everything into the next sprint. Your sprint failed. You have no deliverable for that sprint at all because you failed to manage it properly. Someone correct me if I'm wrong.
|
|
| Aug 17, 2017 at 19:34 | comment | added | Shane | +1 for a useful practical answer. OP is doing basically everything about scrum wrong. When one member says this, they are ignored and nothing changes -- basically you are telling them to f-off. Then other team members see that and don't bother to volunteer anything more. Then you wonder why morale is low and why the process isn't getting better? | |
| Aug 16, 2017 at 16:25 | comment | added | jhocking |
A+++++ would buy again And here I thought doing work is what their job was all about. I wonder who was suposed to be dealing with impediments.... oh right. A Scrum Master. It's your job. They tell you what's wrong. You fix it. Not the other way around.
|
|
| Aug 15, 2017 at 22:15 | comment | added | Marcin Raczkowski | Sorry about that, I might have been a bit harsh, but sometimes 'suggestions' don't really reach people. Regarding adjustment: there's a saying 'Hard to be a prophet in your own country'. It's sometimes hard to see the problems from the inside, you often need some outside perspective. That's why they used to hire Scrum consultants, now you have Stack Overflow ;) Good luck, and if you have some follow up questions, let me know :) | |
| Aug 15, 2017 at 22:08 | comment | added | user42401 | It's a little hard not to take personally ;-) But I get what you're saying. I have been part of this team for 3 years now (working agile for 6), and I feel the same way as they do on most areas. It's my first time in the role as Scrum Master, so it's a steap learning curve to figure out how to deal with all of this. | |
| Aug 15, 2017 at 21:59 | comment | added | Marcin Raczkowski | You're welcome. Please try to not take this personally. I've made many similar mistakes back in a day :) It's also easier for me to see as I've been a part of a few failing SCRUM teams. Try to focus on improving the process and adressign concerns of your team, and you'll find the morale improves, then you get few successful sprints and it'll only get better from there. | |
| Aug 15, 2017 at 21:54 | history | edited | Marcin Raczkowski | CC BY-SA 3.0 |
Formatting, some typos
|
| Aug 15, 2017 at 21:45 | history | edited | Marcin Raczkowski | CC BY-SA 3.0 |
Added a section on company attitude.
|
| Aug 15, 2017 at 21:42 | review | First posts | |||
| Aug 16, 2017 at 14:11 | |||||
| Aug 15, 2017 at 21:35 | history | answered | Marcin Raczkowski | CC BY-SA 3.0 |