Search

When Can You Expect Your Newly Formed Team To Perform?

I can visualize the curious facial expression of the readers out there especially if the reader is a Team lead or Manager or Delivery Head. Jokes apart! It’s a quite common scenario whenever a new chunk of work comes to an IT-Farm. A team is formed which starts focusing towards project execution. Once a team is having visibility of the requirement, a ballpark estimate is given to the client. Looks like the team is all set to perform right from outside? Hence the leadership team (inclusive of the Team lead, managers, delivery head etc.) start expecting output. Thus, unknowingly an unhealthy pressure gets built up on the team. Hold on for a second. Aren’t we expecting that with an introvert mindset? Let’s have a look at the ground reality and consider the below model. A team when formed passes through certain stages. We can consider it as a “Tree life cycle”. Whenever we plant a seed it requires extra care and nourishment. After some days of watering and care sprouts starts coming out followed by which, with time, it becomes strong enough and gets converted to a tree.Similarly, a new team when developed passes through the below 5 important stages- 1. Forming2. Storming3. Norming4. Performing5. Adjourning Let’s talk about different stages of team productivity in details:1st Stage: Forming A team enters the forming stage when it is newly formed. Members of the team meet each other for the first time. There is a minimal visibility around the roles and responsibilities of an individual within the team. Hence members are in an “observing mode”, they observe other members of the team to get the feel around the person and how they can contribute together towards the project goal. Team members tend to behave independently since they do not know each other well enough to unconditionally trust one another. Team leader plays a crucial role in this phase. They should define Project goal and should ensure an individual is having clear visibility around his/her roles and responsibilities. 2nd Stage: StormingPost forming stage, a team enters the storming stage where there are high differences among the members due to less acceptance among the individuals. Members think more from an introvert mindset and from an individual perspective. Productivity from the team member is least, members collide more with each other. In this stage, the team leader should first continuously keep track of the work and resolve conflicts. Exhaustive presence and input are required from the leader to ensure that the team is running on the constructive track. 3rd Stage: NormingPost Storming phase, the team enters the norming phase wherein there is a high acceptance around the decision and differences between the member of the team. The team becomes more mature and there is a high collaboration among the members of the team. They work more as a team rather than an individual contributor. There is a shift from an introvert to extrovert mindset among individuals. The team members start building trust towards other members and actively seek each other out for assistance and input. We can call this phase Pre-Performing phase. The productivity of the team is high compared to the previous two stages. The team leader may not be involved in decision making and problem-solving anymore, as the team is working better together and are holding themselves accountable for the delivery. However, on a need basis, the team leader can pitch in and provide direction to the team. 4th Stage: PerformingOnce a team exits the norming stage, it enters the performing stage. Here the focus is more towards achieving the project goal as a group. Here throughput from team members is at its peak. There is a high trust factor, collaboration, and proactiveness among the members of the team. Hence the team takes quick decisions and solves their problems quickly. Thus, there is a timely delivery from the team. In this stage, a team leader is not involved in decision making and problem-solving. From the performing stage, it is possible to revert to the Storming stage if a member starts working individually and is not a good team player. Hence the team leader keeps a watch to ensure that this stage doesn’t change back to storming stage. 5th Stage: AdjourningA team enters this stage when the assignment gets completed and the team can be dissolved. The entire team celebrates the success with the help of different activities ( For eg: Team party ). The team leader plays a crucial role in this phase. The leader should ensure that the members are appreciated for their valuable contribution. Here is how the performance of the team would look like-The above model is known as “Tuckman Model of team formation”.Bringing it all together“A general thought on how often being a Team leader we think of it and accordingly expect productivity from the team?” Let’s re-analyze the current stage of our newly formed team and help them achieve the “Performing” stage by working constructively along with the members, rather than creating an unhealthy pressure of delivering irrespective of the current stage of the team. Please share your thoughts in the comment section, we can connect on LinkedIn and talk more. If you enjoyed this post, spread it to your connections on LinkedIn or other channels. Thank you!
Rated 4.0/5 based on 2 customer reviews

When Can You Expect Your Newly Formed Team To Perform?

139
When Can You Expect Your Newly Formed Team To Perform?

I can visualize the curious facial expression of the readers out there especially if the reader is a Team lead or Manager or Delivery Head.
 
Jokes apart!
 
