To institutionalize Agile practices across the organization across the below domains :-
(E) Enterprise wide Software Development
(T) Tools & Technological landscape
(H) Hardware & Architecture
(N) Non Software Processes
(I) IT Operations & Infrastructure
(C) Cultural changes
Vip Call Girls Noida ➡️ Delhi ➡️ 9999965857 No Advance 24HRS Live
Agile transformation model
1. Agile Transformation –
“ETHNIC” Model
By Ashutosh Bhatawadekar
Enterprise Agile Coach & Transformation Consultant
24th November 2015
1
2. Agile Transformation ETHNIC Model – Statement of Purpose
To help organization transform from a
traditional software development process
to a customized Agile enablement process
To institutionalize Agile practices across
the organization across the below
domains :-
• (E) Enterprise wide Software
Development
• (T) Tools & Technological landscape
• (H) Hardware & Architecture
• (N) Non Software Processes
• (I) IT Operations & Infrastructure
• (C) Cultural changes
These are given an acronym “ETHNIC”
E H N CIT
2
An ethnic group or ethnicity is a category of
people who identify with each other based on
common ancestral, social, cultural or national
experience Source : Wikipedia
The proposed model analyses the existing practices
across the “ETHNIC” domains, then proposes a
transformation roadmap to help organization
achieve agile enablement , agile maturity
Key Assumptions
- Each IT organization exhibits a unique set of ethnicity
patterns and “One Size Does not Fit All”
- Tailor made solutions generally give a better fitment
towards enabling agile across organizations
- Senior Management & leadership buy in exists for the
Transformation Initiative
3. E
3
Enterprise Wide
Software
Methodologies
• Analyze existing
software
development
process
• Requirement
Gathering process
analysis
• Map against
agility parameters
to identify gaps
T
Tools & Technology
Landscape
• Mapping of Tools
with the
requirements
• Tools applicability
analysis
1. Suggest Quick Wins
2. S/W Reengineering
Approach
Document
1. Tools Inventory
List
H
Hardware &
Architecture
• Studying existing
hardware &
network setup
• Understand
Hardware
Provisioning
Process
• Architectural
Envisioning
Process
1. Hardware
Process
Document
2. Architectural
Approach
N
Non Software
Processes
• Interact with
other business
units like HR,
Finance, Admin ,
Quality (SEPG) to
understand
existing org
processes
• Understand the
current SLA’s and
guidelines for
service
provisioning
1. Expectation
Document (Other
BU’s)
I
IT Operations
• Understand the
existing IT Ops
landscape
• Understand the
Data center
operations and
security policies
1. IT Ops Analysis
document
2. Suggest Quick
Wins
C
Cultural Changes
• Understand the
existing org
culture, policies,
HR initiatives,
team motivation
• Analyze the HR
Dimension
towards agility
1. Recommended
soft skills training
2. Inter BU Cross
cultural
awareness
training
Process Steps
• Pilot Projects Selection Guidelines
• Obtain Buy in from Key “ETHNIC”
stakeholders on the Charter
• Pilot Charter Approval & Signoff by Executive
Leadership & Sponsor
• Obtain Pilot Funding from the Executive
Leadership & Sponsor
Initial Wave – Pre Pilot Analysis & Study
• Propose a Tailored Agile Process based on “ETHNIC”
Inputs
• Business Case, Value Drivers & Success criteria
• Finalizing Agile Metrics & Measurement guidelines
• Documenting the Pilot projects execution approach
Pilot Funding
Pilot Program
Charter
3
4. 4
Next Wave – Pilot Execution
Initiate
Release
S1 S2 Sn
Mid
Course
Review
Release
RetrospectiveWorking Software
Release
Demo
Software
Delivery
PMO SEPG IT Ops
Key Pilot Metrics Reported
Every Sprint Level
• Stories Planned vs. Delivered
• Sprint Velocity
• Burndown & Burnup Charts
• Sprint Cumulative Flow Diagram
• Impediments raised vs. Resolved
• Impediments Ageing Report
Key Metrics Reported
Release Level
• Release Burnup & Burndown
Charts
• Business Value Planned vs.
Delivered
• Release Velocity
• Cumulative Flow Diagram
Arch. Product
Key Deliverables
• Pilot Completion Report
• Key Recommendations for ETHNIC
stakeholders to align
• Agile Transformation “Go or No-Go”
Decision
• Documenting Lessons Learnt
Next Steps
• Pilot Validation with the Charter
• Establishing the Organization Agile
Transformation Framework
• Obtain Executive Funding &
Sponsorship for Next Phase
(Transformation)
• Establishment of the Agile Project
Office
• Organization Wide Rollout of the Agile
Transformation Model
SME
Arch.
Lead
PO
Scrum
Master
Release
Manager
Team
R
O
L
E
S
“ETHNIC” Stakeholders
B
A
C
K
L
O
G
Final Report
Pilot
Projects
Program
Dashboard Charter
Validation
Exec
Sponsor
5. Next Wave – Enterprise Wide Transformation
Tools
• Agile Lifecycle
Management
Tools e.g. JIRA,
Rally, IBM RTC
• Build Management
Tools e.g. MS
Build, ANT/Make,
Maven-Hudson,
Cruise Control
• Architecture Tools
e.g. Rational
Software Architect,
Axure for
Wireframe, Adobe
Photoshop
5
Engineering
• Engineering
Practices like TDD
(Test Driven
Development),
ATDD (Acceptance
TDD),
• Code Refactoring
Guidelines
• Continuous
Integration, Build &
Deployment
Product
• Product
Prioritization
Techniques like
MOSCOW, KANO
etc.
• Business Value &
Drivers
• Product Roadmap
• Themes, Epics, &
User Stories
IT Ops
• Service
Virtualization
• Automation Tools
• Data Center
Guidelines &
Maintenance
• Web Services
• Database
Administration
• Infrastructure As a
Service
• Cloud
Transformation Levers
Human
Resources
• Soft Skills
Training
• Servant
Leadership
• Conflict
Management
• Emotional
Intelligence
Key Metrics
Reported
• All Pilot Metrics
– release &
Sprint Level
• Transformation
Coverage
• Cost Savings
• Productivity
Increase
• Business Value
Delivered
• Human
Resources Index
Steady Flow of
Projects Agile Project Office
Project
Delivery
Continuous
Improvement