Skip to main content

Few things - As technical lead, we should take care.

The below are only the points.
Read the original article in [www.littletutorials.com].
Really awesome.
In fact, the author of this article inspired me to restart my knowledge sharing activity and started writing few thing in the web.

Sec-1:Set yourself up for success
  1. Define early on what success means for you, the team and the business
  2. Believe in the project: idea, architecture, time, team
  3. Understand the domain, the business requirements and the technical challenges
  4. Know your team: strengths, weaknesses, ambitions and personalities
  5. Have a plan as a result of a planning activity
  6. Be part in the design of everything
  7. Get your hands dirty and code8. Act as a communication proxy for your team
  8. Make sure everybody understands the big picture: their work has implications
  9. Fight for architecture and design consistency
  10. Know the status of everybody’s work and detect slippage
  11. Record technical debt if you need shortcuts but try to maintain architectural integrity; report the debt
  12. Use the process that makes sense in your particular case
  13. Avoid dogmas - question why everything is done the way is done; make sure everybody else knows the reasons
  14. Avoid design by committee; listen to everybody but make your own decisions
Sec-2:Build your relationship with the team

  1. Gain the team’s respect with the quality of your work and by doing what you are preaching
  2. Be fair
  3. Admit your mistakes
  4. Publicly recognize both team’s and individual members’ merits
  5. Don’t blame anybody publicly for anything
  6. Build morale and confidence by offering early victories to the team and to its individual members
  7. Match people and tasks based on skills and their personal preference if possible; explain your decisions
  8. Work the estimates with the team don’t come up with them
  9. Mentor people
  10. Listen to and learn from people
  11. Explain your technical decisions
Sec-3:Build your relationship with the management and business people

  1. Be sure you have authority along with responsibility
  2. Be sure you get requirements and not architecture/design masked as requirements
  3. Explain technical decisions in business terms
  4. Try to be accurate in your estimates; avoid being too optimistic and don’t push it with hidden padding; explain the need for padding
  5. Set reasonable expectations
  6. Understand the relationships and dependencies with other teams or projects
  7. Accurately report the status with alarms, explanations and solutions; report any technical debt
  8. Resist pressure for change in requirements, and more important for shortcuts
  9. Be aware of politics
  10. React to surprises with calm and with documented answers

Thanks!

Comments

Post a Comment

Popular posts from this blog

Top Skills Professionals Need to Master

What do professionals really need to know? All working individuals and professionals need significant competency and skill in all of the following eight areas in order to be successful, and most are sorely lacking in several if not most of them. Research shows that most are lacking in at least three of these skills at the same time. 1. Communication Skill In order to be successful in your job and career, you must communicate powerfully and effectively with confidence and clarity. There's been  much written about introverts as leaders and managers, and how they can use their innate skills and gifts to succeed as leaders. Your  personality type and level of introversion/extroversion aside, if you can't communicate your ideas in an empowered, clear and engaging way, you  simply won't perform or progress as well as your counterparts who can communicate with ease and strength. 2. Building Relationships So many professionals don't get this one basic point until it...
Post a Comment
Read more

25 Things Every Young Professional Should Know By 25

If you want a job straight out of college, don’t knock on Kirk McDonald’s door.  McDonald, the president of a tech company in New York City, wrote a brutally honest op-ed in The Wall Street Journal called “Sorry, College Grads, I Probably Won’t Hire You.” He believes most college graduates don’t have the one skill that’s in high demand: computer programming.During your first few years in the real world, what else should you take time to learn? Here are 25 things every professional should know by age 25: 25. “Definitely” is not spelled “definately.”  Spell-check always. 24. You should read an entire apartment lease before you sign it.  23. An Excel PivotTable will change your life. Nothing is lesser. 22. A cover letter should add color and personality to your resume—not summarize it.  21. Everyone likes to receive praise, but the smartest young adults actively seek constructive criticism .  20. The days of a college syllabus are long gone . If you’re wait...
Post a Comment
Read more

Most Common Interview Questions...

Prepare for the below questions generally asked in the job interviews. Tell me a little about yourself Why are you looking (or why did you leave you last job)? Tell me what you know about this company. Why do you want to work at X Company? What relevant experience do you have? If your previous co-workers were here, what would they say about you? Have you done anything to further your experience? Where else have you applied? How are you when you're working under pressure? What motivates you to do a good job? What's your greatest strength? What's your biggest weakness? Let's talk about salary. What are you looking for? Are you good at working in a team? Tell me a suggestion you have made that was implemented. Has anything ever irritated you about people you've worked with? Is there anyone you just could not work with? Tell me about any issues you've had with a previous boss. Would you rather work for money or job satisfaction? Would you rath...
Post a Comment
Read more