It’s a quite common scenario whenever a new chunk of work comes to an IT-Farm. A team is formed which starts focusing towards project execution. Once a team is having visibility of the requirement, a ballpark estimate is given to the client.
 
Looks like the team is all set to perform right from outside? Hence the leadership team (inclusive of the Team lead, managers, delivery head etc.) start expecting output. Thus, unknowingly an unhealthy pressure gets built up on the team.
 
Hold on for a second. Aren’t we expecting that with an introvert mindset?
 
Let’s have a look at the ground reality and consider the below model.
 
A team when formed passes through certain stages. We can consider it as a “Tree life cycle”. Whenever we plant a seed it requires extra care and nourishment. After some days of watering and care sprouts starts coming out followed by which, with time, it becomes strong enough and gets converted to a tree.

Similarly, a new team when developed passes through the below 5 important stages-
 
1. Forming
2. Storming
3. Norming
4. Performing
5. Adjourning
 
Let’s talk about different stages of team productivity in details:
1st Stage: Forming

A team enters the forming stage when it is newly formed. Members of the team meet each other for the first time. There is a minimal visibility around the roles and responsibilities of an individual within the team. Hence members are in an “observing mode”, they observe other members of the team to get the feel around the person and how they can contribute together towards the project goal. Team members tend to behave independently since they do not know each other well enough to unconditionally trust one another. Team leader plays a crucial role in this phase. They should define Project goal and should ensure an individual is having clear visibility around his/her roles and responsibilities.
 
2nd Stage: Storming

Post forming stage, a team enters the storming stage where there are high differences among the members due to less acceptance among the individuals. Members think more from an introvert mindset and from an individual perspective. Productivity from the team member is least, members collide more with each other. In this stage, the team leader should first continuously keep track of the work and resolve conflicts. Exhaustive presence and input are required from the leader to ensure that the team is running on the constructive track.
 
3rd Stage: Norming

Post Storming phase, the team enters the norming phase wherein there is a high acceptance around the decision and differences between the member of the team. The team becomes more mature and there is a high collaboration among the members of the team. They work more as a team rather than an individual contributor. There is a shift from an introvert to extrovert mindset among individuals. The team members start building trust towards other members and actively seek each other out for assistance and input.
 
We can call this phase Pre-Performing phase. The productivity of the team is high compared to the previous two stages. The team leader may not be involved in decision making and problem-solving anymore, as the team is working better together and are holding themselves accountable for the delivery. However, on a need basis, the team leader can pitch in and provide direction to the team.
 
4th Stage: Performing

Once a team exits the norming stage, it enters the performing stage. Here the focus is more towards achieving the project goal as a group. Here throughput from team members is at its peak. There is a high trust factor, collaboration, and proactiveness among the members of the team. Hence the team takes quick decisions and solves their problems quickly. Thus, there is a timely delivery from the team. In this stage, a team leader is not involved in decision making and problem-solving.
 
From the performing stage, it is possible to revert to the Storming stage if a member starts working individually and is not a good team player. Hence the team leader keeps a watch to ensure that this stage doesn’t change back to storming stage.
 
5th Stage: Adjourning

A team enters this stage when the assignment gets completed and the team can be dissolved. The entire team celebrates the success with the help of different activities ( For eg: Team party ). The team leader plays a crucial role in this phase. The leader should ensure that the members are appreciated for their valuable contribution.
 
Here is how the performance of the team would look like-
The above model is known as “Tuckman Model of team formation”.

Bringing it all together

“A general thought on how often being a Team leader we think of it and accordingly expect productivity from the team?”
 
Let’s re-analyze the current stage of our newly formed team and help them achieve the “Performing” stage by working constructively along with the members, rather than creating an unhealthy pressure of delivering irrespective of the current stage of the team.
 
Please share your thoughts in the comment section, we can connect on LinkedIn and talk more. If you enjoyed this post, spread it to your connections on LinkedIn or other channels.
 
Thank you!

Suraj

Suraj Sharma

Blog Author

Suraj Sharma is working as a Full Stack QA Engineer with leading IT farm and is striving for bringing change in Industry. Strong believer of "Learning or Decaying" mantra. Technology explorer, Blogger and part-time cyclist by passion. Connect with him on LinkedIn.

Leave a Reply

Your email address will not be published. Required fields are marked *

