13.12.2012
Need for Speed (N4S)
Tommi Mikkonen/Tampere University of Technology
Motivation
• The widespread adoption of the World Wide Web is reshaping
our world in various ways
– The software industry is on the brink of a similar transformation, or a
paradigm shift; web-based software will dramatically change the way
people develop, deploy and use software.
• Internet of Services & Things, SW Development, Customers
and Consumers will be more and more interlinked.
– Need for Improved management and control via appropriate
measurement systems – better understanding of SW business and
users’ values
• Need for effective software development and deployment
tools and methods which enable global deployment and fast
feedback for improvement
1
13.12.2012
Elements of speed in the web era
• Lean and agile development
• Organizational issue; methodology issue
• Continuous integration
• Automation, infrastructure, methodology (e.g. test-driven development)
• Continuous deployment
• Even more automation and infrastructure
• Automatic feedback from real users at real time
• A/B testing (compares the effectiveness of two versions of a web page,
marketing email, or the like to discover which has better response rate,
better sales conversion rate, or the like.)
• Architectures flexible enough to support new features as well as
removal of obsolete ones
• Built-in support needed in all implemented systems
3
Goals of Need for Speed
2
13.12.2012
Breakthrough targets
• Cut the lead time of software
development by 20%
• Cut the lead time of software
deployment by 50%
5
A grand software challenge of 2010s:
How can we do this?
• Create best practices for internet speed development and
deployment of software
– Executed in close cooperation with companies
• Experiment the approach in true products with real clients
– Different products with different characteristics welcomed (e.g. web
services, shrink-wrapped software, embedded systems, …)
• Based on best practices, distill a unified methodology
– Affects both technical artefacts (architecture, build system etc) and
process
• Construct a toolset that supports the methodology
– Already existing components and tools will gladly be adopted (e.g. A/B
testing systems, feedback channels, databases for data mining
feedback, etc)
6
3
13.12.2012
Need for Speed (N4S) preparation
Core team (in arbitrary order and tentative)
• Research
– Tua Huomo (VTT)
– Satu Miettinen (University of
Lapland)
– Tommi Mikkonen (Tampere U. of
Tech)
– Tomi Männistö (Aalto University)
– Markku Oivo (Oulu University)
– Pasi Tyrväinen (University of
Jyväskylä)
• Companies
–
–
–
–
–
–
Janne Järvinen (F-Secure)
Kimmo Kouhi (OpusCapita)
Pasi Kovanen (Vincit)
Jari Partanen (Elektrobit)
yyy (Ericsson)
…
• There is still room for active
companies to drive this
• There is still room for active
drivers (with good industry
connections, as this is companyled research in the end)
21.06.2012/SeLa
8
4
13.12.2012
N4S Preparation Schedule 2013
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
N4S
workshops
SRA
Preparation
N4S Program Plan
N4S Plannign &
Tekes Applications
N4S Workshops
SRA
Preparation
workshops
N4S Workshops
SRA Proposal to
Tivit BoD 05/2013
are
organized Jan/Feb 2013 in Capital
Region, Tampere and Oulu,
See www.tivit.fi for more information.
N4S Program Plan
proposal to Tivit BoD
09/2013
N4S Kick-off
Jan 2014
21.06.2012/SeLa
Preparation schedule refined
• Hosted by VTT in Espoo, Tampere and Oulu
• SRA Preparation workshop schedule 2013
– Feb 6., Espoo, Vuorimiehentie 3,
– Feb 14., Tampere, Tekniikankatu 1
– Feb 21., Oulu, Kaitoväylä 1
• Core team meeting for go/no go scheduled for Feb 22 in Oulu
• If positive decision, SRA planned for TIVIT BoD May meeting
21.06.2012/SeLa
10
5