21st century problem… the cost of it department!
•
1 like•86 views
21st-century problem… The cost of IT department! In this lightning talk, I want to outline the problem of today's times - the cost of IT department. Every company, every product, every department need them, but what is the real cost of their work. Step by step I will show it to the audience and stimulate discussion about these issues and possible ways to solve it. Let's meet, talk and find optimization possibilities!
Recommended
Recommended
More Related Content
Similar to 21st century problem… the cost of it department!
Similar to 21st century problem… the cost of it department! (20)
More from Krzysztof (Chris) Ozog
More from Krzysztof (Chris) Ozog (16)
Recently uploaded
Recently uploaded (20)
21st century problem… the cost of it department!
- 1. 21st-century problem… the cost of IT department! Chris Ozog - Codesushi CTO
- 2. We are optimizing costs via automation delivered by IT, who optimizing the costs of IT??? What is a real cost of building the software? Let’s check it out together!
- 3. Each product cost is a compilation of costs...
- 4. How usually companies are optimizing the costs? ➔ Fewer people - more automation ➔ Accounting - software ➔ Production - software ERP ➔ Software, Software, more Software, even more Software, SaaS, IaaS, PaaS, etc.
- 5. But what's the cost structure of the software? White collar thinking: ➔ Cost of implementation + hosting, maintenance etc. Blue collar thinking: ➔ Man-days, hourly rates, recruiting, training, offices, team building, environment, cloud hosting, DevOps, code reviews, refactoring, tests… releases 99% People, 1% everything else… In fact best-paid people in the world!!!
- 6. We need to go deeper...
- 7. Cost per feature? Cost per Activity! How much particular feature cost? What is the structure of this price?
- 8. Classic lifecycle of feature: User story created > Ticket added > Developer Assigned > Ticket Understanding > Coding > Googling > Debugging > Coding > Debugging > Googling > Coding > Googling > Debugging > Coding > Debugging > Googling > Coding > Googling > Debugging > Coding > Debugging > Googling > Coding > Googling > Debugging > Coding > Debugging > Googling > Pull request > Code review > Refactoring > (Googling > Coding) x Xh > Pull request > Pull request merged > Release!!!
- 10. Creating feature is essentially 2 types of activity CODING GOOGLING
- 11. Creating feature is essentially 2 types of activity CODING: ➔ Views ➔ Controllers ➔ Models ➔ DB GOOGLING: ➔ Hints ➔ Code samples ➔ Libs ➔ StackOverflow
- 12. What if we could get insights from each feature created? No more silent timesheets!
- 13. Thank you for your attention! Questions? If needed, this will be the easiest way to reach me: /krzysztofozog chris@codesushi.co