L4 SWE/$300k/8yoe Transferred to new team and project after a reorg. Just found out dev productivity expectations here include number of points completed per sprint, not just number of changes and lines of code submitted. I guess they want more granular sprint tasks.
I measure my personal success this way and try to be at the top of my team, never behind. The one benefit of Agile is being able to track your progress using points by measuring how difficult tasks are. It makes more sense to gauge productivity this way than using LOC. TC: 105K
Yeah, but to do it properly it seems like I need to make tasks extremely granular to avoid lengthy laboring on a very large task that was estimated as medium.
Points Inflation or backstabbing are the only answer to mediocre management practices.
Have used points to gauge velocity in the past but find that only is moderately effective on less skilled teams. Prefer to assign credit based on work product evaluated by peers and higher level eng staff, which enables more nuance and ensures there is adequate knowledge transfer of the work being done around the org (visibility). Plus enables feedback and reduces time spent on arbitrary agile ceremonies that are ultimately meaningless.
Is there a silver bullet to getting your work product evaluated without explicit buy-in for that sort of evaluation? Everyone is so focused on spending time on their sprint points, it's hard to imagine anyone willing to pay attention to something that isn't on the critical path to completing the points they're assigned for their current sprint.
That description of sprint points is exactly why I dislike sprint points. Advocate for code quality and preemptively share your work (pull request or similar) with your team and other people in your circle, be willing and open to criticism and comments and explicitly ask people to share their thoughts. Also helps to have/or establish an explicit branch model and code review process, often with specific individuals responsible for gathering reviews and making decisions about whether or not to approve the code. Have an explicit rubric for what is an is not acceptable code quality and evaluate every PR based on this rubric. Also can make a point to have live sessions with screen share to review each pull request line by line, and demo the change and answer questions (should include original developer to address these things as they should be most familiar).
Health & Wellness
Yesterday
959
Lasik cost
India
12h
539
'Hindutva': The Radical Hindu Ideology That Seeks to 'Push Christianity Out of India’
AMA
Yesterday
1227
PM Manager, early 40s, married and ENM (Ethical Non Monogamous) AMA
World Conflicts
9h
381
Is "From the River to the Sea" So Wrong?
Tech Industry
Yesterday
273
Which degree is more worth it?
Every button color fix should be 13 points