Johanna Rothman

Johanna Rothman

Profile picture for user johanna

Member for

13 years 6 months

Johanna Rothman, known as the “Pragmatic Manager,” provides frank advice for your tough problems. She helps leaders and teams see problems and resolve risks and manage their product development.

She was the agileconnection.com technical editor for six years. Johanna is the author of these books:

Read her blog and other articles on her site, jrothman.com.  She also writes a personal blog on createadaptablelife.com.

Company
Rothman Consulting Group, Inc.
Job Function
Consulting
Job Title
President
Industry
High Tech
Interests
Agile
Leadership
Lean
Software Testing
Country
United States

Johanna Rothman, known as the “Pragmatic Manager,” provides frank advice for your tough problems. She helps leaders and teams see problems and resolve risks and manage their product development.

She was the agileconnection.com technical editor for six years. Johanna is the author of these books:

Read her blog and other articles on her site, jrothman.com.  She also writes a personal blog on createadaptablelife.com.

All Articles by Johanna Rothman


All Stories by Johanna Rothman

Shirt tag saying "One size does not fit all" What’s Your “Size” of Agile?There are approaches to agile that sound great on paper, but will they really be the best choice for your team in practice? Instead of standardizing on any form of agile, think about the results you want. Why not create the environment that works best for you? There's more than one way to do agile.
Self-managing team Who’s the Boss? Let Agile Teams Manage ThemselvesThis idea of a team in charge of itself is difficult for many people to accept. Traditional practices condition us to wait for someone to tell us what to do, and managers are accustomed to controlling everyone’s work and knowing everyone’s status. But agile teams can manage themselves—in fact, it's essential to agile.
Learning An Agile Mindset: Learning Early, Not Failing FastAgile encourages teams to continuously improve through learning. One of the phrases associated with this process is "failing fast"—trying new things and taking lessons from mistakes as you go. But Johanna Rothman thinks "learning early" is a better phrase. That change in terminology can give you a happier mindset.
Agile culture Creating Your Organization’s Agile Culture

Some organizations decide they can just “install” agile by simply telling the technical team members what to do. It never occurred to the managers that much of what makes agile successful is the organizational culture. It's important to recognize that agile is something you work toward—with the whole team.

