Author name: Johanna

I help you identify and solve the problems that prevent you from releasing systems, hiring the right people, deciding which project to work on next. I take a pragmatic approach: what will work best for you, now? Some people call me a focuser. Some call me an accelerator. When I work with people, first we define our goal together. Typically, it's to get a better product out the door faster. I work with my clients to help managers figure out how to do the managing better, and how the technical contributors can contribute better, not to create a by-the-book system. I work with you, your staff, and your current product development practices. Together, we learn what works well for you and what doesn't. I believe in changing only what needs to be changed at the current time, to maximize your success. We work together to develop a blueprint for the future, and to build in capacity to recognize and implement change.

Articles

Management Myth 34: You’re Empowered Because I Say You Are

“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

MPD, program management

Small Internal Releases Lead to Happy Customers

If you saw Large Program? Release More Often, you might have noted that I said, You want to release all the time inside your building. You need the feedback, to watch the product grow. Some of my clients have said, “But my customers don’t want the software that often.” That might be true.  You may

MPD, program management

Large Program? Release More Often

I’m working on the release planning chapter for Agile and Lean Program Management: Collaborating Across the Organization. There are many ways to plan releases. But the key? Release often. How often? I suggest once a month. Yes, have a real, honest-to-goodness release once a month. I bet that for some of you, this is counter-intuitive.

hiring process, HTP

Six Tips for Interviewing Scrum Masters, Part 2

Now that you know what you expect from your Scrum Master’s job (the deliverables), and you know the essential and desirable skills (the first three tips), you can focus on creating the interview questions and audition. (If you have not yet read Six Tips for Interviewing Scrum Masters, Part 1 for the first three tips,

management, MPD

Management Feedback: Are You Abrasive or Assertive?

Let me guess. If you are a successful woman, in the past, you’ve been told you’re too abrasive, too direct, maybe even too assertive. Too much. See The One Word Men Never See In Their Performance Reviews. Here’s the problem. You might be. I was. But never in the “examples” my bosses provided. The “examples”

hiring process, HTP

Six Tips for Interviewing Scrum Masters, Part 1

People want to know the “secret sauce” for hiring Scrum Masters and agile coaches. I wish it was easy to provide a standard set of questions. Because your agile team is unique, your questions should be different. However, there are some common qualities, preferences, and non-technical skills among Scrum Masters. First, do a job analysis

Articles

What Do You Look for in a Servant Leader or a Scrum Master?

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

Articles

Which “Scrum Master” Are You Hiring?

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

hiring strategy, HTP

Creating a Succession Plan for Your Technical Team

We often think about a succession plan for managers. But, if you’re not thinking about a succession plan for your technical team, you’re falling prey to local shortages, and hiring the same old kinds of people. You’re not getting diverse people. That means you may not be able to create innovative, great products. It also

agile, MPD

Scale Agile With Small-World Networks Posted

I posted my most recent Pragmatic Manager newsletter, Scale Agile With Small-World Networks on my site. This is a way you can scale agile out, not up. No hierarchies needed. Small-world networks take advantage of the fact that people want to help other people in the organization. Unless you have created MBOs (Management By Objectives)

Scroll to Top