How to choose the right technology or tooling in IT? A presentation by Yakup Kalin (ACA IT-Solutions). It's not easy to know which technology you should keep an eye on or which tool you can use best in a specific situation. Customers, however, expect that consultants are in line with everything going on in the market. Yakup Kalin will present various techniques to show how you can deal with this in the best possible way. Some examples of methods that will be discussed: IT Maturity: Capability Maturity Model Magic Quadrant Forrester Wave Cocomo Model Gartner Cricital Capabilities Methodology

1. How to choose the
right technology / tooling in IT
Yakup Kalin
@yakupkalin

2. Yakup Kalin
Mobile Solution Expert & Team Lead
@YakupKalin
mobile.aca-it.be

3. I'm involved in agile mobile
development, where I develop and
deliver creative input for realizing
usable and likeable mobile
applications.

4. embraced tools
(tools: technology, development language,
libraries, frameworks, methodologies, …)

5. Creating applications

6. And most of the time…

7. Developer:
Why tool a, and not tool b?

8. Email:
Did you hear about tool b, it’s
very cool?!

9. IT Article:
Tool b is better than tool a.

10. Business:
Tool e is FREE

11. Explain why

12. Do you know why?

13. You should.

14. Do you know why JAVA?

15. Do you know why .NET?

16. Are you sure about PHP?

17. naturally and unaware
(school, 7 years experience, colleague, windows/mac, …)

18. Your choice, defines you/project

20. Eliminate options

21. Part of a selection process
naturally and unaware

22. Aware

23. A tool/concept

24. Technology Radar
Thoughtworks

25. a living document
to assess the risks and rewards of
existing and emerging tools/tech.

27. 4 Rings
Adopt
Trial
Assess
Hold

28. 4 Rings
Adopt
Trial
Assess
Hold

29. 4 Rings
Adopt
Trial
Assess
Hold

30. 4 Rings
Adopt
Trial
Assess
Hold

31. 4 Rings
Adopt
Trial
Assess
Hold

33. Balance risk vs. adoption

34. A platform for continual analysis

35. Unified message from the
technical to the interested-but-non-
technical

36. Excuse to have impassioned
conversations about technology

37. Helps align business and IT views
on technology

38. 1. Angular

39. Selection criteria

40. Personal preferences

41. 2 Radars
Personal radar
Project/company radar

42. Personal radar
Project/company radar
preferences, resources,
experience, learning curve, …
company culture, resources, enterprise support,
focus, cost, …

43. Yakup Kalin
Radar match

44. 1. Angular1

45. Who is next?

49. Critical Capabilities Methodology
(Based on Gartner)

50. Define use cases
(enterprise mobile dev, enterprise web dev,
hackaton, release, …)

51. Define critical capabilities
(performance, security, scalability, enterprise support, …)

52. p1 p2 p3 …
Rating within use case

53. Result
in points
/5
Angular
Polymer
…

56. Promising, emerging
and phasing out providers/tools

57. Don’t copy paste,
make your own.

58. Okay, what do we know now?

59. 1. Make your selection (aware)
2. Create your radars (personal / company)
3. Keep an eye on tools/tech (follow up)
4. Don’t reinvent the wheel

60. 1. Make your selection (aware)
2. Create your radars (personal / company)
3. Keep an eye on tools/tech (follow up)
4. Don’t reinvent the wheel

61. 1. Make your selection (aware)
2. Create your radars (personal / company)
3. Keep an eye on tools/tech (follow up)
4. Don’t reinvent the wheel

62. 1. Make your selection (aware)
2. Create your radars (personal / company)
3. Keep an eye on tools/tech (follow up)
4. Don’t reinvent the wheel

63. Validated choices of
tools/technology

64. Influence
tools/technology

65. YOU!

66. Developers are leading indicators
of technology shifts (Forrester)

67. If you know what technologies are growing out in
the social coding community and where
developers are investing their time, it’s possible to
predict what technologies might seep into the
enterprise through the back door.
(Forrester)

68. Good to know
before introducing a tool…

69. COCOMO

70. The Constructive Cost Model
(COCOMO)
is a software cost estimation
model

71. It predicts the effort and schedule for a
software product development based on
inputs relating to the size of the software and
a number of cost drivers that affect
productivity
COCOMO

72. Basic model
Intermediate model
Detailed model
3 Models

73. Basic model
1. Quick, early, rough order of magnitude
estimates of software costs
2. Does not account for differences in hardware,
constraints, personnel quality and
experience, ...

75. www.openhub.net
Discover, Track and Compare Open Source
BlackDuck

77. Introducing a specific tool
not always a good idea

78. Software development process

79. Design, develop, integrate & test
Project planning, project monitoring,
measurement & analysis, ….

81. Defines
Quality

82. The Capability Maturity Model (CMM) is
a methodology used to develop and
refine an organization's software
development process.

84. Introducing an innovation tool
within company at ”initial” stage

85. Introducing tool that
eliminates risk and waste

86. Why so important?
Why are you telling me this Yakup?

87. Consultants / Freelancers
Provides expert advice in a particular area and generally
engages with multiple and changing clients.

89. Key takeaways
1. Create your radars
2. Validate your choices
3. You are an influencer
4. Company maturity/context
5. Step by step

90. How to choose the
right technology / tooling in IT
Yakup Kalin
@yakupkalin