4 ms·
What were you using before the switch to Kanban? This is very interesting to me, the idea that just switching up techniques can have that much of an impact on h
by distrill 11y ago
What were you using before the switch to Kanban? This is very interesting to me, the idea that just switching up techniques can have that much of an impact on how you feel at work.
- cam- 11y agoKanban is more relaxed than scrum. When the teams I worked with switched to kanban, they liked that they didn't have the end of scrum deadline, they also disliked that they didn't have the ten day deadline anymore as they felt the arbitrary deadline helped to push them a little. That being said, kanban is better, it is more relaxed and feature feedback is faster than scrum.
- distrill 11y agoI'll have to look more into it then. At some point we just got tired of hearing about all the different ways to approach agile, and we've been using some sort of (mostly scrum) hybrid for the last few projects I've been a part of. But if there really is merit to this then that's something to consider.
- emmelaich 11y agoI guess we were using nothing really. We had RequestTracker (for ops) and Jira for development and I found myself in the middle. At the start I was the sole sysadmin and did the small amount of developer support stuff as well. We've tripled in size over the last ten years. As we grew I was doing the jobs of product owner, business analyst, developer, devops, sysadmin without really being conscious of the change. The great temptation is to think that things won't work unless you're involved because you know it all. Boiling frog syndrome in a way(1) Not having to decide priorities is a massive relief; the product owners know they have to discuss priorities with each other and my team leader, not me. (1) yeah I know it's not an accurate analogy.