Many teams have found that they can work more effectively in agile meetings. Productivity depends on clear and structured work. Deadlines are set for all tasks so that teams always work on time. In this workshop, agile process expert Doug Rose will explain how to make agile meetings more effective. It provides advice on key activities such as planning, organizing key meetings, scheduling sprints. You'll also learn how to avoid common mistakes and ensure consistent progress on your projects.

More productive meetings

In a constantly changing business world, organizations must adapt to increase their productivity and creativity. Meetings are a necessity and flexibility is increasingly important. You may have heard of the agile method, but what is it? It's a modern concept that has evolved in recent years, but it's not new: it originated in the early 1990s and redefined project management and teamwork. It encourages dialogue between all parties involved in a project.

What is the agile methodology?

Before we get into the details, let's look at some basic concepts. As we mentioned before, over the past two decades, agile development has become a standard in software development. Agile methods are also used in other sectors and companies. Whether you like it or not, its immense popularity is undeniable. If you haven't already, familiarize yourself with the basics.

What you need to know about the agile method is that, although it is often described or perceived as a way of working (a step-by-step process), it is in fact a framework for thinking and labor management. This framework and its guiding principles are described in the agile software development manifesto. Agile is a general term that does not imply a specific methodology. In fact, it refers to various “agile methodologies” (eg Scrum and Kanban).

In traditional software development, development teams often try to complete a product using a single solution. The problem is that it often takes several months.

Agile teams, on the other hand, work in short periods called sprints. The length of a sprint varies from team to team, but the standard length is two weeks. During this period, the team works on specific tasks, analyzes the process and tries to improve it with each new cycle. The ultimate goal is to create a product that can be iteratively improved in subsequent sprints.

Continue reading the article on the original site →