notarapper
notarapper on Hacker News
Jira has many project types and products, and the one most commonly used is actually called Jira SOFTWARE. It literally has software in the name.
If you're building a product for software companies, you can think about how to do it better specifically for engineers
Loser gets the weekend pager duty shift
No, the data is measured through the source control (git). Jira tasks often suffer from poor hygiene since developers are tasked to update it manually, an we devs don't like manual stuff ;)
Honestly I don't think you can avoid getting measured, even if the person measuring only does it in their head. If you feel you're doing a good job than it's best for you to measure that on your own and show proof for that instead of your boss relating on their instincts...
Also if you feel you can do better than it's probably best that you understand why in order to improve that, so your boss won't have the need to let you go.
Everyone's looking at the one negative side but there are tons of positives that apply to a large percentage of the worforce
Saying that the team dynamics have set up for success or failure on the get go sheds light only on teams that are on the positive side of that statement. What if my team is on the negative side? Should I just accept the loss and continue to a new project?
I agree that the dynamics of a dev team are extremely important. But how can one drive to get better without understanding their current status?
In my personal experience, there should be an open conversation between the team on deciding what to measure and what does the team want to improve on even if the team already has good dynamics. My moral as a developer was always up when my team got props for something, because I was a part of that success.
I think the focus needs to be on the team as a whole, instead of getting dragged into a comparisons game. The developers should be aware that this isn't an individuals race.
If you work in a large organization then you will still be measured even if you're team doesn't take the measurements on their own. Good metrics can only benefit you since you can control the conversation with your own data instead of data from a corporate figure that only looks at you as another row in their spreadsheet.