Problem management Are You Problem Solving When You Should Try Problem Managing?Usually in our projects, our goal is problem-solving. We find the root cause of a problem and experiment until we eradicate it. But is solving always the right path? Sometimes, our problems are temporary and only require a patch. In those cases, problem managing is probably the better choice.
Why? Know the “Why” behind Your ProjectsEvery project has its own unique reason for existence. We often work on projects to deliver some kind of return for our organizations. When you start a project, do you know what that return is? When we know the reasons behind our work, we can be more successful—knowing why can create success.
Feedback loop Shorten Your Feedback Loops to Build Better Software, FasterWhen we have short feedback loops, we are still in the moment for that feature. We still have the context. The longer the feedback loop, the less likely we are to still have all the context for the feature because we are on to the next piece of work. How long are your feedback loops? Can you shorten them?
The Problem with Expectations for Agile TeamsToo many people sell agile as a way to get better, faster, cheaper. But the problem with setting these high expectations for agile teams is that we too often neglect the roles of and expectations for agile managers. Managers are responsible for creating the environment in which people can deliver great work.
Comparing apples and oranges Why Process Standardization Is a Terrible IdeaHaving a standard process everyone uses makes sense in theory. You could compare metrics and progress across teams and projects. But it practice, it becomes like comparing apples and oranges. Teams aren't all the same, and neither are projects. Each team need its own optimized way to deliver value.
When Can You Honestly Call Yourself Agile?If you're working more iteratively and incrementally and things are better for your team and your customers, can you call yourself agile? As long as you're improving, does it really matter what you call yourself? Johanna Rothman says yes. Unless you're following the Agile Manifesto, you aren't truly agile.
Scaling Agile: Reasonable Practices for Program ManagementIn a big push to scale agile, it can help to think of scaling agile as program management, or coordinating projects where the value is in the overall deliverable. Consider how you can deliver your product one small, finished bit at a time. If you deliver value as often as possible, you see real results.
Think Agile to Work Efficiently and EffectivelyOf course it's important to work efficiently, without wasting time, money, or energy. But working effectively is just as important. Agile cycles between creating, testing, and getting feedback, allowing us to work in small chunks and make sure what we're producing has the most value. That's effective.
Do You Design Your Software Process for Flexibility or Repeatability?Manufacturing design looks a lot like software: You iterate through possible solutions, and the manufacturing itself is about repeating the making process. But building software means learning about the problem as you solve parts of it. For that, you want flexibility. How do you find your ideal process?
Agile Methods for Tackling the Work You Don’t Want to DoWe all have work we don't want to do. Some of it is boring or unpleasant, but there's another type: work we don't know if we can finish to our satisfaction. It's hard to tackle a task you're not an expert at. Johanna Rothman offers two classic project management approaches to face the work you're putting off.
The Value of Taking BreaksMany people think breaks are a waste of time; if you keep working, they reason, you'll get more done. But what is the quality of that work? And how do you feel at the end of the day? Breaks are beneficial to you and to your work. You can refresh yourself, gain a new perspective, and evaluate what you've done.
Make the Effort to Invest in YourselfTo keep relevant in an ever-changing industry, you need training. But many companies don't provide or reimburse for continuing education. That means you're responsible for your ongoing career development. Don't fret; you don't have to spend a lot. And the more you learn and practice, the more value you have.
Agile Does Not Equal Scrum: Know the DifferenceSome people say “agile/Scrum,” as though they’re the same thing. They're not! Scrum is just one way to approach agile. Johanna Rothman defines each concept and also addresses kanban and Extreme Programming, two more approaches. Don't write off agile until you've explored different ways it could work for you.
Start the New Year with a RetrospectiveThis new year, instead of a resolution, consider a retrospective. Rather than just setting one large goal for yourself, you review what you've been doing, what's been working and what hasn't, what you want to accomplish, and what small steps you can take every day to reach your objective.
What Do You Believe?Many people in the agile community believe their way of doing agile is the only right way. This is supported by confirmation bias, which lets us only see facts that support our beliefs. We deserve data-based approaches to determine what leads to the best outcomes. Can you look beyond your personal beliefs?
Making Time for ReflectionHow often do you reflect on your career or life? It can be difficult to examine how you work and live to confirm that you are where you want to be. But using some of the same questions and techniques employed in agile retrospectives can help you evaluate your personal choices, too—and brainstorm ideas.
Self-Improvement, or How to Work Up to Your PotentialHave you ever been told you have “a lot of potential”? It's meant as a compliment, but it can be a little insulting if you feel you're already working up to your potential. Johanna Rothman shares the steps she took to gather data, assess her work, and discover whether she's working up to her full potential.
What Are You Measuring?Many teams do single-point measurements in their projects. But that doesn't give you a good long-term picture. When you look at multiple-dimension measurements—especially trends over time—you learn more. You can take those trends into a retrospective to investigate how your team could work better.
What Do You Do When You’re Stuck on a Problem?Some problems we can resolve on our own in a couple of minutes. Some take more time, or we can’t resolve them alone. What do you do then? Johanna Rothman suggests scheduling a timebox to find a solution alone, then if that doesn't work, using one of the ideas in this story to "unstick" yourself.
Become an Estimation LeaderSingle-point estimates, whether they are for a budget or a schedule, are never correct. Things happen. Demanding that your team provide you an exact number and then treating that as a guarantee is not being a good manager—or being agile. What if you could provide a different estimation leadership?
How Much Time Do You Spend Doing Your Job versus Learning Your Job?When was the most recent time you decided to learn something specific about your job? Many organizations do not build time in for learning in the workday. Instead of thinking you're too busy doing your job to take time to learn, ask yourself if you can incorporate learning into everything you do.
What Drives Your Behavior at Work?Do you know what drives your behavior at work? Is it the sheer fun of programming or testing? Is it about serving customers or finding solutions to problems? Think about your mission and consider your principles when you debate potential risks and outcomes. Then, you can start exercising leadership.
Who Is Responsible for Happiness?No one can take full responsibility for another person's happiness. However, a manager can create an environment in which a team can thrive, and that leads to happy environments. Being a servant leader means you don’t micromanage; you manage for outcomes. Is team happiness part of your culture?
Let’s Stop Discussing Post-Agile: We Still Can’t Agree on AgileSome people in the software world feel that agile focuses too much on problems of the past. These people have moved on to what's being called post-agile, which shakes up the process. Johanna Rothman, however, thinks they're getting ahead of themselves—first, we need to keep working to achieve agile.
What Do You Do on a Snow Day?Extreme weather happens, and it can make getting into the office difficult (or impossible). Do you try to collaborate remotely? What if everyone else is taking the day off? If you still want to get some work done (instead of building snowmen), here are some perfect tasks you can do on your own.
If It’s Tuesday, It Must Be Time to Innovate

