one-on-one

management, MPD

Management Myth #3: It's All About the Work

  Too many technical managers think that if they assign people to good work and leave them alone, people will be happy. It’s true that people need challenging and interesting work. And it’s true that micromanagement or other interference is not helpful. But people, even the most introverted people, need a relationship with their manager […]

MPD, schedule games

Schedule Game #2: 90% Done

  I was a fortunate young developer. In my first three months at work, I ran into the 90% done schedule game. I did it to myself. I estimated a particular task was going to take 6 weeks. Of course, being an arrogant and naive developer, it never occurred to me to break the task

MPD

Spending Time With the Schedule or the People?

  In one of my classes earlier this week, one project manager explained that he spent an entire day each week working the Gantt chart in a scheduling tool. He has a project of roughly 20 developers, a few testers, and a few other people (I’ve forgotten the details). I asked if he had one-on-ones

MPD, thinking

Succession Planning or Working Yourself Out of Job

In Who Wants to be a Technical Lead? I promised I’d talk about succession planning. Here’s the general idea: as someone who works for a living, your job should be to work yourself out of your current job by learning, practicing, and mastering some new skills. The less work experience you have, the easier this

MPD

Coaching is a Management Obligation

  Managers have an obligation to coach employees to help employees obtain better performance. However, managers choose when and whom to coach. Managers also have an obligation to provide feedback — which is not a choice. Every employee deserves feedback about his/her work on a frequent (weekly) basis. I’ve never met a manager who didn’t

MPD

Who Wants to be a Technical Lead?

In his comment, Rich explains, “I am directly managing 12 employees and 14 contractors doing application support and maintenance for something like 12 or 15 software products. I have most of my old team, and 6 other teams. I have been asked to develop a plan to cross train these individuals to build out a

management, MPD

Ask for More Value

David Anderson has an intriguing post, Lawyers, Unit Tests and Performance Reviews. David says “Individual team members can be set specific goals and behavior objectives…” and gives examples. I prefer that team members set their own goals with input from their managers. But the key here is that a technical person should be looking to

MPD

Visible Progress

  Rick commented on my last post that some engineers think that status checking slows them down. Mark said that engineers push back on demos and pointless measurements and then said in another comment, “progress metrics can always be free.” Here’s how and what I look for, to determine status. If I’m managing a traditionally-planned

Articles

Successful Software Management: 14 Lessons Learned

© 2003 Johanna Rothman. This article was originally published in Crosstalk, Dec 2003. This article is the outgrowth of my original talk/article, Successful Engineering Management: 7 Lessons Learned Successful managers realize that they need to balance the needs of the business, the employees, and the work environment to be effective. In this article, the author

management, MPD

One-on-Ones: Just as Necessary for Managers

Last week at the Software Development conference, I met a software director. His group, a total of about 30-40 people (I’ve forgotten the exact number) is responsible for all the software his company produces. He has two managers managing those folks. He’s busy, so although he requests that his managers have one-on-ones with their staff,

Scroll to Top