Suggested Blogs

Scrum Master and Product Owner: Understanding the differences

 Agile methodology imparts the easy and convenient path to work. Scrum is one of the famous Agile methodologies. Agile methodologies consists of 4 main roles, viz. Product Owner, Scrum Master, Scrum team and Stakeholder. Each role has its share of responsibilities. These roles are all about commitment. Scrum master and the Product owner are two vital roles in the Scrum Software Development Methodology. Since they both are working on different areas of the project, they are indispensable for the project. Scrum Master is a mediator between the Product owner and the Development Team.       Product Owner vs Scrum Master- Though the Product Owner and the Scrum master vary in their roles, they complement each other. Scrum master should support the product Owner in every step possible. There should be an amicable relationship between the Product owner and the Scrum master. Disputes may happen between them if the roles are not clarified. Let us have a look at the differences in roles between the product owner and the scrum master. The Scrum Master concentrates on the project success, by assisting the product owner and the team in using the right process for creating a successful target and establishing the Agile principles.    Scrum Master Skills (SM): SM creates a friendly environment for the team for Agile development. SM improves the quality of the product. Certified Scrum Master Certification, adds advantage to become effective. SM protects his team from any kind of distraction and allows them to stay tuned. SM helps product owner to maximize ROI (return on investment) to meet the objectives. SM removes disputes between the product owner and the development team. SM encourages the team to meet the project deadline. SM acts like a coach for a team to perform better. A good Scrum Master should possess the skills like project management, engineering, designing, testing background and disciplines. SM provides continuous guidance to teams   Duties of Scrum Master: SM facilitates team for better vision and always tries to improve the efficiency of the teams. SM manages Scrum processes in Agile methodology. SM removes impediments for the Scrum team. SM arranges daily quick stand-up meetings to ensure proper use of processes. SM helps product owner to prepare good product backlog and sets it for the next sprint. Conducting retrospective meetings. SM organizes and facilitates the sprint planning meeting. The Product Owner’s responsibility is to focus on the product success, to build a product which works better for the users and the customers and to create a product which meets business requirements. The product owner can interact with the users and customers, stakeholders, the development team and the scrum master.   Product Owner Skills (PO): PO should have an idea about the business value of the product and the customers’ demands. Certified Scrum Product Owner Certification (CSPO) will be beneficial for the sales team. The development team consults PO, so he should always be available for them to implement the features correctly. PO should understand the program from the end-user point of view. Marketing is discussed on the sales level in most of the Organizations. So it is the PO’s duty to guide the marketing persons to achieve the goals successfully. PO is responsible for the product and the ways to flourish a business. PO has to focus for the proper production and ROI as well. PO should be able to solve the problems, completing trade-off analysis and making decisions about business deliverables. After CSPO course, PO can work with the project managers and the technical leads to prioritize the scope for product development. Sometimes PO and the Customers are same, sometimes Customers are thousands or millions of people.   Duties of the Product Owner: PO has to attend the daily sprint planning meetings. PO prioritizes the product features, so the development team can clearly understand them. PO decides the deadlines for the project. PO determines the release date and contents. PO manages and creates the product backlog for implementation, which is nothing but the prioritized backlog of user stories. PO defines user stories to the development team. Spending some time to prioritize the user stories with few team members. One can enhance his/her knowledge in many directions and beyond boundaries, after undergoing the Certified Scrum Product Owner (CSPO) training.
Rated 4.0/5 based on 1 customer reviews
Scrum Master and Product Owner: Understanding the ...

 Agile methodology imparts the easy and convenien... Read More

Does Scrum Apply To All Types Of Projects?

