You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a person: junior developer that in 40 hour/week write less code lines than senior developer. How can I model this situation. Every person work the same time (40 hour/week).
How can I model this situation using Atlassian Portfolio?
Hi Samuele, There is no direct representation of a "productivity factor", but I've seen different approaches for how to reflect Junior/senior productivity in planning:
a) Reduce the weekly hours of the junior dev - even though the junior dev practically works fulltime, model him/her with for example 20 hours a week only, if you assume everything will take roughly twice as long
b) Use different skillsets, i.e., model a "Junior Dev" and a "Senior Dev" skill within an implementation stage, and define when estimating a work item, how many "senior days" or "junior days" it will take by expanding the estimates column in the backlog and entering the estimates into the according columns. this will also guide the automatic team and member suggestions to assign the juniors accordingly.
There is no right or wrong here, other teams will just factor this into the overall team velocity - it depends on how detailled you need to plan. option a is probably a more rough approximation but less effort to model, option b gives you more detailed control and also helps with member assignment, but in turn requires a bit more modelling effort with defining estimates correctly for these skills.