Practice

You have ten feature requests and capacity for three. How do you choose?

Read first: a sample answer

Fictional sample answer written by JoRoute to show the shape of a strong answer. Do not copy it: replace every detail with what is true for you.

First I would score each request on impact, effort and fit with this quarter's goal, because a shared scoring makes the choice explainable. Then I would review the top five with engineering, since effort estimates change the order. For example, a reporting export scored high on impact and low on effort, so it went in. For the seven we drop, I would tell each requester why and when we will look again. At my last company in Boston I used this scoring for a backlog of 40 requests each quarter; prioritisation is easier to accept when the planning and the reasons are visible.

Use only details that are true for you. The benchmark below is fictional.

What you type here is sent to JoRoute's server to produce this result, then discarded. It is not stored or logged, and no account is needed.

Next in your job search