Meeting, or "ritual" is an important part of agile development. As one of the important elements that the meeting should not exist independently from the other elements. (A lot of people tend to add a waterfall in a similar ceremony in the project, then called "agile", this approach is simply nonsense.)
Now, let's look at these ceremonies agile, how they achieve team empowerment and promote agile development.
Note: Some of these rituals from the Scrum. Scrum is a need for a limited time, in an iterative manner to achieve agile methods. The concept behind these rituals can also be applied to other forms of agility, such as kanban or lean. Scrum Sprint is only a term, and the use of other forms of agile more general term "iterative" development represented in a limited time frame for.
Sprint planning
Participants: team, Scrum Master, Product Owner
held Time: Sprint start
duration: time limit of one week iterations, the duration of the meeting is usually an hour - for example, a two-week Sprint will be at the start for two hours planning meetings.
Agile Framework: Scrum (of course, Kanban team also planned, but they did not use a formal Sprint planning meetings to develop Iteration Plan)
Objective: Sprint planning meetings to plan for the entire team to ensure the success of the team throughout the Sprint. Before the meeting, Product Owner will arrange to prepare a prioritized Product Backlog. They with the development team to discuss each list, and estimated workload. Then, the development team will be Sprint forecast estimated the team about what work can be done in the Product Backlog, which is part of the work is the Sprint Backlog.
Expert Tip: specifics team through Sprint planning meetings to enrich the work needs to be done. Encourage team members for all user stories in the Sprint, errors, and tasks outlined tasks. The purpose of the conference is to promote discussion and consensus on action plans. Effective planning can increase the probability of Sprint team to achieve goals.
Daily station will
Participants: team, Scrum Master, Product Owner
held in time: once a day, usually in the morning.
Duration: not more than 15 minutes. Do not let us sit in the conference room. Standing meetings can shorten its duration.
Agile framework: Scrum and Kanban.
Purpose: The purpose of that station will allow the team members to quickly understand the current progress. This is not a detailed status report on the meeting. The overall atmosphere of the meeting should be fun, but informative. Meeting team members should answer the following questions:
• What is accomplished yesterday?
• What to do today?
• What obstacles encountered?
Own progress report to the team yesterday companion is a very subtle way of accountability. Nobody wants to be the team that people laggard - repeating the same thing every day, and no progress.
Expert Tip: Some teams use a timer to ensure that each person who spoke concise, words, and there was. Some teams may choose to let the players while meeting while passing each other, in order to ensure the team's focus. The existence of many geographical disparities teams will choose to use video conferencing or chat group of stations will be done daily. Each team has its own unique character, so daily station will also be different!
Iteration will be assessed
Participants:
must attend: the development team, Scrum Master, Product Owner
is recommended to attend: project stakeholders
held in time: the end of the sprint or milestones
duration: 30-60 minutes.
Agile framework: Scrum and kanban. And planning meetings, like, kanban team should be consistent with the assessment team milestones, rather than a fixed rhythm held.
Objective: To review the iteration is to demonstrate the achievements of the team time. They can use "Friday demo demonstration (demo Fridays)" and so relatively easy to form, it can be more formal meeting format. No matter what form, the assessment team will all celebrate the achievements of the work, the presentation of the completed work in the iteration, and given the opportunity to feedback from project stakeholders there. Remember, only demonstrate compliance with the requirements and meet the quality standards of the team's achievements before they can be considered complete before they can be displayed in the review meeting.
Iteration retrospective
Participants: team, Scrum Master, Product Owner
held in time: At the end of the iteration
duration: 60 minutes
agile framework: Scrum and Kanban. Scrum team meets regularly review meeting. Kanban team may also benefit from the occasional review meeting held in.
Objective: Agility is the core from which rapid feedback to optimize product development and culture. Recalling the meeting can help the team understand what is done well, and what needs improvement.
Recalling the meeting not only complain about the gun nozzle is no workaround meeting. Which team can use the review conference is an effective way to find out, the team can continue to focus and use. And what improvements need to be made, and discuss the creative solutions at the conference and to develop an action plan. Continuous improvement is to support and promote the development of power agile teams, and review meetings are key actions to achieve continuous improvement.
Expert Tip: Even if the entire team is progressing smoothly, and do not stop the review meeting. Because the review meeting will provide ongoing guidance to the team, in order to maintain good running condition.
A team of agile development practices rooted in the need for real, change method relies on tactical and strategic team and excellent writing. Agility ceremony but the whole team played a role in simplifying the communication process.
Source: Worktile agile blog
Welcome to exchange more questions about technology and collaboration.
Article please indicate the source.