Product Roadmap vs Development. Thoughts about business and IT alignment

1. TECHNICAL
ROADMAP
Thoughts about business and IT alignment

2. About me
■Software engineer
■Running Gemotial Software Studio
■Co-organizer ofWrocNET
■Blog: http://blog.klimczyk.pl
■E-mail: pawel@klimczyk.pl
■Twitter: @pwlklm

3. What I do
Software Quality/SOLID
jobesto.com
C#/.NET/BizTalk
netdevelopers.pl
BJJ

4. 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

5. 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/

6. Startup

7. Enterprise

8. Why we ended
up like that?

9. Different perspectives

10. Communication

11. Fast development =>Technical Debt

12. Killer feature
or
Killing feature
hint: ask developers for feedback

13. Treat developers as part
of business team, not
like code monkeys

14. Delegate responsibility
instead of work
and
provide environment

15. Product roadmap build by the
whole team
leads to
common understanding and
same goals

16. Technical vocabulary
■Domain Driven Development
■Agile/SCRUM
■Continuous Integration/Continuous Delivery
■Technology Stack
■Technical Debt

17. Share the map and aim
for the goal…. same
goal.

18. Book

19. Thank you
Blog: http://blog.klimczyk.pl
E-mail: pawel@klimczyk.pl
Twitter: @pwlklm