Skip to main content

The Evolution of Team Collaboration




In my point of view, if a team has a good collaboration, team members will achieve the following:
  • To be more effective
  • To make work more enjoyable
I have been working for a company for nearly four years as an software developer. Working on various projects from maintaining existing systems to developing a substantial product resulted in me moving to new teams three times. Actually, my most stable team lasted only around three years. 

Every time I've moved to a new team, I have a chance to work with new members and a new team culture again. Indeed, I realize that there is a process of developing the team collaboration which gets better time by time. I think it is an evolution!

Phase 1: Poorly collaborate

For example, that is when the team members have the following issues:
  • Only work on his/her area of expertise
  • Don't communicate to others
  • Be not confident to take on new challages
  • Don't listen to other members.

Subsequently, the team has some Failed Sprints and the knowledge gap between the members is increased.

Phase 2: Cover each other

As a result, the team would have a lesson learned! In Scrum, we have the Restropective Meeting where the team members can figure out what are the issues. 


Now, the team members have to learn how to collaborate. Each member becomes willing to support the others when being asked. Moreover, each member actively "takes care" of the others even he/she is not asked. 

For example, there are two members working on a User Story. If a member find a missing requirement or a potential bug of the other partner, he/she will proactively contact to the partner and then solve these issues together

Phase 3: Be self-organized

The team has already collaborated well is good but not enough. How about if their Scrum Master/PO is off? How about if tallented and strong members leave the team? And, so on. That is when the team should be self-organized. Each member should achieve the following attributes:
  • Be able to work as a leader.
  • Be knowledgeable, courageous and autonomous.
  • Have team goal rather than personal goal in mindset.
  • Trust each other blindly and respect is in the DNA of each team member. [1]

What I mean when I did highlight these words: trust and respect is that we should try avoid the conflicts among a lot of strong members. Am I right?

In the end

Hope you enjoyed the videos! :)

I think we should consider to include one criteria "team collaboration" when setting up the team goal in order to build up our stable dream team.

Do you have a self-organizing team? What I am thinking about is a Scrum Master can even lead more than two teams but I am not sure if it is real. 

Post YOUR opinions down below!

-------------
Reference:
[1]. https://www.scrum.org/resources/blog/evolution-development-team

Comments

Popular posts from this blog

Coders are NERDS | Learning English with Podcast

Let's learn three English vocabulary words based on real-life context through a humorous video about the life of software coders, especially at big tech companies when they work from home. Credit to Joma Tech. 🤓

The HelloWorld example of JSF 2.2 with Myfaces

I just did by myself create a very simple app "HelloWorld" of JSF 2.2 with a concrete implementation Myfaces that we can use it later on for our further JSF trying out. I attached the source code link at the end part. Just follow these steps below: 1. Create a Maven project in Eclipse (Kepler) with a simple Java web application archetype "maven-archetype-webapp". Maven should be the best choice for managing the dependencies , so far. JSF is a web framework that is the reason why I chose the mentioned archetype for my example. 2. Import dependencies for JSF implementation - Myfaces (v2.2.10) into file pom.xml . The following code that is easy to find from  http://mvnrepository.com/  with key words "myfaces". <dependency> <groupId>org.apache.myfaces.core</groupId> <artifactId>myfaces-api</artifactId> <version>2.2.10</version> </dependency> <dependency> <groupId>org.apache.myfaces.core<...

Generating PDF/A From HTML in Meteor

My live-chat app was a folk of project Rocket.Chat which was built with Meteor. The app had a feature that administrative users were able to export the conversations into PDF files. And, they wanted to archive these files for a long time. I happened to know that PDF/A documents were good for this purpose. It was really frustrated to find a solution with free libraries. Actually, it took me more than two weeks to find a possible approach. TL, DR; Using Puppeteer to generate a normal PDF and using PDFBox to load and converting the generated PDF into PDF/A compliance. What is PDF/A? Here is a definition from Wikipedia: PDF/A  is an  ISO -standardized version of the  Portable Document Format  (PDF) specialized for use in the  archiving  and long-term  preservation  of  electronic documents . PDF/A differs from PDF by prohibiting features unsuitable for long-term archiving, such as  font  linking (as opposed to  font em...

Why Functional Programming Matter

What issues do we concern when implementing and maintaining systems? One of the most concern is debugging during maintenance: "this code crashed because it observed some unexpected value." Then, it turns out that the ideas of  no side effects  and  immutability , which functional programming promotes, can help. Shared mutable data is the root cause Shared mutable data are read and updated by more than one of the methods. Share mutable data structures make it harder to track changes in different parts of your program. An immutable object is an object that can't change its state after it's instantiated so it can't be affected by the actions of a function. It would be a dream to maintain because we wouldn't have any bad surprises about some object somewhere that unexpectedly modifies a data structure. A new thinking: Declarative programming There are two ways thinking about implementing a system by writing a program. - Imperative programming: has...

Junit - Test fails on French or German string assertion

In my previous post about building a regex to check a text without special characters but allow German and French . I met a problem that the unit test works fine on my machine using Eclipse, but it was fail when running on Jenkins' build job. Here is my test: @Test public void shouldAllowFrenchAndGermanCharacters(){ String source = "ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ"; assertFalse(SpecialCharactersUtils.isExistSpecialCharater(source)); } Production code: public static boolean isExistNotAllowedCharacters(String source){ Pattern regex = Pattern.compile("^[a-zA-Z_0-9_ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ]*$"); Matcher matcher = regex.matcher(source); return !matcher.matches(); } The result likes the following: Failed tests: SpecialCharactersUtilsTest.shouldAllowFrenchAndGermanCharacters:32 null A guy from stackoverflow.com says: "This is probably due to the default encoding used for your Java source files. The ö in the string literal in the J...