1. Agile
  2. Daily Scrum
  3. Sprint Planning
  4. Kanban
Answer: 2 & 3

Daily scrum

As described in the Scrum Guide, the purpose of the Daily Scrum is to inspect progress toward the Sprint Goal, adapt the Sprint Backlog if necessary, and adjust the scheduled work. The Daily Scrum is a 15-minute event for the Developers from members of the Scrum Team. To reduce the complexity of the event, it's conducted in the same location each working day of the Sprint. If the Product Owner or Scrum Master is engaged in the work of items on their Sprint Backlog, they participate as developers.

The Developers can choose any method and structure they prefer as they ensure that their Daily Scrum focuses on progress towards reaching the Sprint Goal and produces an effective plan for the following day's work. This helps to focus the team and improve self-management.

Daily Scrums enhance communication and identify obstacles, enabling rapid decision-making and removing the need for further meetings. It is important to note that the Daily Scrum is not the only opportunity for Developers to have the ability to alter their plans. They will often have meetings throughout the day to discuss deeper discussions on adapting or revising the plan for the remainder of Sprint's tasks.

The Developers employ The Daily Scrum to inspect progress towards meeting the Sprint Goal and to inspect the progress towards completion of the work in the Sprint Backlog. This Daily Scrum optimizes the development team's probability of meeting the Sprint Goal.

When it's about a team, a question always comes up How should work be allocated to the team in a scrum project?

So, each day, the Developers must know how they intend to collaborate as a self-organizing group to complete the Sprint Goal and achieve an expected increment after it. The team members meet immediately following their Daily Scrum for detailed discussions or modifying or revising the remainder of the Sprint's activities.

Daily Scrums enhance communication and eliminate meetings that are not needed, as well as identify any obstacles to development that need to be eliminated. They also highlight and encourage rapid decision-making and increase the Development Team's expertise. This is an important inspection and modifies the meeting.

The Developers determine the format of the meeting. The meeting may be conducted in various ways if the focus is on the progress towards reaching the Sprint Goal.

Sprint Planning

Sprint planning is a process in the scrum which kicks off the Sprint. Sprint planning aims to determine the tasks that can be accomplished in the Sprint and how that work is executed. Planning for sprints is carried out by working with the entire scrum team.

When it comes to scrum, it is said that the Sprint is a predetermined duration of time when everything is completed. However, before you start your Sprint, you must organize the Sprint. It would help if you decided what the time box's duration will last, the Sprint's goal, and the location you'll begin. A sprint-planning session starts at the beginning of the run by creating the plan and setting the focus. Doing it correctly creates an environment that ensures the team is engaged and stimulated and can succeed. Poor sprint plans can sink the team's progress by creating unreasonable expectations.

Planning for sprints should be limited to by no more than 2 hours per week during the Sprint. For instance, the sprint planning meeting for a two-week sprint should not exceed four hours. This is referred to as "timeboxing", or setting the maximum time the team must finish a task, for example, organizing the Sprint. It is the Scrum Master who is accountable for making sure that the timebox is understood correctly. Suppose the entire team appears satisfied when the timebox has been completed, and the event has ended. A timebox is the time limit, and there is no limit on the time that can be used.