Maybe it sounds childlish, but this presentation is about understanding each other. And no, I didn't come up with this idea after watching one of the disney movies but after struggling with the same mistakes over and over.

1. Understanding a project
magic tip to improve your software
development process

2. This presentation is not about
• Process. A process is good and make us feel safe, but
often slows us down.
• Estimations and specifications. A good plan helps
us deliver what we planned, but not the best
product. And often just limits our creativity.
• Communication. If you have problems with
communication then, well, just start to
communicate, duh.

3. So what is it about?
• Understanding each other
• Stepping out of a comfort zone
• Learning to code, design, UX, sales of your product
• Learning that the way to communicate better is to
put yourself in someone else's shoes

4. Do you have any idea how other
team members work look like?
• We stick only to our narrow competences: Code,
graphic design, UX, sales, marketing
• We know the results of work of the others, but don’t
know why they do something this way and not that
way
• We often forget that the result we all want is the
best product ever created, not just ours part in it

5. If the whole product is not
great, nothing is
Not seeing the product as a
integrity is a common cause of
failure

6. What can you do?

7. Learn and understand things
outside your comfort zone
• Developers, learn some design. Designers, learn
basics of html/css at first. Product owners, learn
something more than just owning
• Share competences
• The whole team have to understand the idea
behind your application. How can your team love
the product if they don't understand its purpose?

8. What will you gain?
• You will understand why and how, not only what.
• You will start questioning. Why do we implement this
feature? Why do we use this template? Why don't we make
it simpler? Is there any faster/better way to do it?
• You will think how to make life easier for the other
team members. A well prepared PSD. A well described
feature.

9. Developers vs designers
Life example: our designer made stunning design with
beatiful shadows behind buttons. He doesn’t know that we
can implement in CSS only 90degrees shadow and made
70 instead. Seems like little thing, but you get the idea?

10. Project manager vs developer
Sometimes it seems that certain feature will take only few
minutes to implement. But moving this form 50 pixels left
will affect responsive design and instead of 10 minutes it
will take 2 hours of developer's precious time. Knowing
what obstacles you can encounter, helps you avoid wasting
time.

11. Product owner vs team
When we share only features to implement, not ideas
behind them, we loose the power of finding better
solution. "Do this or that" is far worse than "i want
accomlish this in that way. Any ideas how to make in
simplier?"

12. What next?
• Step out of your comfort zone and start learning other
things. You won’t become an expert, but it’s not the
point.
• Try to understand what are the reason of every decision
• Think how your decisions will affect other areas of the
product and other people work

13. Step out of your comfort zone
and to start to understand
each other!

14. Thanks!
Visit us at blog.123ship.it