Dateline: Mar. 16, 2014
During his workshop entitled, Quantifying Software Productivity and Quality, held at last year’s PNSQC, Capers Jones said: “For a capable team using capable methodologies, you can predict results. Incapable teams using chaotic methods cannot predict results.” So it seems that high quality software starts with capable people, but what is a capable person? I had a discussion in our office about this and we came up with a list of characteristics that we want to look for when hiring people. These include:
- Domain knowledge
- Technical knowledge
- Written communication skills
- Oral communication skills
- Team Collaboration skills
- Organizational and planning skills
- Problem solving abilities
- Motivation
- Responsibility and reliability
- Years of testing experience
- Years of work experience
- Certifications
We took a first shot at defining them as key elements in Software Quality Dependencies. However, I’m still wondering, how to really do an objective evaluation. Any ideas?
(Visited 15 times, 1 visits today)
