Wednesday, September 21, 2016

How to be a successful Project Lead in software development world?

Q: What are all the critical Roles and Responsibilities of Team Leader?

1) Crystal Clear Understanding of requirements
This is prime important thing as team evaluates leader based on how much clearly he/she captured the requirements. Also, some bad team members used to cross-verify the requirements to make leader to degrade. So, never allow this loop hole and make sure you got the crystal clear requirements from customer and your understanding is the authenticated one. You may need to put extra miles to get this level of clarity - talking to various stake holders, team members, coming with flow/process diagram, acceptance criteria, test cases...etc

2) Having FIRM VISION from requirements
Only visionary lead could have perfect mind to complete the project. The lead should become the top most visionary person in team. The vision makes the lead think what, how and when things needs to be accomplished to achieve the vision.

3) Converting requirements into WBS/Activities
Vision is passive but mission is active. The real success of team lies in converting the requirements into activities. So, the lead should spend good amount of time to convert the reqs to WBS/activities.

4) Assigning and Managing team to get them done
Assigning the reqs to appropriate person with timeline is the next important step. Tracking and motivating team to accomplish the task is highly challenging.

5) Review the team's work and give continuous feedback
Once team says the task been complete then throughly review either it is code/design/doc...etc
Remember, once you reviewed it then only it has to pass to customer. Your AUTHORIZATION is most important before release of product.

6) Design and Architect the project
The team really value you when you participate in development activities like design/architecture and coding. Though it doesn't seems true, most of the team members expectation is the lead should be well versed in the activities they do. They are highly impressed if the lead also put his hand on coding/designing and making them improve. It is human tendency to think that our leader should have been the BEST DEVELOPER and should have crossed similar steps as me sometime before.

But careful about bad team members loop hole here and every where.

Team member becomes really bad when
1) Their suggestions are not accepted.
2) They think they are better than lead in-terms of knowledge in domain, coding, design...etc
3) They are insulted in front of team
4) Their work is given many feedbacks /comments
So, make sure you don't fall prey on these areas. If happend so then come out strategically else one may loose the team and its spirit. 

No comments:

Post a Comment