Detailed efforts estimation report with a breakdown structure by module and features is done after completion of BA phase and a clear vision of the app’s structure and requirements.
Throughout the course of the project, all efforts are being tracked and reported through the task management system (Atlassian Jira)
Any time the project stakeholders are capable to check the status of the current sprint/task and the corresponding amount of hours spent by team members.
Using a Kanban approach in Intellica all the stakeholders can track the progress within the active sprint.
Scrum is an agile way to manage a project, usually software development. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team. This is because the team will know best how to solve the problem they are presented.
This is why in Scrum development, for example, a sprint planning meeting is described in terms of the desired outcome (a commitment to a set of features to be developed in the next sprint) instead of a set of Entry criteria, Task definitions, Validation criteria, Exit criteria and so on, as would be provided in most methodologies.
Scrum relies on a self-organizing, cross-functional team. The scrum team is self-organizing in that there is no overall team leader who decides which person will do which task or how a problem will be solved. Those are issues that are decided by the team as a whole.
And in Scrum, a team is cross-functional, meaning everyone is needed to take a feature from idea to implementation.