This document discusses how DevOps practices can improve software development. It begins by providing background on the author and their company Eficode. It then contrasts classic/waterfall software development approaches with more modern agile approaches enabled by DevOps. Classic approaches are prone to "Epic Fail" through lack of prioritization, coordination, and automation. Modern approaches emphasize prioritizing requirements, completing features incrementally, defining minimum viable products, sharing information efficiently, continuous optimization, embracing automation and tools, building cross-functional teams, and applying DevOps practices across the entire organization and product development lifecycle.

1. Timo Stordell
24-Mar-2017
Boosting Your SW Development
with Devops

2. ABOUT EFICODE
130
EMPLOYEES
DEVOPS PIONEER
SINCE
2005
CURRENT
TURNOVER
10 M€
OPERATES FROM
HELSINKI
TAMPERE
STOCKHOLM
COPENHAGEN
BEIJING

3. PERSONAL HISTORY
● 17 years in telecom R&D:
SW, integration, testing, methods, tools
● 3 years of consulting devops practices:
methods, automation, audits
● Versatile experience from different roles in R&D

4. “Our highest priority is
to satisfy the customer
through early and continuous
delivery of valuable software.”

5. THE NAKED TRUTH
ABOUT AGILITY
Most of the organizations
that claim to be agile
are not

6. CLASSIC R&D
● Controlled by processes that are defined to
different phases, practices and monitoring
● Based on common tools that don’t work
together, and team-based tools that are not
available for all
● Projects are long and multi-phased
● Lead often to Epic Fail™

7. EPIC FAIL:
Tips for Planning
● Accept always all new requirements
● Don’t update the schedule when doing so
● Don’t prioritize, start the implementation
of all features in parallel at once

8. EPIC FAIL:
Tips for Coordination
● Make an optimistic plan and write it in stone
● Constantly request schedule updates from
the teams. Accept only those that support the
optimistic plan.
● Control. Don’t share responsibilities.

9. EPIC FAIL:
Tips for Development Process
● Create agile teams but keep the
project in waterfall mode
● Don’t bother to ensure that important
information is shared in the project
● “We have always done it this way”

10. EPIC FAIL:
Tips for R&D
● Use only slow and cumbersome tools.
Make good excuses why it has to be so.
● Automate nothing
● Embedded systems: Develop and test
using only immature prototypes
● Keep SW, testing and operations in silos

11. THAT’S ENOUGH!

12. LET’S RATHER
BUILD FOR SUCCESS

13. MODERN R&D
● Traditional products need to be transformed to
interesting digital services
● New concepts and technologies are coming up
frequently and ever faster
● Concepts need to be piloted quickly; discarding
defunct and proceeding with the potent ones (fail fast)
● Organizations are getting global; how to keep
practices harmonized and agile

14. PLAN AND COORDINATION
● Prioritize requirements ✅
● Complete features one by one, create
releases that are ready for production ✅
● Define the minimum viable product ✅

15. DEVELOPMENT PROCESS
● Bring agile mindset to the whole
organization ✅
● Keep important information shared
efficiently ✅
● Continuously optimize the R&D
pipeline with experiments ✅

16. R&D
● Love your IT: Use only tools make R&D
more efficient ✅
● Automate the tasks that are boring,
repetitive or critical ✅
● Utilize virtualization everywhere ✅
● Build cross-functional teams ✅

17. DEVOPS CULTURE TO THE ORGANIZATION
REQUIREMENTS
MANAGEMENT
ACCEPTANCE
TESTING
DEVELOPMENT
ENVIRONMENTS
PACKET
MANAGEMENT
TECHNICAL TESTING
VERSION CONTROL
CONTINUOUS DELIVERY
CODE ANALYSIS
PRODUCTION
SERVER
ENVIRONMENTS
MONITORING
BUSINESS REQUIREMENTS
TECHNICAL NEEDS
OPERATIONS
VIRTUALIZATION
AND
ORCHESTRATION

18. AUTOMATION
VIRTUALIZATION
SMART TOOL CHOICES

19. EVERYTHING IS CODE
TIMO STORDELL
timo.stordell@eficode.com
+358 40 5459865