I’ve been meaning to write a series of posts on schedule games, and a story I heard over the weekend has jolted me into writing about schedule chicken. I’m most familiar with schedule chicken that happens in meetings. Usually in a project status meeting, with the project manager and the project team, especially where […]
Two different colleagues wrote me with similar conundrums. Their managers wants a “technical” project manager. One colleague was a hardware person, the other was a tester. They have both been managing software projects for several years. No one has told them they were ineffective. (I’ve discussed this issue before: The Difference Between Project Managers and
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
I’m teaching project management (and some hiring) workshops in Israel. I’ve caught up with timezones, so I may even be able to post this week. I attempted to explain why pair programming works to some skeptical project managers last week. I explained that in the best environments, a person can work 6 hours a
You’ve probably seen these elsewhere, but since this blog is for me too, I don’t want to forget about them: Why Crunch Mode Doesn’t Work: 6 Lessons. I particularly liked the origins of the 40-hour work week. Conquering the Cubicle Syndrome. I liked the idea of talking to people, building those relationships. Like Esther says
In the Hiring Geeks That Fit book, I wrote this (p. 261): Functional managers organize the work of similar people (people performing a given function). They hand off their deliverables to another group. Project managers coordinate the work of numerous people to deliver a product to the organization. Matrix managers manage people of a similar
I gave a talk at the local PDMA group called “Setting Expectations Between Engineering and the Three PMs”, attempting to clarify how the roles of product management, program management, and project management are sometimes confused, and to suggest practices that help people unconfuse them. I set up teams of people to create a little
Last week, Effern of The Vision Thing interviewed Hal Macomber, Clarke Ching, and me about project management. He made a podcast at The Sound of Vision: 02/04/2005. I was pleasantly surprised at how well Hal’s, Clarke’s, and my conversations meshed. We didn’t rehearse our answers. Effern, I appreciate you for the time you took
Caveat: I just started thinking about this, so I don’t feel particularly articulate. After reading Roy’s post of Kent Beck’s discussion “Invest in the design of the system every day”, I realized that’s what I do for project planning. Every day, I’ll adapt the work I’ve planned to do, to meet the needs of
© 2005 Johanna Rothman. This column was originally published on Stickyminds.com Partway through an assessment, the senior manager asked me, “How long should the testing take?” The answer to the senior manager’s question is, “It depends.” If you do test-driven development, there is rarely more than an iteration’s worth of at-the-end testing. When I coach