Embed Size (px)
DESCRIPTION
On August 14, in the format of Tech Hangout internal meetings Galina Kostetskaya, Engineering Manager at Innovecs, shared her experience and told the crowd what to do to avoid Killing Your Project. *TECH HANGOUT COMMUNITY was found in 2012 by the developers for the developers for knowledge and experience sharing. Such meetings are the part of Innovecs Educational Project that actively develops sphere of internal trainings and knowledge exchange program among professionals. This Initiative was born within the walls of Innovecs and has proved to be extremely popular and high-demand. In a short period of time it gained its own Facebook group with more than 100 members, blog with more than 40 posts and constant quarterly external meeting of Tech hangout community with more than 80 participants. The concept of the event proposes a 30-minute report on the topic previously defined, and the discussion in a roundtable session format. Join to discuss - https://www.facebook.com/groups/techhangout/
Citation preview
The Best Way to Kill YourProject
Galina KostetskayaEngineering Manager
14/08/2014
Today’s agenda
••••••
Technical debtTestsSqueeze the juiceCrappy code4 easy steps for PMs How to understand, that trouble
we are in a
• What PMstuffQ&A
can do about all of that
•2© Copyright Innovecs 2012
It always starts in a very !optimistic way….
3© Copyright Innovecs 2012
Technical debt
is a term to describe the cumulativeconsequences of corners being
developmentcut
throughoutprocess.
the
4© Copyright Innovecs 2012
Technical debt
5© Copyright Innovecs 2012
They are so serious, as they are observing how the tech debt is born. 10 sec before the push.
Someone just said “Let’s fix it after the demo”.
6© Copyright Innovecs 2012
Tests
Your project is like a rocket – you aremoving so fast, that you have notime for unit tests.
7© Copyright Innovecs 2012
Squeeze the juice
•Short-term speed (Sprint) !•Long-term speed (Marathon)
you can't have both
8© Copyright Innovecs 2012
Squeeze the juice
9© Copyright Innovecs 2012
Crappy code!
10© Copyright Innovecs 2012
CRAPPY CODE!rescue kit for PMs (in 4 steps)
11© Copyright Innovecs 2012
Step 1. Identify the problem.
If you hear that the code is crapwhile drinking coffee at the kitchen or passing by thedeveloper’s table – it’s a bit late.
12© Copyright Innovecs 2012
Step 2. Identify the reason.
Crappy code exists becauseit.developers created
13© Copyright Innovecs 2012
Step 3: Act
STOP WRITING JUNK CODE.Just stop doing it.
14© Copyright Innovecs 2012
What if you don’t
15© Copyright Innovecs 2012
What can help
•••
Keep your test’s green.Definition of done.You inherited crappy code fromyour descendants: It is not possible to “overwrite everything” as your team advices you. Just start with reducing the tech debt.
16© Copyright Innovecs 2012
What if you do
17© Copyright Innovecs 2012
Step 4: Everything isIt’s time to monitor)
ok now?
Add the subcolumn “Tech debt” to your board. Check the “Code health” rate during the daily meeting/retrospective.
•
•
18© Copyright Innovecs 2012
How to understand, that weare in a trouble
•You•The
don’t produce any tech debt.bugs don’t stop.
•Your code has too many // @todo: comeback and fix!
•You have no tests.•Developers don’t perform refactoring.•Velocity is going down.•You have a lot of “places” everyone is scared to touch as they “just work”
19© Copyright Innovecs 2012
What PM can do
•Do not ask your client’s if they needunit tests. If they need refactoring. You just do that.
•Set the process. Just set it, no“will do it later’ aloud.
mess or
•Make your tech dept visible.•Share the code. •Perform code reviews.
20© Copyright Innovecs 2012
21© Copyright Innovecs 2012
Thank you!!
Galina Kostetskaya!
Engineering Manager!
