E0 estimates are the estimated done on the basis of high level scope, usually done in sales cycle before the project starts.
E0 is revised after the project starts and requirement analysis is done. The project manager prepares E1 which is more firm estimates based on low level requirement discussions in the project requirement analysis phase.
Ask the person asking you.
This advice applies in general - whenever someone uses a term with which you are unfamiliar, ask them what it means.
This carries a slight risk of making you seem ignorant. Which is far better than the large risk involved when making an incorrect assumption, which can end up being costly to the project.
Not to mention, it's ...
Velocity was never intended as a performance measure. It is designed specifically to help teams to estimate their capacity in future sprints. If it is being used to criticise the performance of teams then you have a problem.
What this highlights is not that there is an issue with the Fibonacci scale, but how important it is that everyone involved is ...
Now that developer has to defend herself as to why her velocity has
If the developer is having to defend velocity changes on sprint by sprint stats alone, that is completely wrong. The team will know if someone isn't putting in the effort needed.
It might be that a three, or five, sprint rolling average might be a more realistic measure.
I'm assuming your dev methodology is Agile (or SCRUM?) and if so, then these are pretty big "Tasks".
In JIRA I'd call the size of work you're describing, a Feature. Features should be broken down into User Stories. User Stories broken down into Tasks.
But the answer to your question is Story Points & Velocity.
Here's a great post by Atlassian ...
I feel that this approach, trying to determine team performance from above, might not be perceived well by the team and may backfire.
As another answer noted, this may well turn your team's focus into looking productive rather than being productive.
Some people may do it just to protect their jobs. But I also know from experience that people love to game ...
Let us assume that you have a completed Technical Spec, where everything is well defined.
Note that the answers overlap and complement each other.
How many front-end developers are needed?
Assuming you are going to use the same language for both platforms, but it's completely different code then the answer depends on how fast you want it completed.
You are entering dangerous territory here. Why?
Because programming is an art.
If you start measuring things like lines of code written then instead of writing clever code, they will write verbose code.
If you start measuring things like tasks finished then they will finish lots of tasks, but ignore quality, like implementing corner cases.
If you start ...
If you have already started the sprint - i.e. its an active sprint and you want to see the 'burn-down chart' in hour instead of story points, then you can go to the settings of the board in Jira you can change the burn-down to look at hours instead of story points.