If you feel like you are getting stretched too thin at this time of year and just have too much to accomplish, Johanna Rothman understands. She has some suggestions that help her get back on track, including prioritizing the big things first, taking breaks, and not letting yourself stay stuck.

What Do You Want This Holiday Season? Three Tips for the OverwhelmedIt’s the holiday season again. As you run around preparing for everyone else, consider what you need. Especially when you are stressed—and the holidays seem to bring out the stress in everyone—take time for yourself. Prioritize, manage tasks, and create action plans, and you can enjoy the season!
Is Your Career a Trick or a Treat?

Have you ever felt tricked by a job you thought would be a treat? Or have you had a job that was once a treat but turned into a trick because you kept doing it year in, year out? Don't get spooked. Johanna Rothman has some tips about what you can do to turn your job into a treat once more.

Beware of Serial Status MeetingsStandup meetings are great in many instances. But if you're calling serial status meetings, you may find that people will stop attending. To engage employees and address issues quicker, you may want to try lean coffee or a problem-solving meeting. Read on for tips on involving your team.
Take a More Agile Approach to Problem SolvingYour managers want you to estimate features or projects months or even years in advance. But the work changes—or the code changes, or the people on the project change. What you thought might be a reasonable estimate four weeks ago looks wacko when you revisit it in six months. What can you do?
AgileConnection Update: Transitions, Distributed Teams, and ManagersJohanna Rothman, technical editor of AgileConnection, highlights some of the content that's being published on the site, including articles about using certain agile practices on an otherwise traditional project, the challenges of distributed teams, and another myth for misguided managers.
Tips for Improving Your Geographically Distributed Agile TeamMany people on agile teams have at least one person who is not collocated. Those on collocated teams indicate that more of their projects are successful; those on far-located teams have the highest number of challenged projects. What can you do if you're part of a geographically distributed team?
How Serving Is Your Leadership?Some managers don’t realize that they are not their titles. The value they should bring is the "plus": the management, plus their relationship with their peers, the people they manage, and the systems and environment they enable or create. If you're a manager, are you providing servant leadership?
Design Each Team’s Project to Optimize at the Program LevelIf you are part of a program, it’s not enough to design your project for your team. You have to consider the needs of the program, too. Each team needs to ask itself, “How do we deliver what the rest of the program needs, as the program needs it?” Aim to meet deliverables—not control your people.
Let Your Teams Design Their Own Approaches to AgileIf you are thinking of agile as part of a program, each team has to have its own approach to agile because each team has its own risks and problems. If you treat people as adults, explain the desired results, and provide training and other resources they need, they are likely to succeed.
Project Management Is Not a Dirty WordSome people dislike the idea of agile project managers, but for teams transitioning to agile, there is a place for management. That place is creating an environment in which the team learns how to self manage. Read on to discover how a PM should offer support and servant leadership to an agile team.
Four Principles for Designing Your New Agile ProjectThere are guidelines for those transitioning to agile. You have to know how your product releases and how often. Next, you should determine how complex your product is. Johanna Rothman helps you determine what type of product you have and how you can work on it while making the transition to agile.
How Management Indecision Loses Money and Hurts Your Project PortfolioWhen managers can’t decide which projects to undertake, they end up making a decision—to not decide. They don’t fund the potentially transformative projects; they go with the safe bets. The difference between when a project goes on the backlog and when it's started eats into your maximum revenue.
Four Steps to Avoid Micromanaging and Get Good Work ResultsThere is a big difference between micromanaging people and understanding their state. If you need a project done quickly, you may be tempted to stand over employees' shoulders asking, "Is it done yet?" But if you leave the team alone and simply check in regularly, you'll get better results.
Calculating the Real Cost of Multitasking on Your ProjectsThe cost of delay due to multitasking is real. It’s invisible to most people, especially management. It’s not just the cost of time lost due to context switching; it’s the fact that projects don't get out on time, which hurts your maximum sales revenue. How do you calculate these costs of delay?
The Cost of Delay for Not Shipping on TimeThe cost of delay is the way to think about the revenue you can lose plus the cost of continued development. When you delay your release and don’t ship on time, you miss the revenue from the maximum sales times. Shipping on time isn't always easy, but it's easy to see why you need to.
Why We Should Get Rid of Bonus-Based Pay

