Slides voor de introductie van de cursus Continuous Delivery 3.0 van het Nederlands Instituut voor de Software Industrie.
NISI is een spin off van Universiteit Utrecht. www.nisi.nl
2. Key needs of the Software Industry
• Employees, Employees, Employees
• Continuous Education
• Knowledge for Business and Product Innovation
– Generic software technology
– Generic development tooling
– Generic entrepreneurship knowledge
• Means
– National research and education initiative
– Post-graduate certification curricula
– Joint research programmes
3. Netherlands Institute for the Software Industry
• Initiative Utrecht University:
– prof. S. Brinkkemper
– Dr. S. Jansen
– Dr. J. Vlietland
– G. Lucassen MSc
• Currently three successful courses:
– Software Product Management
– Continuous Delivery 3.0
– Advanced Agile Product Ownership
4. • NISI is a spin-off of Utrecht University
• Mission: advance the software industry in the Netherlands, by
providing – Network – Innovation - Knowledge
• Research agenda:
–Continuous Delivery
–Agile Software Architectures
–Agility & Agile scaling
4
NISI mission
5. 1. NISI Academy
2. NISI Scans & Assessments
3. Knowledge & Skills for the software industry
4. Knowledge Hub towards universities
5
NISI Services
6. Post-graduate certification
• During BSc/MSc in Computer Science/Software Engineering: just 1 or 2
courses on Architecture, Requirements Engineering, Delivery,
Development
• Need for continuous education
• Companies want to invest in personnel
• Personnel certification, e.g. individuals
• Areas: Software Architect; Product Management, Delivery Management,
Software Management, Software Development
7. 7
NISI core team
Dr. Jan Vlietland has a
doctorate in Agile eco-
systems, is co-founder and
head of NISI, and has been
working in the software
industry for over 20 years.
Prof. Sjaak Brinkkemper is
head of the faculty of
Information and Computer
Science and professor at
Utrecht University, and NISI
initiator.
Dr. Slinger Jansen is assistant
professor at the faculty of
Information and Computer
Science of Utrecht University,
and heads research at large
software companies.
Garm Lucassen performs PhD
research about User Stories.
9. CD 3.0 lecturer Team
Jan Vlietland Arjan Franzen Maikel Meeuwse Fabiano Dalpiaz
Sjaak Brinkkemper Slinger Jansen Ewan Klomp Garm Lucassen
9
10. Course Objectives
• Help companies to cope with fast moving markets
• Advance participants knowledge about Continuous Delivery
3.0
• Help participants to implement CD 3.0 in their organizations
• Knowledge sharing between Continuous Delivery experts of
different companies
• Certification by NISI
10
11. Certification
• Continuous Delivery 3.0 exam and certification at the end of
the course
• We are currently transferring the Continuous Delivery 3.0
certification to the International Software Product
Management Association (ISPMA)
12. • What would you like to know about Continuous Delivery?
• How do you currently track usage of your software?
• How do you select the work for your developers?
• What do you hope to find in this session/course?
Participants Needs
12
14. • Continuous Delivery enables fast delivery of new software to the market, with
technology that integrates, tests en distributes software in a fast pace
• But what do you need to have in place to enable such delivery?
• And how to grasp the need of your customers and market?
• How do your select the right features to deliver customer oriented software?
• This course offers answers to these questions!
• We take modern software companies as an example and go in the details of a
Continuous Delivery 3.0 cycle from concept to cash.
14
Market theme
17. Continuous Delivery 3.0 defined
Continuous delivery (CD) is the automation of the software delivery process,
which enables teams to continuously produce software. It aims at building,
testing, and releasing software faster and more frequently.
Continuous delivery 3.0 (CD3.0) is the automation of the full software
engineering cycle, which enables teams to continuously produce software,
track usage and adapt planned engineering. It aims at tracking, planning,
building, testing, and releasing software faster and more frequently.
Sources: https://en.wikipedia.org/wiki/Continuous_delivery
18. Continuous Delivery topics
Commit Build
Check
Code
Quality
Store
in
respository
Unit
testing
Acceptance
testing
Performance
testing
Deploy
on
acceptance
Deploy
on
performance
environment
Deploy
to
production
Continuous
Testing
Continuous
Deployment
Continuous
Integration
31. Cross Browser Fingerprinting
• Uses code that instructs browsers to perform a variety of
tasks.
• Those tasks, in turn, draw on operating-system and
hardware resources—including graphics cards, multiple
CPU cores, audio cards, and installed fonts
• Works slightly different for each computer.
• The cross-browser fingerprinting carries out 20 carefully
selected tasks that use the WebGL standard for
rendering 3D graphics in browsers. In all, 36 new
features work independently of a specific browser.
• Over time it builds consistent unique profile
identifications with a 99% success rate
Source : http://yinzhicao.org/TrackingFree/crossbrowsertracking_NDSS17.pdf: Cao, Li & Wijmans (2017)
33. • Linking data – linking data from various sources
• Correlation Analysis – researches the relationships between variables
• Regression Analysis – researches the causal relationship between one
or more independent variables and a dependent variable
• Monte Carlo – simulation method in which a physical process is
simulated many times, each time with different starting conditions
• Neural networks – analyzing mathematical models with a neural
network, by recognizing patterns and manipulating data
33
Data Analyzing Methods
Data
Analyzing
47. Making Improvements
Requirements
5 days
2 : 3 days
Sign Off
10 days
1 : 9 days
Analysis
5 days
4 : 1 days
Code
2 days
2 : 0 days
Test
6 days
1 : 5 days
Review
10 days
1 : 9 days
Deploy
15 days
1 : 14 days
1 day 5 day 4 day 5 day
4 day 3 day40% rejected / Repeat 2x
20% rejected / Repeat 1x
48. Practical Sample Value Stream Map
Source: http://mediad.publicbroadcasting.net/p/kwmu/files/styles/x_large/public/201105/ED_War_Room.JPG