Once you’ve seen some evidence of a lifecycle, look for the practices the candidate has used on projects. To be honest, I can imagine seeing one or two of these on a resume; certainly not all. Test-driven development (likely to be on a resume) Unit testing (likely to be on a resume) Pair programming (likely […]
I spoke with a recruiter yesterday about how to hire people for an agile team. Her client had suggested she look for people with XP experience, and that candidates have “stand-up meetings” on their resume. Oh no. Looking for agile people is much more than keywords.If you’re recruiting for an agile team member, first, decide
This is a little off topic, but it’s a big deal to me 🙂 We hit a major milestone this week. Daughter #1 is off to school. (For my non-US readers, that means university.) We have just one daughter at home, who starts high school this week. Sending a child to school is not like
I’m in the midst of writing the PM book (which is why I haven’t blogged much). One of my tips is that projects have both requirements and goals–and that the PM (at least) needs to know the difference. A requirement can be a use case, user story, a shall statement, whatever. So can a
I’m leading several sessions at SD Best Practices, Sept 11-14, 2006. Here’s the list: Monday, Sept 11: Coaching Your Peers and Staff to Excellence (half-day experiential) Wednesday, Sept 13: Predicting Project Completion Wednesday, Sept 13: Develop Your Interviewing Skills Thursday, Sept 15: Managing the Project Portfolio Thursday, Sept 14: Successful Software Management: 15 Lessons
There’s a fascinating email thread started by David Anderson about What would Agile Auditing Look Like?. Part of the discussion stems from what the definition of an audit is. Audits are about compliance to a defined process. Do we need audits? Sure, for some projects. I would very much like to know that any project
A few weeks ago at the “Hiring for an Agile Team” session, the group generated a number of behavior-description questions. I promised I would post them, so here they are: “Tell me about a time you made a mistake.” Using the context of shipping/releasing a product late: “What did you change?” (Notice the past
Want to save time on your next project? Improve working relationships? Understand what contributed to your success–or what didn’t? You’ll need a retrospective to do these things, and if you want a great retrospective, you’ll buy a copy of Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen. A retrospective provides
I received some great comments on Why Puzzles and Riddles Discriminate. Adam has a terrific list of the things he’s looking for when he uses “puzzles and/or brainteasers and/or random programs to test”: Do they give up right off the bat? Do they ask questions or sit silent pondering? Do they make different attempts or
I’m very pleased to be speaking at another Kennedy Audio Conference. See information at Building a Hiring Strategy.You’ve noticed that I’ve been blogging about some of the hiring strategies. Well, there are 12 strategies that I’ve noticed, and I won’t blog about the rest until after the audio conference. I do hope you join me.