There are several problems with basing a knowledge worker's pay on a bonus. In a team-based organization, management often doesn't know who did exactly what work; people concentrate on their own objectives rather than working together; and whether some targets are hit depends on too many factors.

The Power Index: Why a Transition to Agile Is a Cultural Issue, TooIn countries with high power indices, it’s more difficult for people in less powerful positions to talk to people in more powerful positions. A transition to agile exposes this power differential, which can be uncomfortable or intimidating. Read on for ways you can help people adopt agile practices.
Four Truths Every Manager Should Learn

Many managers seem to be in the wrong position. They don’t know or don’t care about management, and that leads them to do crazy things. It’s OK to be an unseasoned manager. Everyone starts somewhere. But you must be willing to ask for help and not think you have all the answers. Read on for advice.

Understand Your Teams' Concerns about Moving to Continuous IntegrationHow do you help your teams bring the entire product together on a periodic basis, regardless of their technical practices? Continuous integration is a real problem for a number of reasons. But you can’t solve the problems you don’t know about, so ask for the impediments first. You may be surprised.
Don't Just Work Longer—Work SmarterPeople who work long hours assume they're also working hard—but that doesn't mean they're working smart. If you have a lot to do, you want to work smart—not just work a lot. How do you discover how much time spent working makes you the most productive? Run this experiment and gather some data.
Handoffs Aren't Bad—Just Think of Cooks in the Kitchen

Some people are confused by the word handoff. They think it means people have not done their jobs and other people had to cover for them. Sometimes that happens, but usually it's more like when one chef cooks his part of the meal, then hands off the plate to the next chef to finish the dish.

