In the software industry, we toss around terms such as “Holacracy,” “meritocracy,” and “collaborative environment.” We claim to hire for skills. That’s not what I see. I see hiring managers hiring people just like them (mini-me’s), people who went to their schools, make similar life choices, and are roughly the same age. That’s because these […]
How can you use certifications in your hiring? In Part 1 and Part 2, I discussed the value of certifications and hiring traps. Let’s see how to be positive about certifications and use them during the hiring process. I’ve already said that a certification might be a sign of perseverance and interest in the field.
In Part 1, I discussed the issue of certification vs. experience. One of the problems in using certifications to discriminate for or against people is that some people might have the experience you want, and might not have the certification paper that represents that experience to you. Here’s an example. I coached a project manager
There are a ton of certifications these days. Many demand only that you sit through a 2-day or even 1-week class and then take an exam. Some certifications demand that you prove you have worked in the field for some number of weeks/hours the previous year or so. Most certifications do not demand that you
, In my session at Agile 2015, (Agile Hiring: It’s a Team Sport) one participant asked me if I hire contractors the same way I hire employees. I do. I use the same approaches for reviewing resumes, phone screens, interviews and decisions. The one difference is the offer—instead of a yearly salary paid in some
You have an open position. You have two internal candidates. You’re going to hire one of them. (See Two Candidates, One Position.) Now you have a problem. You have one person who will not be happy. This often occurs when you have two candidates for technical leadership or management positions. You might have a political problem.
We talk a lot in agile about generalizing specialists. Scott Ambler has a terrific essay on what a generalizing specialist is: Has one or more technical specialties… Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new
Now that you know what you expect from your Scrum Master’s job (the deliverables), and you know the essential and desirable skills (the first three tips), you can focus on creating the interview questions and audition. (If you have not yet read Six Tips for Interviewing Scrum Masters, Part 1 for the first three tips,
People want to know the “secret sauce” for hiring Scrum Masters and agile coaches. I wish it was easy to provide a standard set of questions. Because your agile team is unique, your questions should be different. However, there are some common qualities, preferences, and non-technical skills among Scrum Masters. First, do a job analysis
In my article, Which “Scrum Master” Are You Hiring?, I suggested you articulate the type of leader you might be hiring. Why? You might not be hiring a “Scrum Master” at all—but you are likely hiring a servant leader. In this article, let’s discuss the kind of qualities, preferences, and non-technical skills you might need