Once upon a time there used to be a company ABC Inc. In the ABC Inc. there used to be a Team "A". Team A and mates were a fantastic mix and match of different competencies and skill sets. They used to handle a project call ESS.
In one sprint all the user stories are completely related to C programming. None of the team mates have the competency in C , and so, being the only member with knowledege on C, Mr. Nith was asked to take the ownership. He instantly accepted the given challenge. The sprint went on well and was a sucess. All is well.
Now came the next sprint. This sprint also deals with C programming. This is mostly related to the last sprint work but in a different module kind of thing. Now, what should the team leader do? Should he again assign the task to Mr. Nith or split up the work among other members who are new to C programming so that they can improve in that area too?
It would be sensible to split up the task among other team members so that they too can develop the skill. Mr. Nith is always handy so that he can be used in case of emergency or in case of urgent deliverables.
This is missed with most of the team leaders. The reason is due to lack of knowledge and experience about how to handle a team and how to provide the scope of learning in the team. This way, the team members would be less bored(due to same type of non-challenging works) and also learn new things.
In my opinion, a Team Leader has to remember few things,
1. To cut-off the dependencies on individuals as much as possible.
2. Provide or should i say, Creating scope for learning to all the team members.
3. Sharing the proper and right information with team members at the right time.
4. Developing rapport among the team members. This can be achieved by simple shuffling of the work responsibilities.
5. Encouragement to try and explore different things in the work. This can be technologies, concepts etc.
6. And more importantly, Creating a friendly environment in the team.
7. Let them speak up their ideas and thoughts.
8. Appreciate where & when ever required.
In one sprint all the user stories are completely related to C programming. None of the team mates have the competency in C , and so, being the only member with knowledege on C, Mr. Nith was asked to take the ownership. He instantly accepted the given challenge. The sprint went on well and was a sucess. All is well.
Now came the next sprint. This sprint also deals with C programming. This is mostly related to the last sprint work but in a different module kind of thing. Now, what should the team leader do? Should he again assign the task to Mr. Nith or split up the work among other members who are new to C programming so that they can improve in that area too?
It would be sensible to split up the task among other team members so that they too can develop the skill. Mr. Nith is always handy so that he can be used in case of emergency or in case of urgent deliverables.
This is missed with most of the team leaders. The reason is due to lack of knowledge and experience about how to handle a team and how to provide the scope of learning in the team. This way, the team members would be less bored(due to same type of non-challenging works) and also learn new things.
In my opinion, a Team Leader has to remember few things,
1. To cut-off the dependencies on individuals as much as possible.
2. Provide or should i say, Creating scope for learning to all the team members.
3. Sharing the proper and right information with team members at the right time.
4. Developing rapport among the team members. This can be achieved by simple shuffling of the work responsibilities.
5. Encouragement to try and explore different things in the work. This can be technologies, concepts etc.
6. And more importantly, Creating a friendly environment in the team.
7. Let them speak up their ideas and thoughts.
8. Appreciate where & when ever required.
1 comment:
Fulfilling thank you so much for this information
php web development
Post a Comment