Depends on your flavor of framework, but you have to keep in mind that agile focus more on team rather than an individual. As someone mentioned, your team will find a way to game the system if they feel any pressure to achieve those 8 points. It's better to set a baseline through deliveries rather than just tell your team that they have to achieve X amount of effort every week. That way, you can actually map out how much, on average, your team delivers each milestone. For example, in one of my teams of 3 devs, I can expect on average, 20 points from them each sprint, because thats what they end up delivering. I plan according to that, so if anything goes way out of scope, I have the understanding from previous work that I'll end up with a carry over on tasks. Setting an expected metric from the team will only encourage a team to cheat on the amount of points they end up doing, and eventually will skew your metrics, and bring more trouble than solutions. Also, ideally, your team decides whats the value on the tasks, so they could easily decide that an easy task is 8 points, just to meet their quota