Mindset evolution by

overcoming four circles of IT-hell.

Roman LiashenkoProject manager at Ciklum (ADF Solutions)

https://www.linkedin.com/in/roma-liashenko-31a42439

lyashenkor@gmail.com

Agenda

Our hero

Circle 1. Developer.

Artist

Good project is:

● Creative ideas● Perfect code● New technologies● Cool atmosphere

Major priorities and risks● stable tasks flow with detailed

description● time for learning/investigation● interesting tasks● offbeat solutions● less legacy code● less disturbing

● reinventing the wheel, working on interesting tasks

● making quick and dirty crunches to complete tasks which are not interesting

● inattentiveness

Some phrasesPhrase Meaning

This task is too complex. I don’t want to work on this task.

It’s impossible to do this. I don’t know how to do this task and I don’t want to do a research.

This task is easy but I need to make a quick research.

I don’t know how to do this task, but it is very interesting for me.

We need to refactor this piece of code. I found dirty piece of code and I want someone to make it better.

Circle 2. Team Lead.

Sergeant

Good project is:

● good architecture● standardized code● stable solution● knit and motivated team

Prevalent myths and realityMyths: ● team lead is the same

developer but with more rights● team lead spends most time on

interesting technical activities● team lead perfectly knows the

application

Reality: ● team lead is responsible for the

whole technical side of the project

● team lead is responsible for the whole dev team

● team lead is spending most time on estimation and meetings

● team lead knows application worse than other devs

Some phrasesPhrase Meaning

I have no time to write the code I like to do the code, but I can not manage my own time to dedicate some for development.

Meetings are just a waste of time I don’t like to explain things which are simple as 1-2-3 for technicians, but my PM can not do this.

Estimate is very rough. We don’t want to predict the future and like the way to see how it’ll go after the start.

We need to do the deep refactoring I don’t like the way application is implemented and team will fix this no matter what.

Circle 3. Product owner.

Capitan

Good project is:

● product● strategy● flexibility● customers● piece of market

Focus and attention

Some phrasesPhrase Meaning

Let’s be agile. I have no idea what I’ll ask you to do tomorrow

It’s not about black and white. You are right, but I don’t want to lose my reputation in front of you

We need to review the estimate The estimate is too high we need to make it lower

Ok, do it. (short phrase after a long description of the the high complexity of the task)

I don’t want to dig deep into this, I’ll get back to you when it will start to take too much time.

Circle 4. Project manager.

Measurer-Facilitator.

Good project is:

● working process ● good communication● continuous deliverables● dedicated resources● clear risks

Activities

Some phrasesPhrase Meaning

(To the team) Guys I have an interesting task for estimate!

I received one more boring task and I know that nobody wants to estimate it, but we need to do this.

(To the client) We are actively working on this task it will be done in the nearest future.

I don’t know what’s the status of this task.

(To the Head of PM) Everything is fine we are on track.

I don’t know where we are, devs told me to relax.

(To the colleagues) I have no time for planning and analysis.

I can not manage my own time. As a result I can not manage time of my team.

And what?- One more IT story is shared - Couple more pieces added to the puzzle- Hopefully you had a good time

Thank you!

Have questions about our hero? Let’s discuss!

:)