Our Methodology

In this stage, we had open discussions to get to know each other better before commencing project work. We were able to build trust, and strengthen our intra-team relationships. In doing this, we were able to analyse our individual strengths, and consider any limitations that may arise throughout the project lifecycle, enabling us to allocate tasks effectively. 

The storming stage is important in any team with diverse backgrounds. During this stage, we encouraged all team members to brainstorm ideas and establish their position in the team. All thoughts and ideas were welcomed, and we developed procedures to help us determine future outcomes. 

As everyone came from different academic backgrounds and have different approaches to similar scenarios, conflicts are expected at each stage. Nevertheless, we developed operating procedures to get the best out of every team member. Additionally, we transformed our disagreements into constructive discussions, to foster a growth of stronger ideas and positive outcomes. In this phase of group development, guidance from a team leader plays a crucial role in resolving issues and functioning effectively. 

At this stage, team roles were effectively finalised, and tasks were allocated based on individual strengths. The team leader assigned ‘sprint’ tasks (designed according to our agile methodology) to each group member, and this gave us all the opportunity to connect with each other on an interpersonal level. Consequentially, members were motivated and focused on the team goals and established strategies to achieve the company’s mission (in line with our core values). Furthermore, our team leader made sure that there were no disagreements and even if those disagreements re-emerged, our team revisited elements from the forming and storming stages.

The Performing stage reflects where our team currently sits, as we are operating at peak efficiency and making the most of our full potential. Performance is managed from a distance, with the team reminded of deadlines and progress being logged iteratively according to our agile development standards. During project completion, our team communicates to ensure individual workloads remain achievable. 

Any conflict at this stage is handled in a similar way to during the storming process – our team discusses alternatives that could integrate both ideas. The team member responsible for the ‘sprint’ task may open discussion to the entire team, to gain extra insight. 

All team members are provided the opportunity to comment or reflect on work completed by themselves or others, at every stage of the project. Following our agile methodology, work is completed iteratively as the team progresses towards building the project’s final outcomes. 

Once all work is compiled (by the team leader or team members given this responsibility), the team meets and evaluates the project against the client’s expectations (which we have established using our team’s collective communication strengths). This helps us ensure no corners have been cut and guarantees we are giving the best possible outcomes to our clients.