Ericsson India and Agile Ways of Working
By Hedwig Baars, Head R&D India

Who we are
• R&D India located at Gurgaon & Chennai.
• Growing from 180 to above 300 today in one year
• Handling 9 products mainly in GSM networks
• 5 years in Gurgaon and 3 years in Chennai into R&D
• We are hosted with in Ericsson Market Unit India & Sri
Lanka (over 6000 employees)

We come from a Complex World (Charging System Architecture)
0..n Historical Data from
DNS update
Core Network VXML IVR DWS (if MINSAT, XML/http)
to AF Same platform (FDS/Sun)
Co-locatable
Charging
ISUP 1 Batch jobs
CC API (CAI) System
0..n
1..n 0..n
NQ
(if MINSAT) MINSAT (ftp) 1..n
Batch jobs 4.0 FD1
MSC CS1+, SCP-T IN-IVR HP IVR POSI, PAMI
XML/http VS (ftp)
gsmSSF CAP (if ASCS) VSIP
v1-v2 gsmSCF Charging
gsmSRF SCF XML/http
System-IN XML/http
SSF / SRF CS1+
RPC XML/http
CS1+, MML DQ
CAPv1-v3 1..n
1..n R
SMAS TMA Thresh.
Notif.
Batch
jobs
AIR
ERTC Batch jobs (ftp)
(ftp) (ftp)
UCIP
INS VPN
CS1+
RPC ACIP
1..n R
LDAP towards
0..n DQ ext. system R Ericsson Rating Engine
SGSN CAPv3 SDP (Community) DQ 0..n
0..n
MML Internal Interface
gprsSSF CS1+
CIP-IP
(lifecycle AF Open Interface
0..n
0..1
CCN notifications) DNS update
from ADM Verified Interface
GGSN SCAP, NQ
SASN SCAPv2/ gsmSCF LDAP
SCF Recovery and Interface towards nodes
R
CAI (barring)
DCCA containing ERE
Synchronization (ftp)
R SC data
DQ DQ DNS Query
RMA synch to Account Finder
IMS Common Nodes
AP
(xml/HTTP) Historical Data
M
SCAP, to ADMIN DR/CDR
EMAPv1&2,
SCAPv2/ (XML/http)
MRF MGFC DCCA
LDAP ETSI MAP NQ Number Query to FNR
SCAP, and HLR
DCCA, MML 0..1 R
CAI (if MINSAT)
S-CSCF Multi Mediation
PAMI (if ASCS)
IMSM (barring) Charging System
DBP(A)
CRS Nodes
DCCA, 0..n R
SBG Online 0..n R
EPK/U/TM-01:008 Uen Rev PE31
EM SI M
DBP(A), Certified Nodes
ET
Mediation File & Event Mediation
AP
Radius CC/HLR Data
(On-line Gateway) Change (ftp)
v1& P
Verified Nodes
0..1 NQ
A
Service Provider
v2,
ZELS Same bundle
DQ Nodes still supported
Support Function but not available for
NQ
DCCA, DBP(A), 0..n 1..n new sales
SMS-C
Parlay (Corba),
Parlay X, Radius
EMA MML HLR/HSS Nodes not verified for
Content Delivery 0..n the release
+ other
Support Function FNR
Service Network SMPP
3

Long-Term Evolution WoW
Streamline Development is our Vision
continuously improved methodology 2008 goals for all sites
tailored to help us reach our way of - Agile In Full Momentum
working (WoW) vision. - 50% TTM reduction vs. 2005
- 100% Compliance to Level 3 Level N
Each step towards our vision is a well
defined and measurable business
Level of compliance
requirement, and of course reflected in
Streamline Development Level …
Enhanced Streamline is an
improvement program with
the objective to get
Level 3 – Agile Practices
to Level 3 Leadership Test Iterative Continuous
Driven Learning
Req.
Level 2 – Core Loop Test
Modeling Quality Automation Traceability Unified
Toolbox Build
Level 1 – Formal Process Create
PLCM Sell
Self-Organizing Latest Prioritization Anatomies Pull Commitments Manage
Small Teams System Version of Requirements Releases
2005 2008 Future Time
4

Tools : How do they relate to each other?
Lean Fork
Knife
Agile Toothpick
Scrum
Kanban
XP
Let’s just say !?
These are all tools!
Henrik Kniberg
5

Beware of comparing tools
There is no such thing as
a good or bad tool
Any tool can be misused
The old
tool
was
better!
6

