After I posted my culture series for job hunters, I saw What Your Culture Really Says. (Hat-tip to Andy Lester who pointed me to it.) This is critical: Culture is not about the furniture in your office. It is not about how much time you have to spend on feel-good projects. It is not about
I had a great time recording an interview last week with Carolyn Seaman for OnTechnicalDebt.com. The interview is over at Pragmatic Ways for Your IT Team to Deal with Technical Debt. Alexandra queued us up. Carolyn and I had a great time discussing technical debt. I even managed to mention Chris Sterling’s book Managing Software
“Juliet, I really screwed up big time. What am I going to do?” Romeo moaned as he plunked himself down in his VP’s office. “I can tell you, but I can’t admit it to my people. They will never respect me again.” “If they discover what you did—and they will—they will never forgive you if
Drum roll please… I am very pleased to announce that Hiring Geeks That Fit is also available at the Pragmatic Bookshelf! I self-published the book at leanpub, and announced it over on Hiring Technical People, and have been writing about it in my newsletter for a few months. And, not everyone knew about it. I
You might have met a manager on a bad manager day. Equally as frustrating is when you work for a manager who has rules about problem solving. I once worked for a manager who proudly said to me, “Don’t bring me a problem without bringing me a solution.” I blinked once and said, “Why would
I did a little bit of work for the ProdBOK (the Product Management Body of Knowledge) earlier in 2012. It was a little bit of work. I had an opportunity to meet Greg Geracie, along with some other very nice people. When the BOK comes out, at some point later this year, I’ll get to
In Part 1, you thought about your culture, and built your lists. In part 2, you developed your questions, and thought about the data you wanted to gather. You started with closed or behavior-description questions, so you had a place to start the conversation. Now, in part 3, you’re going to think about when to
I have an article posted on projectmanagement.com. Think Small: Five Tips for Agile Program Management is up. I’ve been quite busy with client work, and was too exhausted to blog. (I know, can you imagine??) Please comment over there.
I wish I could tell you I never had a bad manager day. I wish I could tell you I never screwed up. Nope, that would be a very tall tale. Here’s a doozy. I once told one of my employees to leave his emotions at the door. Yes, I really said that. Luckily, he
If you have an agile project larger than two or three feature teams, you have an agile program. A program is a collection of projects where the objective is one business deliverable. If you’ve managed programs before, you know how difficult it is to keep programs on track. With bigness comes more risk. One of