Everyday Kanban

Discussing Management, Teams, Agile, Lean, Kanban & more

Category: Management (page 22 of 25)

Diagnosis Manager – Scraped skin and broken bones

Part 1 of the Diagnosis Manager series contemplating common management ailments suffered by teams. No teams or managers were harmed in the writing of this blog post.

I have been thinking quite a lot recently about how managers can become impediments to progress, not to mention improvement. The discussion about this is increasing exponentially by the day in Agile and Lean circles, if not others. I am a manager of a development team and have 8 people that I value and whom I want to see do great things while being happy doing them. So, the concept that I might unknowingly be getting in the way of that is troubling and very nearly led to some sort of crisis of purpose for me. I started some conversations in the community and did a good bit of reflection – though still not nearly enough. What I noticed as I started writing down my initial thoughts on managers as impediments is that those thoughts came back to one or two root concepts.

Continue reading

Put your focus on Focus

I’m relatively new in my current job — working on 6 months now. I was speaking with another manager and the conversation drifted to the first changes my team implemented after I joined. But, as every good change agent knows, before you implement changes, you have to orient and observe.

When I came aboard, my team had a sizable backlog and every feature request and bug report was assigned out to members of my team of 8. New items came in daily and items were assigned as soon as they were received, regardless of how long it would be until it got attention. Each team member had handfuls of requests assigned to them plus any work for projects they were working on. Not only that, but each team member took weekly turns being the person that spent time each day figuring out who would be assigned to every new item.

Continue reading

Midnight thoughts on capacity, slack and WIP

What’s more than 140 characters but less than my normal tome? This blog post 🙂 Its midnight here in Seattle and my brain is still whirring about topics stirred up at Lean Coffee this morning. So, I just wanted to throw some quick thoughts down on virtual paper regarding capacity, slack and WIP. Here goes…

Look, managers (and I can say this to you, because I’m a manager too). It’s about flow, not capacity. What I mean is that the measure of success is not ensuring that developers are busy every single minute. Rather, its improving your system flow so you get more done in less time. The problem is that people think to do the latter, the former must be done. Beware! It can have the opposite effect.

In addition, that 15 minutes at the foosball table or 10 minutes playing with nerf guns can be crucial to those with jobs involving complex thought work. The brain needs time to process information. A developer who is actively coding 100% of the time is likely not doing their best work. Now, team, if you’re reading this, I’m not signing off on 4 hour sprees in the game room!

This morning a topic was how to get developers to buy into WIP limits. I can say with certainty that my experience proves that WIP limits are analgesics for workers. More focus breeds better quality features completed faster and THAT equals less stressed developers. Who doesn’t want that?

« Older posts Newer posts »

© 2024 Everyday Kanban

Theme by Anders NorenUp ↑