Developing a project with the Tuckman's model

From apppm
Revision as of 18:58, 19 February 2022 by S217122 (Talk | contribs)

Jump to: navigation, search

Contents

Why we need this model and how it works?

When it comes time to carry out a project, there are a number of elements that are essential for the proper functioning of the team or group assigned to it. In the first place, the cohesion and synchrony of the team are essential to progress effectively, in addition, good leadership of one or more members (depending on the size of the group) can become one of the key factors for the success of this project.

If you have worked on any of these projects, you will know that this is not easy, since most people come from different backgrounds, cultures, origins, ways of working... and therefore this synchrony is not always achievable. To solve this, B. Tucman designed in the 70s, a model (Tuckman Model), which more than a model can be considered a tool, since it helps to improve the productivity, synchrony and performance of teams through growth and development of the members of it. All this based on giving these people a sense of belonging to a group and some marked phases in the development of these projects.

Therefore, to achieve this through the tuckman model, we can say that this tool consists of a group of phases that a group is considered to have to face for its development and correct functioning, and that are considered necessary to be able to speak of a high-performance team.

How is distributed

Initially, the model consisted of 4 ordered parts in which a non-linear progression was obtained, that is, the effectiveness of the team does not increase as it progresses through the phases, but rather it is about obtaining a better performance as a whole at the end of the phase. these 4 and not during them. We can also consider a fifth phase that is not considered in some cases (adjourning phase), but we will talk about this later.

The name of these phases in an sorted way are forming, storming, norming and performing.

The different stages

Forming phase (Stage 1)

This is the initial stage for all projects, even those in which this model is not intended to be followed, we can see that it is still being carried out, to understand this we are going to explain what this phase consists of. In the first place, we find ourselves in an environment where the members do not know each other, there is greater uncertainty and lack of knowledge about how I can contribute to my team, what they can contribute to me, what is expected of me and what I expect of them.

This behavior leads to an individualistic attitude where it is about standing out so as not to denote insecurity or lack of confidence, or on the other hand so as not to be seen as dominant people, quite the opposite. For this phase it is important that the leader is able to detect the strengths, abilities and skills of the people in his group and thus be able to assign each of them their role, trying to guide all the members towards the same direction where all members can show their strengths, but also learn and show different points of view.

In addition, this is a good phase for the leader to declare his way of working, where he may want the group to perceive a high dominance of the leader in the project or, on the contrary, a much flatter structure where the leader only manages the work but does not is the most important member.

Once these elements are clear, it is about reaching an agreement on how you want to manage this project and its objectives, and although all these may vary, it is important and very useful to have them established and clear beforehand

Storming phase (Stage 2)

This is considered the phase where the participants show less cohesion and less performance in terms of group work. At this point problems can arise, which leads the different members to disagreement and to express the different points of view on how to deal with certain elements or problems, in the same way you can see the different dynamics proposed by the members and their strategies to solve these points based on your experiences, perceptions and opinions.

Although it is necessary to work carefully, since at this time dominance problems may appear on the part of the leader with respect to one or several members, the role of the leader must be marked and the conflicts must occur under his supervision.

These confrontations, once resolved, show the different members of the team that it is not a negative thing to express their opinion, confront each other or try to change the opinion of the rest and leads to an environment of confrontation and problem solving rather than an environment of avoidance. these, since it must be clear that conflicts are not a negative element but an opportunity to take different points of view.

What is expected at this point (already at the end of this phase, is that the members are able to talk about the problems, expose them and that it does not affect the group individually, in addition, the trust between the members will have been increased and therefore it is more difficult to disintegrate the group.

Stage three

Characteristics and strategies (norming phase)

Stage four

Characteristics and strategies (performing phase)

Stage five

Characteristics and strategies (adjourning phase) And why this phase was unexistent at first?

Benefits of using this model

Real proofs and assumptions of why the model should work In this part, through documented real experiences, we will try to analyze why this model should or should not be used and in which cases it is more beneficial.

Current problems with the tuckman model

Why is it currently not considered such a good model? Numerous articles are recently written referring to the fact that this model is wrong and lacks effectiveness.

Challenges using this model

Problems you will probably face if you use this model Problems faced by groups using this model and how to overcome these

How to appply Tuckman's model as a group

Tricks and experiences of how the tuckman model has been used in projects and/or programs

Bibliography

References

Developing a project with the Tuckman'S model Raül Ciscar

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox