1) F-Secure developed an internal open source cloud infrastructure and common platform to enable agile software development across multiple global teams. 2) Any employee can directly contribute code changes, with automated tests running continuously to detect issues. Status boards display test results to quickly identify and address failures. 3) Key aspects that allow it to scale include feature teams with end-to-end responsibilities, continuous integration, strong test automation, management support, and an emphasis on quick fixing of broken builds.

1. Scaling Software Development throughInternal Open Source Cloud Infrastructure Chee-Chan Keng Senior Manager, R&D

2. F-Secure KL R&D and I © F-Secure 2011 June 28, 2011 2 Keng Chee Chan Senior Manager2007–current Quality Engineering Competence Security Research Program Project Manager &Sr. Software Engineer2001–2007 Network Management Systems iDEN CDMA GSM

3. What did we learn from Open Source Community? How do most people learn about Python or Android development? How does someone get on board through the documentation? Is knowledge transfer needed when Open Source project members leave the project? Is staff attrition a potentially critical issue for Open Source Projects? Do we need mega planning and meetings to plan and design the solution? How many managers are needed to run open source projects? © F-Secure 2011 June 28, 2011 3 How can companies reap the benefits of crowd in the world of open source? Could it advantageous to companies that have similar practice within the company?

5. Blowing it big with Continuous Integration & test automation

6. Internal open source with Code Guardians

7. Everyone has equal rights to make changes

8. Agile Transformation

9. Feature Teams

10. More flexibility in sharing the code

11. 1 team per component

12. Code guarded by component teams

13. Too many requests from different products

14. Too much planning and handover

16. Major architecture changes to enable common-platform development

17. Proactive engineers and strong management support

18. Simple product lines

19. Less teamsFrom triggers… to outcome 2005 2010

20. From Component Teams to Feature Teams © F-Secure 2011 June 28, 2011 5 Feature Team 1 Feature Team 3 Feature Team 2 Head Team Eyes Team Ears Team Hand 1 Team Hand 2 Team Common Practice,Common PlatformContinuous Integration Leg 2 Team Leg 1 Team Feature Team 6 Feature Team 4 Team specific practice,Different Platforms, Integration hell Feature Team 5

21. F-Secure’s Internal Open Source Platform A private cloud platform to enable open source use and development within R&D Foundation of our product development with many people developing it 24/5 Over 100,000 automated tests executed automatically in the cloud, either triggered automatically with code changes, or triggered daily Anybody can make improvements to the system, the person can be a programmer, tester, architect, Scrum Master, Product Owner, or a manager Examples of Open Source software used: Linux distributions Jenkins Eclipse Python + nosetests © F-Secure 2011 June 28, 2011 6 What’s new?

22. F-Secure Global Private Cloud in 2010 © F-Secure Confidential June 28, 2011 7 Hundreds of Virtual Machinesthat relies on Python Test Automations

23. Damage Control… Anybody can make code improvements to the system… But when someone checks in codes that fail the system, how do we detect and fix it? © F-Secure 2011 June 28, 2011 8

25. Tests are automatically triggered whenever code changes happen

26. Test Automations driven by Jenkins, written mainly in Python Language

27. Tests should pass at all times, lots of effort and commitment required

30. How to Scale this in the Lean & Agile Way? F-Secure’sWays of Working: Continuous Integration for fast feedback Programmers and testers shares the same Test Automation system Formation of effective feature teams Strong management support and involvement in change management Avoid dedicated central control - “It is everyone’s responsibility” 2-week sprints demo to manage expectations Every team owns end-to-end software development responsibility © F-Secure 2011 June 28, 2011 12

31. Internal Open Source in Action! © F-Secure 2011 June 28, 2011 13 Contributors F-Secure’s Internal Open Source:Scale Confidently through Sufficient Test Automation