Ask questions

Tell things

• Won't feed you today
• Opportunities
• More influence

Strategic Value

• Immediate value and benefits
• Get Stuff Done
• More freedom

Tactical Value

Tech Spiral

Learn from History

Yes, I am sure I will do this in 5 years and pursue this goal whatever it costs

Learn first how to cope with failures yourself

• How do you feel about it?

• How do you learn from it?

• How do you fix the consequences?

Learn from other people failures 

• Networking!

• Conferences, Meetups, Chat rooms

• Case Studies

• Share Failures!

Failure is the source of experience

Experience is the source of intuition

Survivorship Bias

Failures and Edge Cases 

are essential to our craft

Respond to failures

Safety Nets / Plan B

...as much as we want them to

My team is proficient with it

People are excited by this technology

Easy to find and add new people

Helps to do things right

The only one working method

Rule #0:

never talk about refactoring

Rule #1: 

Refactoring is an essential part of a task

Rule #2: 

Boy Scout Rule

Always leave the code behind
in a better state
than you found it

Inverted Pyramid

Rule #0:

Do not explain the answer 

before

answering the question

Rule #1:

Start with

the single most important

fact

Not to "be right"

Not to "be better"

Close the loop: offer some options

Constructive: help them become better

the ultimate relationship destroyer

the ultimate happiness killer

Eye contact

Relaxed Attention

Imagine things

No interruptions and suggestions

Body language

Feedback

Blogging

Chats

Talk to people

Well-Crafted Software >  working software 

Steadily adding Value > responding to change

A Community of Professionals > individuals and interactions

Productive  Partnerships >  customer collaborations

... is still a mess

"Agency - Customer" model

Warzone methodology

Expert-Driven micromanagement

Pull-based model

Involves everyone

Quotas

Eliminating Waste

We are still "not there"

 Sustainable and reliable progress

Getting things out of your head

Fighting complexity

Changeability

No more than 2 weeks!

Include all phases

Implementation

Testing

Logging / Metrics

Design / Refactoring

30%     Implementation

30%     Testing

10%      Logging / Metrics

30%     Design / Refactoring

Realistic estimate = 3 * implementation time

Divide & Conquer:
Epics, Stories, Tasks

Make optimistic task estimates

Add time boxed investigations

Include risks

4 weeks per story max, otherwise investigate!

Bus Factor

Illness

Fuck ups

Vacations

Holidays

Design Mistakes