Free The Weekly Team Meeting Case Study Example

Being the manager of several IT project, leaded according to Scrum methodology, it cannot help paying attention to the so-called important component as meeting. The methodology involves high formalized structural approach to software development (cascade model). Agile focuses mainly on the iterative development with the minimum allowable formalization process.
SCRUM - one of the flexible software development methodologies. An important part of this methodology is SCRUM-meeting, which should oversee the competent person - SCRUM-Master (often project manager or team lead).
Exactly SCRUM foresees the real importance of meeting for the general success of project. Fortunately, I hold the position of SCRUM-Master in two application development projects because I am competent in this sphere. Meeting plays the vital role in project management. Scrum requires two types of meeting. Daily meeting control the fulfillment of tasks. And we hold one at 3 pm every second Wednesday to solve the accumulated issues. Definitely, the last ones are important for the further interaction of team.
The team happened to be waiting for half of team members. This case breaches the discipline and the management in general. Surely, I cannot help tolerating this because this is my personal obligation to manage. In most cases, the delay is caused by the mismanagement of his time planning or careless attitude to project, subsequently, to the members of team. Thus, the team manager should focuses on these two keys.
The problem of irregular time planning relates to the poor knowledge of time management. As everybody agreed to attend the training onсe a week, we undoubtedly implicated this approach. Therefore, employees could become the managers of own time.
As for team leaders’ attitude, this issue requires different solutions. The best decision turned out to reward the people who wait for and to punish the guilty ones. Following this purpose, one manager has brought a piggy-bank. The rules were very simple. People pay the conventional amount and bring cookies for the team if they come not on time. This approach came into force very quickly. Every month we could spend the money for personal needs. Surely, the employees became more punctual at once.
SCRUM meeting focuses on the results of two weeks. Thus, everybody has to present the fulfillment of taken tasks. As it turned out, team members don’t feel the responsibility for some duties and the project cannot be analyzed because of some keys located in the “in progress” gap. Having sampled different approaches, I inclined to the demonstration. The fulfillment of tasks of each employee should be represented by percentage from the whole mass of planned work. Thus, it visually demonstrates the efficiency. Team members have no desire to become the main key for speculations as the main cause of project slowdown. This methodology is successfully implemented in many IT project that follow SCRUM.

The mentioned before issues may increase the project duration and affect the quality of fulfillment.

Surely, this is far from all approaches that improve the basic performance of management. They help not only avoid barriers in project, but build team that works as a solidary mechanism.