The document provides an agenda and information for a knowledge sharing session for new team and technical leaders. The summary includes: 1) The session covers understanding roles and expectations, common project roles, characteristics of team/technical leaders including hard skills, and what is needed to do the job well. 2) Key characteristics of team/technical leaders include honesty, confidence, ability to inspire, strong communication, decision-making capabilities, delegation and empowerment skills, and empathy. 3) To be effective in the role, leaders need knowledge of required job skills, accountability, responsibility for keeping skills updated, demonstrating high quality work, and managing expectations through clear communication.

1. First time being a
Team/Technical
LeaderSummer 2019
Knowledge Sharing Session

2. Agenda
● Motivation
● Objectives
● Common Project Roles
● Team/Technical Leader’s Characteristics
● Hard Skills
● What you need to do your job

3. Motivation
There is always space for improvement, no matter how long you’ve
been in the business – Oscar De La Hoya

4. Motivation
● Many Team Leaders/Technical Leaders are new to these roles.
● There are plenty of room for improvement.
● Managing expectations is the key (but before that, you’ll need to understand
what are expected).
● “Empowering your team” is a critical part of our job.
● Having strong Team Leaders/Technical Leaders is the only way to scale a
team without compromising delivery quality.

5. Objectives
Til your good is better and your better is best. – St. Jerome

6. Objectives
● Understand your roles
○ Requirements;
○ Expectations;
○ and the values you bring to the team.
● It is in everyone’s interest that you do your job well.
● Fulfill the expectations. Deliver values. And be happy (both professionally
and mentally).

7. Project Roles
Coming together is a beginning, staying together is progress, and
working together is success – Henry Ford

8. Common Project Roles
● Developer
● Senior Developer
● Technical Leader
● Team Leader
● Technical Architect
● QC
● QC Leader
● BA
● Senior BA/BA Lead
● Scrum Master
● Project Manager

9. Team/Technical Leader
Characteristics
None of us is as smart as all of us – Ken Blanchard

10. Team/Technical Leader?

11. Team/Technical Leader? (2)

12. Honesty and Integrity
Characteristics (1)
Confidence
Real integrity is doing the right thing, knowing
that nobody's going to know whether you did it
or not – Oprah Winfrey
Skill and confidence are an unconquered army – George
Herbert

13. Ability to Inspire
Characteristics (2)
Commitment and Passion
Find your voice and inspire others to find theirs
– Stephen Covey
The only limit to your impact is your
imagination and commitment – Tony Robbins

14. Communication
Characteristics (3)
Creativity
Think like a wise man but communicate
in the language of the people – William
Butler Yeats
The true sign of intelligence is not knowledge but
imagination – Albert Einstein

15. Decision-making Capabilities
Characteristics (4)
Accountability
Different perspectives, experiences, and insights
improve decision-making and lead to superior
performance – Lynne Doughtie
A good leader takes little more than his share of the
blame and little less than his share of the credit –
Arnold H. Glasow

16. Delegation and Empowerment
Characteristics (5)
Empathy
Sometimes you just have to be willing to delegate
and not feel like you're the only one with the answer
– Ronald D. Moore
Empathy is the starting point for creating a
community and taking action. It's the impetus for
creating change – Max Carver

17. Trust: years to earn, seconds to break.

18. Hard Skills
S.T.R.E.S.S. = Someone Trying to Repair Every Situation Solo

19. Job Knowledge
Demonstrate required job
skills and knowledge (i.e.
coding skills, testing skills,
analysis skills, etc) to
complete assigned
responsibilities.
Unless you try to do something
beyond what you have already
mastered, you will never grow –
Ronald E. Osborn

20. Accountability
Make and keep
commitments;
Complete assignments,
projects and goals within the
allotted timeframe and
budget.
When confronted with a
challenge, the committed heart
will search for a solution. The
undecided heart searches for an
escape – Andy Andrews

21. Responsibility
Take initiatives to keep
skillset (i.e. technology,
process, industry knowledge)
up to date.
Recognize potential problems
and take responsibility for
action; offer constructive
suggestions, initiatives; create
ideas and solutions for
improvement.
There are two primary choices in
life: to accept conditions as they
exist, or accept the responsibility
for changing them
– Denis Waitley

22. Work Quality Demonstrate the quality of
deliverables, for example,
the quality of code, test
results, design architecture,
requirement specification,
etc.
Quality means doing it right when
no one is looking – Henry Ford

23. Questions
1. Who does the code review?
2. Who does the task distribution?
3. Who makes the technical designs?
4. Who should help when a member gets blocked?
5. Who should resolve a conflict between team members?
6. Who follows up the tasks’ progress?
7. Who should detect an unhappy member?
8. Who should be accountable for the delivery quality?
9. Who should perform the technical trainings?
10.Who should push for the initiatives for the better?

24. What do you need
to do your job?
When everything seems to be going against you, remember that the
airplane takes off against the wind, not with it – Henry Ford

25. Questions you should ask
● What do I need my team to do?
● What do they need so they can do what I need them to do?
● How do I get them there?
● What do I need from my manager?

26. Perspective is everything
It's not what happens to you, but how you react to it that matters – Epictetus.

27. People often resist change because there is a
comfort in what we know.
[we] Don’t
● Build complex/complicated processes.
[we] Do
● Processes are built to benefit both the
team/company/client and the individuals;
● Lean processes.
Please
● Give ideas of improvements
● Be polite, considerate and constructive.
“Don’t find fault, find a remedy” – Henry Ford.
Continuous Improvement

28. Managing Expectations
Follow these tips
● Make no assumptions
● Communicate, communicate, communicate
● Pushing back is OK

29. Bonus: Leadership Levels