The FrameWork Nivelics is an agile framework based on scrum, a framework that tends to build as effectively as possible the increment (digital product) required by the Client, fully satisfying their expectations. The framework is based on the proper interaction between roles, artifacts, and events. The foregoing seeking a total and assertive adaptation with the project management culture of each of our clients.
PO (Product Owner): Person in charge of centralizing business expectations detailing them in the digital product, in order to clearly express them to the team. Must be fully empowered, it is not advisable to have more than one person in this role.ç
Scrum Master – Digital Manager: Person in charge of applying the best agile practices in project management, in charge of proposing and monitoring artifacts, communication between client and team, problem solver and scenario projection maker.
Development team: Team in charge of building with the best development and agility practices, for the required increase. Self-organized and self-managed
Document where the detail of the requirement is consolidated, both as epic and HU that must include acceptance criteria and an assertive priority. It will be a documentary repository where the application architecture, Wireframes and approved designs are also included (if the scope includes them). This is the general basis of the list of requirements for the construction of the increment that the client needs.
Document where the HUs are selected to carry out in a time box – Sprint. It must include the sprint objective and the agreement of the Done term, that is, the variables necessary to complete the selected increment.
Burn Down Chart
An artifact that will allow us to analyze the pace and speed of construction of the increase, it is a radiator of information that helps us to project scenarios in the agile management of the project that seeks proactivity in its case.
PBI Refinement (Product Backlog)
Although it is not an event as such, it is a relevant process that seeks through joint work sessions (Client – Levels), to refine, detail the list of product requirements in terms of HU, consolidating the Acceptance Criteria.
We consider this process key in order to successfully build the increase required by the client since it represents the total alignment between business expectations and the Nivelics construction team.
Session where the entire team, together with the PO, plans all the details required to start the construction of the increment per Sprint.
Daily alignment sessions between the team. A constant session, at the same time and with a maximum duration of 15 min
Session where you see the increase, align and settle expectations with the business. This must be done for each Sprint.
Session at the end of each Sprint, where we identify opportunities for improvement and lessons learned that help us improve in the next time boxes