As you work on teams of diverse backgrounds and
expertise one that stands out is that of developers. As a product owner
it may be that you have to sit in with interviews to see if a developer coming
on board would be a good fit or not. I’ll cover a few things you’re going
to want to look for in one.
First would be hustle. Development often
is a practice of creating something out of nothing. Sometimes the projects
or problems won’t have a solution known beforehand. You’ll want to ask
your developer about a time they encountered a problem and how they worked to
solve it. You’ll want to ask:
- What was the challenge?
- What was their approach?
- How quickly did they solve the challenge?
- Did their solution work well?
- How did you prioritize?
That last one is important because while being
as perfect as possible is important, having that get in the way of actually
delivering a MVP or feature that needs to be released into dev or test
environments for validation purposes can obviously be a problem. You’ll
also need to ask them how they work with teams.
Sometimes they may need to code review someone else’s work or contribute
during a sprint retrospective. If they’re
a unicorn, i.e. a developer who really can work and create anything from start
to finish (front and back end combined as a full stack developer), but don’t
like helping others to progress and grow the overall team that may be a
problem.
Lastly you’ll want to assess their code quality.
Ideally their code is cleanly written and so it is easy to update,
processes faster, is modular, and has plenty of commenting in it so that
someone else could step right in and know what the code and functions are doing
without needing to rely on someone else to explain it and then fix it.
No comments:
Post a Comment