Tools must be combined.
No single tool is complete.
Prescriptive vs Adaptive tools Compare tools for
understanding, not for
judgement.
More prescriptive More adaptive
RUP XP Scrum Kanban Do Whatever
(120+) (13) (9) (3) (0)
• Architecture Reviewer • Business use case realization
• Business Designer • Business use-case model • Whole team • Scrum Master • Visualize the workflow
• Business-Model Reviewer • Business vision • Coding standard • Product Owner • Limit WIP
• Business-Process Analyst • Change request • TDD • Team • Measure and optimize lead time
• Capsule Designer • Configuration audit findings • Collective ownership • Sprint planning meeting
• Change Control Manager • Configuration management plan • Customer tests • Daily Scrum
• Code Reviewer • Data model • Pair programming • Sprint review
• Configuration Manager • Deployment model • Refactoring • Product backlogt
• Course Developer • Deployment plan • Planning game • Sprint backlog
• Database Designer • Design guidelines • Continuous integration • BUrndown chart
• Deployment Manager • Design model • Simple design
• Design Reviewer • Development case • Sustainable pace
• Designer • Development-organization • Metaphor
• Graphic Artist assessment • Small releases
• Implementer • End-user support mateirla
• Integrator • Glossary
• Process Engineer • Implementation model
• Project Manager • Installation artifacts
• Project Reviewer • Integration build plan
• Requirements Reviewer • Issues list
• Requirements Specifier • Iteration assessment
• Software Architect • Iteration plan
• Stakeholder • Manual styleguide
• System Administrator • Programming guidelines
• System Analyst • Quality assurance plan
• Technical Writer • Reference architecture
• Test Analyst • Release notes
• Test Designer • Requirements attributes
• Test Manager • Requirements
• Tester management plan
• Tool Specialist • Review record
• User-Interface Designer • Risk list
• Architectural analysis • Risk management plan
• Assess Viability of architectural • Software architecture
proof-of-concept document
• Capsule design • Software development
• Class design plan
• Construct architectural proof-of- • Software requirements
concept specification
• Database design • Stakeholder requests
• Describe distribution • Status assessment
• Describe the run-time architecture • Supplementary business
• Design test packages and classes specification
• Develop design guidelines • Supplementary specification
• Develop programming guidelines • Target organization assessment
• Identify design elements • Test automation architecture
• Identify design mechanisms • Test cases
• Incorporate design elements • Test environment configuration
• Prioritize use cases • Test evaluation summary
• Review the architecture • Test guidelines
• Review the design • Test ideas list
• Structure the implementation • Test interface specification
model • Test plan
• Subsystem design • Test suite
• Use-case analysis • Tool guidelines
• Use-case design • Training materials
• Analysis model • Use case model
• Architectural proof-of-concept • Use case package
• Bill of materials • Use-case modeling guidelines
• Business architecture document • Use-case realization
• Business case • Use-case storyboard
• Business glossary • User-interface guidelines
Business modeling guidelines User-interface prototype
Henrik Kniberg
• •
• Business object model • Vision
• Business rules • Work order
• Business use case • Workload analysis model
7

How we started in R&D India
Agile Ways of Working in Ericsson Introduction
Training based on Scrum for all employees
Use of Ericsson Agile Coach – Marc
We had certain specialized trainings by industry
experts such as Certified Scrum Master Training
A specialized Agile Deployment Team was established
to plan and roll out Agile Ways of Working in R&D India
8

Challenges we faced at Startup
How do we go from heavy documentation to User Stories
Product Owner role within R&D Organization away from Customer
Customer
Market Unit
Product Management
R&D Unit
Global Services
Change in Management mindset, move away from Command and
Control to Coaching
1

Source of Incoming Work into R&D
R&D Team
R&D Requirements R&D PM
Various Decision Forums
CoS Requirements
RRF Handler
ACoS Requirements
DM Responsible
2

Product Backlog Creation
Stakeholders and
R&D Product Owner’s Forum
Requ
ir e m
ents
CoS Req R&D PM
uirem ents
Product
Backlog
Node SM
RRF Handler
Node Program
ements
ACoS Requir Manager
DM Responsible
d LSV Manager
itiate SAT Team
e In ents
Nod irem
u
Req
3

Node Product Backlog (Example)
12

IVR – Agile Setup
IVR-Eagles
Product Owner are SAT team members iteration
for Agile teams Backlog
Stakeholders and
Product Owner’s Forum
IVR-Pillars
iteration
Backlog
Node
Product Node SM
Backlog
R&D PM acts as Product Owners
Product Owner
IVR-Rocks
iteration
Backlog
RRF Handler
NPM
act as
Team Coach
for all Agile teams
DM Responsible LSV Manager
13

IVR – Iteration Plan (Showing Summary Aspects)
14

Learn and Adapt
We did some course correction with learning from retrospectives
and adapted our way forward
– Team re-shuffles to get better synergies and performances
– Get better input into the Agile teams
– Auto-build and auto-test framework (Home made) for daily builds
and test activities
– Improve Self Managing and Self Organizing Agile teams and less
coaching from outside
– Adapted our work environment towards Agile Ways of Working
15

Agile Ways of Working (Status)
Agile Practices which are working well
– Daily Standup
– Iteration Plans and Visualization
– Pre-Planning Game / Planning Game
– Demo
Agile Practices we need to improve
– Retrospective
– Backend : System Verification Team goes Agile
– Front-end : Technical Expert Team goes Agile
– Velocity Measurement
Agile Practices Next Step
– User Story Points estimation in Pre-Planning
– Test Driven Development
– Agile Life Cycle Management Tools Evaluation
16

Our Achievements
In growing organization with new staff (young) fast
learning curve and enjoyable work environment
To the existing organization it becomes very
transparent (who’s doing what)
Empowerment & motivation of staff
Despite all new staff (50%) no drop in output and
quality
17

Steps Towards E2E AGILE
R&D India is E2E AGILE
te ps One Track in Place
eS
A gil LSV part of Development team
dia
Test Driven Development
In SAT Goes Agile
R &D Node System Anatomy in Place
Continuous Integration & Automation
LSV WoW in Place
Agile Practices in Place
18

19