Scrum, undoubtedly, is one of the potentially viable approaches to managing software development projects. Scrum is just a development methodology which delineates the processes and practices that help in managing software development activities.However, before adopting any methodology one should ask these questions -Is the use of Scrum being forced upon you to fit into the project?Has the research been done to predict its success rate?Have you analyzed the risks associated with this adoption?What types of projects fall into the purview of Scrum framework?I worked in the IT industry for 9+ years on a wide variety of projects where the success rate of Scrum was very high. Hence, I got the impression that it works for all types of projects. Here is my experience with one of the projects that threw away all my misconceptions about Scrum and changed my opinion.My team worked on a huge, multi-dimensional project, that included distributed teams.Multiple versions of the product were already out in the market and customer satisfaction was running high. Then we decided to switch to Scrum for this particular project. As the software product was already out in the market, customer issues and complaints piled up that were assigned a priority level in order to be resolved.The team working on the newer version was also required to support the older versions as a part of the contract with the customer.  Therefore, the same team is working on new versions of the product including enhancements and new features while also addressing the customer issues and bug fixes for the older version of the software.Now, since the product owner had already groomed the backlog for the software release, whenever any new issue from the earlier versions was raised by the customer, we took them on priority. This leads to these issues being constantly added in the midst of the sprint to the backlog and the whole team started working on the issue, leaving their current work behind.As a result of these mid-Sprint changes-All of a sudden, team had to shift their focus.No planning was done for this issue while grooming.Unplanned work being added to the backlogDelay in creating and delivering current project deliverables.Then comes the conundrum -Are we really using Scrum the right way? Is our project really getting any benefit by using Scrum?The answer is probably NOT. But the management still wouldn’t agree and will continue to force the use of Scrum for this project.Now, let us discuss the below scenarios.1) Sometimes there were too many issues from the earlier versions but the other times too few issues (but of high priority) were thereIn these cases, we need to immediately switch our focus to a high-priority issue and provide a possible solution to the customer as early as possible. The current sprint needs to be cancelled and pending tasks need to be transferred to the next sprint.2) Sometimes no issues at all.Continue the sprint.3) Sometimes issues need to be addressed but the current project is also in a critical stage.An example is the build failure of the current project and where testers weren’t able to continue the testing. This becomes a critical condition for any project which needs to be addressed and planned for.Because of this critical situation, management switched its stance and agreed to abandon Scrum for this project as it stalled both the projects and instead used the waterfall model.Few suggestions to avoid this scenario -Make two separate teams - one for handling the issues of earlier versions and one for the current project sprintsSlowly and steadily we should stop giving the support to the earlier versions (End of life) and this should be clearly communicated to the customer in advance so that they can also prepare themselves. It should be coded in the contract at the time of signing. However, this is not always possible due to complex nature of projects that run big manufacturing and production plants which may adversely affect their productivity/throughput.The above two solutions can be addressed in the following ways:Plan and allocate budget to provide support to the earlier versions of the product instead of hiring the new team. In case of no issues, the team can continue to work on the current project.For such projects, Scrum and Kanban both methodologies should be used.Conclusion:In my opinion, before adopting any methodology we should always deep dive into it and understand its success rate in different scenarios of the project. We should not impose any methodology on any project by giving justification that it is already used by other projects.Also, start off with small (maybe internal) projects having few sprints and few team members just to predict the success rate of the methodologies and frameworks.“It’s better to fail first than at the end”.So, for the projects where there is high unpredictability (don’t know when new tasks will come), chances are there that Scrum may not work; so it is better to use Kanban in those situations.Inappropriate application of Scrum can lead to its doom – Scrum is not a prescriptive method, but a suggestive approach to software development. So, the way it is implemented makes all the difference.
Rated 4.5/5 based on 0 customer reviews
Does Scrum Apply To All Types Of Projects?

Scrum, undoubtedly, is one of the potentially viab... Read More

5 Hurdles that Scrum Masters Commonly Face

