Intellias applies Scrum methodology in order to ensure the utmost flexibility in project development. At the beginning of the project, the product planning takes place, including the creation of Product Backlog, which contains the list of functionality and requirements, prioritized according to their importance. During this phase we also make the initial estimate, which evaluates the scope in comparison with the other stories.
The next phase is sprint planning, during which we set the goal for the sprint, the list of the team members and their workload, sprint backlog, stakeholders' demonstration date, exact timing of everyday Scrum.
Sprint Backlog represents the list of User Stories, which the team commits to complete. The list of User Stories is formulated by the project team in collaboration with the Product Owner and considers story importance, size (effort estimate for the story) as well as expected productivity of the team.
The stories, in which the number of story points do not exceeds the forecasted productivity of the team in points, are qualified for the sprint. If several free story points are left, the sprint could be completed by the stories from the product backlog, which have less importance and are logically connected to the main stories of the sprint.
Then we proceed to the sprint itself. The team develops the required functionality. After the beginning of the sprint, the requirements and the list of the user stories are not allowed to be changed.
Short daily scrum meetings are held, with the 3 main questions being discussed:
- What have you done since yesterday?
- What are your plans for today?
- Do you have any problems that prevent you from achieving your goal?
The current status of sprint execution is monitored by the sprint burndown chart. When any problems are identified during the sprint execution, the team immediately provides appropriate solutions and corrective actions.
Every sprint ends up with the demonstration of the results to the customer and all the stakeholders.
After the completion of the sprint, the retrospective discussion and summary is held. Afterwards, the planning of the next sprint, taking into account the retrospective sprint results, is done. After the completion of all the sprints, the project proceeds to the final stage.
- Transparency for the customers and stakeholders
- Easy procedure for change requests
- Quick problem identification
- Immediate availability of the results for the inspection
- Project progress is obvious (determined by the fully-functional application)