STMicroelectronics IT service Manager explains how requirement management and software development are managed at ST Worldwide : 10.000 active users, 5.000 R&D and embedded software projects.

1. My Tuleap Story #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
Denis PILAT
IT Service Manager
STMicroelectronics
@twitterdenis.pilat@st.com

2. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
STMicroelectronics/ ICT department
Internal challenges – for ICT
• ICT/SSE mission: provide efficient solutions to support software development activity in
ST WW.
• Challenges:
• Doing more and more with less and less resources.
In other words, increasing the efficiency of the Tuleap support team, and reducing
overhead related to Tuleap upgrade
• Better communicate Tuleap capabilities (most of our Tuleap users only know 30% of
features)

3. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
Why did ST choose Tuleap
• Legacy reasons. Old version already deployed in ST 13 years ago, so long before
Tuleap
• A centralized tool (versus several tools) with a centralized management reducing
resources.
• Supported by the provider thru a contract defining Service Level Agreements.
• No cost scaling when usage increases.
• And finally, migration to another system would be too expensive so benefits must
worth.

4. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
How do ST you use Tuleap
• Around 5000 active projects. Mostly R&D and embedded software. From 2 to 800 team members in a project.
• 10000 “active” users in different Tuleap, with any kind of profile, from SW developers to purchasing organization.
• Most of Tuleap features used. By decreasing order of importance : Subversion , Git, Trackers, Gerrit, wiki,, mailman,
docman, SOAP, REST, FRS and CI connectors …

5. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
What specific configurations ST made to meet your challenges?
• 4 Tuleap instances in production (plus 4 dev. and 4 qualification environments). One on the internet for
collaboration with external partners, customers and suppliers. 3 on the intranet for misc reasons.
• All Tuleap features are used at ST, but Agile is not used so much. For some services we have no mean to
analyze how it’s used.
• Gerrit is deployed and widely used, most of Jenkins server are under the responsibility of business groups
(not ICT)
• We put in place Git mirroring on 2 site where LAN performances were poor, but they are not used
anymore.

6. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
The gains
• Regular phase-out of multiple Git and Subversion servers around the planet, decreasing
management and maintenance overhead for the company.
• Phase-out of some other Forge or tracking systems with similar gains.
• Centralized data & application means more security, and more control.

7. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
The future of Tuleap in ST
• Light integration with Bugzilla (in Q3 2017)
• Deployment of agile methodologies
• Ramp-up of the Test Program Management platform including Jenkins
• Wish list:
✓ New instance of Gerrit for one Forge
✓ Deployment of Git pull request
✓ Usage of integrated test and validation tool
✓ More automation with ICT supported Jenkins (via Cloudbees offer or directly
Jenkins)

8. #TuleapCon2017 @TuleapOpenALM
100 % Agile & Open Source
My Tuleap Story
Thanks for your involvement
and for your contribution to Tuleap life