Agile has gained a significant track and has been adopted by all organizations. Agile Methodology today has become one of the most popular and most dynamic project management styles among the software development teams. And Agile is also being adopted by various other functions. It is important to note that Agile can be applied to many types of teams and projects and should not be thought of as limited to engineers or software development projects only.We run all our software delivery through an Agile methodology called Scrum. Scrum is well-recognized amongst engineering teams, but a variety of teams across industries have come to love the Scrum way. From manufacturing to operations and education, businesses of all kinds have used Scrum practices and successfully. As long as your projects involve a concrete product, Scrum can work for you. We have been using Scrum for last few years and have some great success with it. But, still the Team come across various common Scrum Pitfalls.Many organizations are adopting Agile and Scrum for producing higher quality products and services.As per the statistics are given by PwC, “Agile projects are 28% more successful than traditional projects.”Almost three-quarters (71%) of organizations report using Agile approaches sometimes, often, or always. (source: capterra)So why not,Organizations are hiring Scrum Masters for implementing Scrum Framework. It’s a sole responsibility of a Scrum Master to make sure it’s fully implemented and followed by the team in an organization.Scrum is easy to understand but hard to implementWho is a Scrum Master?The Scrum Master is a champion for a Scrum team. He coaches the team, the product owner, and the business. The Scrum Master is a multitasker were deeply understands the work being done by the team, motivates the team and makes sure that the teams are following the Scrum processes and will also work together with them to continuously improve them.How important is a Scrum Master?Scrum Master also ranks on the top of the hierarchy on most of the Agile or Scrum Process, with an eye towards a better understanding of role and importance, here is a closer look at the Scrum Master roles. 1. Scrum Master plays a vital role in the success of the project, he serves as a glue that can hold the entire project.2. Scrum Master may not participate in daily Scrum meetings but supports the entire team.3.  Scrum Master helps in strengthening the Agile development team4.  Scrum Master facilitates team meetings, which also includes Daily Stand-up5.  Scrum Master aims to deliver the maximum value to the customer.Let’s have a look at the 5 hurdles that Scrum Master commonly face:1. Managing Role ExpectationsMany organizations, as well as the upper management, confuses the role of the Scrum Master with a Project Manager. However, the most important thing that we all should know is that the Scrum Master is a Scrum facilitator for a team as well as an organization.However, sometimes management expectations are different, which makes the life of a Scrum Master little harder. We all need to understand that Scrum Master is a facilitator, a guide, a process follower and most importantly, a Servant Leader.2. Change ResistanceAs per Mike Cohn, it is the social aspect of change that can create resistance, all resistance comes from specific individuals. Teams or departments do not resist changing to Scrum, Individuals do.So, when we talk about Scrum implementations, the Scrum Master is the change agent for the same. It’s a major hurdle faced by a Scrum Master during the implementation. Change Resistance is not a surprise, it’s the most expected reaction whenever a new change is introduced.                                                      Tip: Choose a length of the Sprints in such a way that it can resist change.There are many ways for adopting Scrum patterns and overcoming change resistance. You will get that Scrum adopting patterns in my previous article- Patterns For Adopting & Spreading Scrum In Organizations.3. Keeping everything Time-Boxed        When we talk about implementing Sprints, every event is supposed to be time-boxed in order to get productive results. For example, the Daily Scrum event should not exceed 15 minutes, but in reality, we see team members start discussing their technical difficulties and the meeting goes longer than the allotted time. It’s one of the most common challenges for any Scrum Master.Well, a funny thing to try to overcome this hurdle is to make the team members stand for 15 minutes. Hide all the chairs! They will eventually get tired and finish up the meeting.4. Handling Urgent Change RequestsScrum Masters follow the rule when implementing Scrum which is to never accept changes within the Sprint. We can handle the change requests at the end of the sprint or at the start of the Sprint but not in between. However, in a practical world, we see Product Owners/Customers/Stakeholders coming up with an urgent change requests or bugs.However, it’s also not good to blindly follow the process without understanding the business and market aspects. It’s always better to communicate, collaborate with all the Stakeholders, replan and then make good decisions.5. Distributed TeamsIt is one of the most common barriers faced by a Scrum Master. When the teams are distributed geographically, there are sometimes delays, network issues, cultural or regional issues, different Time Zones, different working hours, it is always difficult to get everyone connected and collaborate/communicate with everyone.Thanks to all the technologies, applications out there that help us overcome this hurdle whether it’s communication, video conferencing, there are many tools available.Scrum Master also come across the following challenges:1. Scrum Master acts as an admin:Basically, Scrum Master tasks start with booking meetings, scheduling events, taking notes, and inviting people to ceremonies. All these may be the primary function of the Scrum Master and these deals with making the team be effective. The tasks involve various challenges.2. Lack of Agile training for the teams:As the Scrum Master is meant for the team, it’s a responsibility to make sure all your team members have foundational Agile training. This is one of the most problem faced by Scrum Master.To summarize, I would say, these are the just the “Hurdles” commonly faced by Scrum Masters but not the “Blockages”. These obstacles can be jumped over, with good skills, expertise and, experience in Scrum implementations. Keep Learning!
Rated 4.0/5 based on 2 customer reviews
5 Hurdles that Scrum Masters Commonly Face

Agile has gained a significant track and has been ... Read More