Adaptive accompaniment Agile & Big Data

1. Adaptive Accompaniment –
Agile and Big data
IFFAT MALIHA

2. Context and Key drivers to attend this
session..
 IT complexity is increasing rapidly with more distributed services, multi-components, more multipart…
 Multifaceted technology environment, multi vendors, are common nowadays to address complex business
problems…
 No single thread application development and servicing are feasible to address such specialties any more…
 One such special scenario is embracing Agile in Big data domain..
 Rapidly growing IT complexity imposes challenges to enable adoption of agile holistically
 However, it is still possible to acquire desired agile benefits in such scenario and this session will enable the
audience with the “how”..
Internal Only

3. Key takeaways..
 Audience will understand the agile nuances in Big data analytics domain
 How to structure your agile transformation journey
 Key agile coaching aspect to increase agile fluency being in such domain
Sticking to agile
values
and principles
Towards
desired
benefits….
with conscious and
contextual
adjustments
Philosophy
Internal Only

4. Business and Technology Landscape
 Compliance and regulatory requirements
for risk management and crime
prevention through KYC, financial
intelligence
 Data acquisition, storage, consolidation
 Data readiness, business insights and
innovation
 Data acquisition in hadoop data clusters
 Data processing by tools like Abinitio,
Informatica
 Data storage in Impala, Hue database on
Hadoop
 Spark SQL queries for data validation, view,
consolidation
Business Technology
Internal Only

5. Common Challenges
 Ingraining right agile behavior to realize the crux of agile values and principles, that
apparently seems impossible to adapt
 Cycle time gets negatively impacted due to inclusion of regulatory review / sign-off,
approval
 External dependency leads to increased difference in planned vs. actual to a major
extent
 DevOps tool adoption with end to end CI-CD implementation is not straight forward,
needs customized solution
Internal Only
CI: Continuous Integration
CD: Continuous Delivery

6. Agile adaptation under Disciplined Agile Delivery
umbrella
Information
Security
Enterprise risk
management
Info Classification &
Handling
Vulnerabilities
& Intrusions
Operational
stability
Data
Governance
Governance&Controls
Internal Only

7. Agile Differentiators ingrained through
coaching
• Disciplined Agile Delivery
• Product vs. Project approach
• Scrum for “Construction” cycles
• Logical grouping
• Slicing strategy
• Technical spikes
• Split stories and
segregate dependency
• Identify and prioritize risk
stories through stakeholder
collaboration
• Exploratory testing instead of
UAT
• Continuous database refactoring
Execution
User story
Estimation
Risk
handling
Testing &
Refactoring
• Build and deployment
• Post deployment env. setup
• Regression tests
Automation
Internal Only

8. Transformation journey
• Solution in live
• Deep automation
• Metrics analysis
• Operations team engaged and
feedback loop established
• Cross-functional team
• Work visualisation
• Metrics capturing
• CI and automation start
• Team formed
• PO available
• Automation planned
• Metrics planned
• Operations rep identified
Level 1
Level 2
Level 3
Level 4
Note: Each level should satisfy the previous level criteria along with the criteria for that level
• Incremental value
delivery with quality
• Reduced production
incidents
• Better operational
stability
• Reduced service
downtime
• ..........
Benefits
Powered by
• Continuous Improvement based on level
3 criteria measured and tracked
• Reflected in measurable outcome
Internal Only

9. Do’s and don'ts for smooth adoption and
sustenance
 Start with story mapping based on business
goals / roadmap
 Update Release plan regularly in collaboration
between Product Owner and Team Lead based
on the construction iteration progress
 Vertical slicing of user stories based on data
clusters in “Extract” layer and “Analytics” layer
 Exploratory testing by Product Owner in
collaboration with Business Analysts
 Delayed revision of release plan
 Incomplete “Definition of Ready” for the user
stories and pulling them for work
 Improper completion of “Inception” stage mainly
with respect to infrastructure readiness
 Product Owner rarely represent the entire
stakeholder community
 Late involvement with control stakeholders
Internal Only

10. Catalysts to accelerate adoption
towards reaping benefits
Product
Owner’s
voice ..
 “DevOps Tiger Team” forum globally to cross pollinate knowledge and solutioning in such varied
technology landscape under the guidance of Agile coaches and DevOps tool lead
 A separate Kanban board on automation related backlog items is in use to keep focus on automation
progress and address blockers effectively
 Culture of sharing common challenges and their way outs, share experiences and learning‘s
 Disciplined usage of ALM tool streamlined end to end workflow
 Improved team collaboration - has helped enrich core team relationship as one team by working closer
together
 Improved alignment with business need / priority with visibility and end to end traceability
 Monitoring work progress daily as a team reflects good work everyone is doing within the team, in turn
improving team morale
Internal Only

11. Q and A
iffat.maliha@gmail.com