How Many People Should You Manage?As a manager, you should be providing a learning environment, coaching when it's wanted, and building trusting relationships. You should dedicate yourself to the employees, and you need time to meet with them often. This can be hard to do if you're managing too many people. What's the right number?
Reduce Your Work in Progress to Make Your Whole Team More ProductiveWhen you are a manager, you have to limit your own work in progress. If you don’t, you can’t pay attention to the most important work you have to do, which can affect your whole team. Read on for some tips about how best to manage work in progress, how transparency helps, and achieving efficiency.
Know Your Program: Which Team Are You Managing?Some program managers whose organizations are transitioning to agile are not always clear which program team they are managing. That can be because the organization doesn’t always realize it needs more than one program team. Here, Johanna Rothman describes some program teams and when to use them.
The Cost of Continuous Integration Is Well Worth the TimeIf you don’t start putting software together a little bit at a time, it gets harder the farther along you go. The cost of continuous integration sometimes can seem high, but it is often well worth the time, even on a large program. Here are some steps to help you move to more continuous integration.
Five Elements for Creating a Healthy Project CultureIn a healthy project culture, people work together to accomplish the goal. It doesn’t matter what approach is used—phase gate, iterative, incremental, or agile; health is key. Read on for five elements of a healthy project culture that can help set up your program, small or large, for success.
The Truth behind Software Development EstimatesThe problem with estimation is that software is not construction. We can’t create software the same way we build a house or manufacture anything else. We can't say, “We can build this software for x dollars per square foot.” But other people often think of our estimates that way. What can you do?
Ease Your Transition to Agile and Learn What Your Team NeedsIf you are starting a transition to agile, first ask yourself: Why do we want to transition to agile? Agile is about the ability to respond to change. Once you understand what your organization’s issues are and you can resolve them, you can move to a program.
What You Can Learn from Sony about Cost Versus ValueSony is now worth a fraction of what it was ten years ago because the company started asking, "What will make us the most money right now?" Your question should not be how much something costs; you should be asking, “How much value will this project provide?” Learn to tell the difference.
Good Project Managers Don't Move Employees Like Chess PiecesWhen you move people from project to project before they've finished their work, you deny them the opportunity to learn domain expertise. You want to leave people to finish projects, learn the product, and create solid teams. Good managers don't move employees like chess pieces.
Advice for Geographically Distributed Teams Transitioning to AgileYou have any number of choices for your lifecycle if you are a geographically distributed team transitioning to agile. But some choices are better than others, and you may need a coach. Similarly, there are many tools available, but you, the team, should choose which you use, not your management.
For Agile Program Iterations, Short Is BeautifulFor programs, the risks are too high to have longer times between integration points and demos. Waiting too long increases potential delays, which increases risks. You want feature teams in your program working together, so you want short iterations and small stories connecting often and everywhere.
Think Test Offshoring Is Automatically Less Expensive? Think AgainWhy does senior management split developers and testers? Because they do not realize that software is about collaboration. Success happens when you hire feature teams in one location. When CIOs are under pressure to reduce budget and release faster, they think offshoring—but that has other costs.
Coach New Project Team Members to SucceedManagers need to conduct one-on-ones, and it's especially important with new people. Managers might not need to perform the on-the-job coaching, but they need to make sure the coaching gets done by someone. Otherwise, new hires are not going to perform at the levels they should—or could.
Working Your Way Out of Large Technical Debt in a Small ProjectWhen you transition to agile with a small project and you have a reasonably sized codebase, chances are quite good that you’ve been working on the product for a while. You have legacy code—and that code comes with technical debt. Johanna Rothman has ideas about how to work yourself out of it.
Which Delivery Option Is Right for Your New Agile Program?With agile, you have delivery model options you didn’t have before. You can do continuous deployment or phased deployment, or stick with a traditional rollout. There is no hands-down best model. What you choose should depend on what your team and your customers need. Here's how to figure that out.
When Managing Multiple Teams, Think Networks—Not HierarchiesThe more complex your program, the harder it is to communicate. But contrary to some management styles, the larger your program, the less you want a hierarchy. It's better to assemble networks of people equally responsible for their problems. Read on for tips on how to organize for multiple teams.
Four Steps to Managing Programs with Agile and Traditional ProjectsYou are a program manager with some agile projects and some traditional projects in the midst of an agile transition. How do you manage the program? You have to help the traditional project managers work in some new and different ways. Here are four steps to help the adjustment go more smoothly.
Making Telecommuting Work for Your Product Development TeamCan you make telecommuting work for your organization? Of course you can. The question is this: Will it make your product development proceed faster, with more ease and less cost, and allow you the most flexibility? If not, you may want to reconsider having employees telecommute.
Meet These Preconditions Before You Think about Project EstimationsWhen estimating a project's release or budget, you can have only one number-one priority. If management has not thought about the constraints, they may be asking employees to cram in too many features with insufficient time. Read on for some conditions and guidelines about estimating for a project.
Inertia Is Bad: How to Generate Momentum in Your Agile ProgramIn a large agile project or program, you know how hard it can be to keep things moving. To prevent inertia from slowing an agile program, there's one simple objective you can assign everyone at the start of an iteration to help the team build momentum. Read on for great advice from Johanna Rothman.
Managing the Stream of Features in an Agile ProgramIf you keep a stream of features moving in a program—even with many feature teams—you are OK as long as the project teams keep talking to one another. You are not OK, however, if someone decides, “I own this code and no one else can touch it.” Johanna Rothman says how agile programs should operate.
Use Personal Kanban to Manage Your Job HuntJob hunting is a complex project, and one way to manage it is to use personal kanban to organize your search. Johanna Rothman gives suggestions about how to create your kanban to make it work best for you, where you put your to-do's and call-backs about job offers, and executing iterations.
Agile Is Not for Everyone (and That's OK)Agile is not just a lifecycle, but also a huge cultural shift for the entire organization. In this article, Johanna Rothman details some of the issues that prevent teams from transitioning to agile and discusses what a team's options are if it decides agile is not the way to go.
We Have Created Our Own Shortage of PeopleIf you are a hiring manager looking for people, don’t create your own shortage of candidates by insisting on too-tight job descriptions. Technical skills are helpful but not critical. Try training a candidate into a good fit for your position.