3 ms·

These criteria fall short and are an example of begging the question[0]. To say that "they are a good team member" as an answer to "how do I know if they're doi

by apeace 10y ago

These criteria fall short and are an example of begging the question[0]. To say that "they are a good team member" as an answer to "how do I know if they're doing a good job", doesn't really help. I have worked with many developers who fit all five of these criteria, who never get any work done. I like to break projects into small, medium, and large. A large project takes 4-6 weeks, a medium takes 2-3 weeks, and a small takes less than 2 weeks. A developer is doing a good job if they're completing two large projects per quarter. They're doing great if they're completing more than that. Instead of two large projects it could be 4-5 medium projects, etc. Many projects are smaller than a "small", so your team should be bundling those together into some kind of focused "project" or "sprint" that is targeting a certain area and achieving a user-centric goal. I also like to measure user satisfaction by sending surveys about new features. Does it solve a problem for you? Is it better than what we had before? Was it buggy? Score from 1-5. These metrics aren't perfect, but in my experience they go a long way towards measuring developer performance quantitatively. [0] http://begthequestion.info/ http://begthequestion.info/

6DM 10y ago
When you say projects, do you mean finished applications or are you talking about features?
- apeace 10y ago
  Either, but usually features. When it comes to building a brand new app, you need to break it into multiple large projects. The first one might be "create a new Cordova app with just a login page", since bootstrapping all the Cordova stuff might take a while. The next project would be "add features X and Y to the app, and deploy in the app store", etc. I constrain projects to no larger than 4-6 weeks because I work in startups, where priorities shift constantly. You need to be able to finish Phase 1, and potentially say "another important priority came up, we need to push back Phase 2 by 2-3 weeks while we complete this other medium project".

by apeace 10y ago

6DM 10y ago

When you say projects, do you mean finished applications or are you talking about features?

apeace 10y ago
Either, but usually features. When it comes to building a brand new app, you need to break it into multiple large projects. The first one might be "create a new Cordova app with just a login page", since bootstrapping all the Cordova stuff might take a while. The next project would be "add features X and Y to the app, and deploy in the app store", etc. I constrain projects to no larger than 4-6 weeks because I work in startups, where priorities shift constantly. You need to be able to finish Phase 1, and potentially say "another important priority came up, we need to push back Phase 2 by 2-3 weeks while we complete this other medium project".