3. Hello!
I AM ZVONIMIR KRIZ
I’ll give this talk because non-technical skills
in agile environment are important.
You can find me at:
@zvonekriz
http://zvonekriz.com
ˇ
4. Marko
too hardworking
to be missed
HOW A QUESTION ABOUT IMPORTANCE OF NON-TECHNICAL SKILLS ARISED IN MY HEAD
OR A TRUE STORY ABOUT MARKO AND BORNA
“Borna”
too introvert
to be kept
5. DON’T TAKE MY WORD
Let’s see the real data from a real research
I got 150+ responses,
from 14 countries (mostly Croatia and Serbia),
managers and developers,
what do they think about importance of non-technical skills.
A survey conducted during the spring/summer 2015 by Z.Kriz
6. DOES IT REALLY MATTER?
50% of employers are willing to pay 30%+ more for those skills!
RESEARCH RESULTS
7. HERE’S WHAT WE’RE GOING TO DO TODAY
START
STOP
EXPLORE 3
MOST IMPORTANT
SKILLS
DO
YOU
WANT
YOUR
+30%?
THINK AGAIN
LEARN HOW TO
"ADVERTISE"
YOUR SKILLS
GOOD FOR YOU!
Y
N
We’re going to
do this...
… and this.
8. WHAT IS (SURPRISINGLY)
NOT SO IMPORTANT
● knowledge about Scrum, Kanban, XP,... (<1%)
● motivator (<4%)
● domain knowledge (<6%)
X
RESEARCH RESULTS
9. WILLINGNESS TO LEARN
41%* of employers and teammates
wants you to constantly learn
*=every participant decided for 3 choices from predefined set of non-technical skills
1
RESEARCH RESULTS
10. Good
◦ distributed
practice
(iterations rather than big bang)
◦ practice testing
(do tests often)
◦ elaborative
interrogation
(ask yourself WHY)
LEARNING TECHNIQUES TO ADOPT
Bad
◦ summarization
◦ highlighting
◦ the keyword
mnemonic
◦ imagery use for
text learning
◦ rereading
Source: Association for Psychological Science: Improving Students’ Learning With Effective Learning Techniques: Promising
Directions From Cognitive and Educational Psychology by prof. John Dunlosky
http://www.psychologicalscience.org/index.php/publications/journals/pspi/learning-techniques.html
12. Bad
“I like to learn new
things.
I mean really...”
JOB INTERVIEW / CV CHEATSHEET ON LEARNING TOPICS
Good
“Last month
I invested in an
ElasticSearch
training, because I
like to learn about
new technologies.”
proof
concrete
technology
(means “I’m
not lying”)
13. PROBLEM SOLVING
40% of employers and teammates
wants you to focus and help
*=every participant decided for 3 choices from predefined set of non-technical skills
2
RESEARCH RESULTS
14. TO BE A PROBLEM SOLVER, YOU HAVE TO FIND WHAT IS A REAL PROBLEM
Lean offers a great set of tools for
a root cause analysis:
◦ 5 whys
◦ Fishbone
diagram
15. JOB INTERVIEW / CV CHEATSHEET ON PROBLEM SOLVING TOPIC
OR A TRUE STORY HOW a FomF GOT THE JOB AT RIMAC AUTOMOBILI
Prove that you’re a problem solver:
a friend
of my friend
16. COMMUNICATION SKILLS
32% of employers and teammates
wants you to communicate effectively
*=every participant decided for 3 choices from predefined set of non-technical skills
3
RESEARCH RESULTS
17. LOST IN EGYPT
?
WARNING: IN SOME CULTURES YOU MIGHT NEED A DIFFERENT
COMMUNICATION MODELS AND SKILLS!
18. “
Individuals and interactions over
processes and tools
Customer collaboration over
contract negotiation
The most efficient and effective
method of conveying information to
and within a development team is
face-to-face conversation.
19. JOB INTERVIEW / CV CHEATSHEET ON COMMUNICATION SKILLS TOPIC
Bad
“I have a good
communication
skills.
I mean,
everybody likes
me...”
Good
“For better communication, I use four-
ears model and I-message in my
everyday work”
concrete
methods/tools
(means “I’m not
lying”)
20. LEARN LIKE CRAZY
SOLVE REAL PROBLEMS
COMMUNICATE EFFECTIVELY
Every day.
P.S. Dont forget to do a self-promotion ;-)
22. CREDITS
Special thanks to all the people who helped
with this presentation:
◦ All people who participated in the
survey
◦ Marko, “Borna” and FomF for taking a
part of this presentation as a real
examples
◦ Presentation template by SlidesCarnival
Notes de l'éditeur
Before we begin, let's check if this topic is for you:
…
Well, I cannot guarantee, but I can tell you: If somebody applied this presentation during a job interview in my team, this person would have got the job for sure.
That's me:
-20 yrs building a software
- agile practitioner for 6 yrs
- right now - leading dev teams on a large international software project (Croatia, Hungary and Egypt)
Really glad to be here:
- we heard that this conference is full of head hunters that hunts for good developers
- after that they sent only me :)
Instead of explaining how this topic came to my mind, I will tell you the true story:
Marko
Came to job interview as one of 10 candidates
Candidates was all of a similar level
Marko was a begginer and was studying for 7 years
Was doing a “baustelle” in Germany for 2 years to pay for school
He got the job
Now he is a really good developer, proving every day that he's hardworker. Willing to learn.
Borna
Not a real name, universal name in Croatia, so it can stay a real anonymous
Even better coding skills then Marko at the beginning
very polite, but very introvert
didn’t communicate problems and didn’t cooperate with others
UNABLE to function as a part of an agile team
after a year, that person lost the job
That was a trigger for me: if you can get or lose a job on non-technical skills, then this skills are really important.
So I decided to investigate it a bit more.
Some friends complied that fellow developers are not important because they’re not giving you a salary. This is all wrong for at least two reasons:
you result depends about a TEAM
the youngest person here could be your next boss in a couple of months!
Here is the first data from a survey:
employers a willing to pay 30% more for non-technical skills that we’re going to discuss today.
Here is the language that we understand to describe what we’re going to do today:
So, we will reveal 3 most important non-technical skills for developers according to our survey.
But, even more important, we will try to teach you how you can tell employers that you have the skills that they need.
Before we reveal what is important, let’s see what is not important according to a survey:
1)somehow I feel that now I’m cutting the branch that I’m sittin on :)
I’m not saying that those skills are not important, but only that the following skills are more important.
Probably a disapointment now: Argh, this guy is going to deliver some generic talk. But, hold your horses, there are some very concrete things to say here:
For the begining:
I want you to do a small test. Think:
What have you learn this week?
If nothing: Why?
Remember, If you’re not learning constantly, you will probably face some job problems in the near future!
Bad:
Keyword mnemonic=mental images of similar word
Good
- Distributed practice: DOING a small steps in a short iterations
-Practice testing – experimenting (e.g. prototypes)
-Elaborative interrogation (e.g. connecting history events)
This is my invention.
By recalling and trying to understand what you have learned, you force yourself to apply it.
And now:
If you are a constant learner, it would be nice to properly communicate it when you’re applying for a job.
Imagine that bad situation. Would you, as an employer, beleive to that guy?
Instead, use proofs and concrete terms.
You may say: No shit Sharlok, everybody would like to be a problem solver.
BUT, the good news is that you can learn something that would improve your problem solving!
You cannot be a good problem solver if you don’t know what is the problem.
Have you heard about Rimac automobili? It is a startap which is the most desirable employer (2014) in Croatia.
They started from the blank paper and produced the fastest accelerating electric car (0 to 100 km/h in 2.8 seconds). The price is also hot: 1M EUR!
A FomF was tired of job refusals. So he decided, instead of CV, he did a real research for wheelchair batteries for US market, and sent it to Rimac automobili as a job application.
A next day, a founder Mr. Mate Rimac gave him a call and asked if he can start to work tomorrow.
The third most desirable skill.
Please, I’m not talking about good and bad, but only that...
In some cultures developers are “unable” to say “No” or “Not possible”
Does this sound familiar? What is this?
See? An effective communication is a must-have for agile teams!
majica prvome
4 ears model = based on 4 layers of communication: MATTER, SELF-REVEALING, RELATIONSHIP, APPEAL. The sender has 4 tongues and recipient has 4 ears.
i-message=Starting sentences with „I”. E.g. „I feel that we have a problem with ”. In contrast with „You message”.
Joke: „I think that YOU messed up” J