The Northeast is in the midst of the Blizzard of 2015. Right now, I’m sitting snug in my home office, waiting for the blizzard to be over. I still have power and heat, which is great! I was wondering—what do you do on a snow day? If you’re agile and you are accustomed to having […]
Summary: Competition between teams does not improve performance. In fact, the added stress may shift team members’ focus from creating a quality product to self-preservation due to fear of failure. Johanna suggests managers emphasize collaboration between teams over competition. “Jonah and Sarah, this next round I want to initiate a little competition to see whose
I was coaching a new client. He’s a senior guy with several directors reporting to him. He had stopped his staff meetings for a while because no one wanted to participate. Hmm. I almost asked him why, but he kept talking. “What do you think of this format for my staff meeting? Everyone does a
“Larry, I need VP approval for this,” said Josh, the director of engineering. Larry looked annoyed. “This is only $30. Why am I signing off on $30?” “Because I have no signature authority on anything. Even though I’m a director, I can’t sign off on any discretionary purchases. I have no capital equipment authorization. I
In my article, Which “Scrum Master” Are You Hiring?, I suggested you articulate the type of leader you might be hiring. Why? You might not be hiring a “Scrum Master” at all—but you are likely hiring a servant leader. In this article, let’s discuss the kind of qualities, preferences, and non-technical skills you might need
Have you looked at some of the ads for Scrum Masters lately? Some ads include the need for PMPs or they say they will give you a bonus if you complete the project at a certain time or to someone’s satisfaction. Some talk about hiring the team or about managing the customer’s expectations. Some talk
Summary: A new approach to projects or a new tool is not a quick fix or a silver bullet. Too often, you have ingrained, systemic problems that require a cultural change. That doesn’t mean a new approach or a new tool won’t help. It can. But you also need to adjust the environment that caused
Summary: It is unfortunate that the department attending to employees is called “Human Resources.” That language colors what managers call people in the organization. But the more you call people “resources,” the more they become interchangeable—and more like desks, or infrastructure, or something that is easily negotiable. Resources are not people. People are not resources.
“OK, I’m really glad we can start this management meeting now. It’s time to talk about standardization. I want to create standards for our projects. I want to standardize on agile for all of our projects.” Joseph, the CIO, thought all of his directors would be pleased. “Uh, Joseph, are you telling us you want
In a recent estimation workshop, one of the participants asked, “How do we estimate something we’ve never done before?” “Is it a feature or a project?” I asked. “A feature,” she said. “How do you do things now?” Based on her previous comments in the workshop, I suspected she was pretty good at what she