Agile methodologies

Take control of the situation with SCRUM

This methodology allows teams to manage complex projects creating a collaborative culture: hikin is a tool that unites teams around a single objective and promotes iterative and incremental delivery.

The 5 SCRUM Ceremonies: keys in process management

Objective of these events is to comply with processes control endowing them with a sense of being that makes them essential for this methodology.

1. Sprint Planning

Sprint Planning is a meeting that takes place at the beginning of each Sprint where entire Scrum team participates.

2. Daily Scrum

Daily Scrum, commonly known only as "The Daily", is a 15-minute daily meeting in which Development Team is exclusively involved.

3. Sprint Review

Meeting at the end of Sprint, where a increase is presented for inspection and corresponding adaptation.

4. Sprint Retrospective

It happens at the end of Sprint and is done in conjunction with Sprint Planning. Its objective is to reflect on latest Sprint and identify possible improvements for the next one.

5. Sprint Grooming o Refinement

Participants of this meeting are the entire Scrum team, as well as any additional resources that PO considers necessary and that can help clarify requirement.


Repeat whole process, trying to improve communication between Team and Client, identifying those points that may be improved.

Be Agile my Friend

What is a Sprint?

Sprint is the heart of SCRUM, a time interval of maximum one month, where the increase of a product is developed, potentially deliverable. Sprint is continuous, that is, its duration should not change while product development is underway, and can be interpreted as a measure of constant rhythm over time, allowing us to reduce complexity and compare results across different Sprints. Sprint allows for transparency, as well as inspecting and adapting other SCRUM events.

hikin combines SCRUM and Agile methodologies with the Kanban boards to maximize productivity, visualization and simplicity when managing any project, no matter how complex.

SCRUM prescribes that a Sprint should last 4 weeks or so.

Although it is quite usual that SCRUM teams choose to have Sprints of different durations according to the pursued purpose. Each case is different and the Team must discover what is the minimum period necessary to generate value through a finished increase. Starting from implementation of "Agile" throughout different organizations, actual duration of Sprints is as follows:

Sprint duration

2 Weeks

Uncommon, generally used in R & D projects or PoCs that require rapid cycling to obtain very short-term results

Sprint duration

3 Weeks

Frequent, it resembles previous one, but generally in initiatives with something more of scale.

Sprint duration

4 Weeks

Most frequent case, seems right rhythm for most of products.

Sprint duration

5 Weeks

Another case is quite common, although it is a duration outside SCRUM standards. It is common to find this scenario in organizations, demanded by Scrum teams themselves. It is very useful in projects that are in early stages, as well as in periods estimated as less productive.

Can we help you?

Do you have any questions or want to try hikin? Leave us your personal info and one of our agents will contact you to study your case.


Support and Questions

Support: Help
General: Info

Sales Team