agile management

MPD, portfolio management

Rethinking Component Teams for Flow

A couple of weeks ago, I spoke locally about Manage Your Project Portfolio. Part of the talk is about understanding when you need project portfolio management and flowing work through teams. One of the (very sharp) fellows in the audience asked this question: As you grow, don’t you need component teams? I thought that was […]

agile, MPD

Podcast About Geographically Distributed Agile Teams

Lisette Sutherland posted a podcast we recorded about geographically distributed agile teams. See Organize Your Distributed Team over on the CollaborationSuperpowers site. We covered how you can think about your geographically distributed agile team: Why you want a distributed agile team (yes, there are some great reasons) How you might organize your team. Here are

Articles

Management Myth 25: Performance Reviews Are Useful

Bill popped his head into Jan’s office as he was leaving for the evening. “Jan, do you have a minute? I have to do performance reviews tonight. I was going to drink Scotch and work my way through all of them.” Jan laughed and said, “Sure. Scotch might make you feel good, but it will

Articles

Management Myth 26: It’s Fine to Micromanage

Sharon poked her head into Heath’s cubicle. “Hey, Heath, are you done yet with that fix?” Heath turned around. “Sharon, you asked me that less than an hour ago. I’m not done yet.” “Well, I need to know when you will be done. Oh, and I need to know if you’re using the design we

Articles

Management Myth 24: People Don’t Need External Credit

“Robert, do you have a minute?” Cheryl, the development manager, stood at her director’s door. “Sure, let me save this.” Robert stopped what he was doing. “You look worried. Come on over and let’s sit at the visitors table. This looks serious.” “Well, it is. I’m not sure how to say it, so I’ll just

Articles

Management Myth 16: I Know How Long the Work Should Take

Sally, the project manager, strode confidently into her meeting with John, the CIO. She’d reviewed the roadmap with the product owner and had discussed the risks with the project team. She was sure, based on the first few iterations, that the project was off to a good start. Sure, she knew that projects rarely stayed

Scroll to Top