TECHNICAL ROADMAP

Thoughts about business and IT alignment

About me

■Software engineer■Running Gemotial Software Studio

■Co-organizer of WrocNET■Blog: http://blog.klimczyk.pl■E-mail: pawel@klimczyk.pl■Twitter: @pwlklm

What I do

Software Quality/SOLIDjobesto.comC#/.NET/BizTalknetdevelopers.pl BJJ

Research on IT projects failures■75% of business and IT executives anticipate their

software projects will fail. (Geneca)■Fewer than a third of all projects were successfully

completed on time and on budget over the past year.

■Around 33% projects meet failure due to lack of involvement from senior management. (University of Ottawa)

■35% of organizations abandoned a major project in the last 3 years (Logica)

■37% of business process change projects fail to deliver benefits (Logica)Source: http://calleam.com/WTPF/?page_id=1445

Failed startups testimonies■did not scale fast enough■ it would not work due to security restrictions■did not scale■dependent on another platform■ ran out of money. Pivoted too soon.■another casualty in the decline of Flash■complex and buggy product■apple built NFC into new product line

Source: http://autopsy.io/

Startup

Founders

Developer

Enterprise

Developers

CEO

Managers

COOCF

O

CTO

Why we ended up like

that?

Different perspectivesBusiness Development

CommunicationBusiness Development

Fast development => Technical Debt

Killer feature or

Killing featurehint: ask developers for feedback

Treat developers as part of business

team, not like code monkeys

Delegate responsibility instead of work

and provide environment

Product roadmap build by the whole team

leads tocommon

understanding and same goals

Technical vocabulary

■Domain Driven Development■Agile/SCRUM■Continuous Integration/Continuous

Delivery■Technology Stack■Technical Debt

Share the map and aim for the goal….

same goal.

Book

Thank youBlog: http://blog.klimczyk.plE-mail: pawel@klimczyk.plTwitter: @pwlklm