Slide 1
Slide 1 text
A G I L E & T H E L A R G E
O R G A N I Z AT I O N :
N A YA N H A J R A T WA L A
C O A C H - K C P C S P C S D C S M C J P
N A YA N @ C H I K L I . C O M
T W I T T E R : @ N H A J R A T W
A P E R F E C T M A T C H
A LY S S A R I E D L
D I R E C T O R
D E B T M A N A G E M E N T S E R V I C E S
A LY S S A . R I E D L @ F I S C A L . T R E A S U RY. G O V
Slide 2
Slide 2 text
P E O P L E
P R O B L E M S
• Command & Control
Leadership
• Changing Team
Dynamics
• Siloed Skill Sets
• Shared Operations Staff
Slide 3
Slide 3 text
P R O C E S S
P R O B L E M S
• Long Release Cycles
• Slow Hardware
Procurement
• Technology Review Board
• Security Reviews
• Change Management
Slide 4
Slide 4 text
L O N G R E L E A S E C Y C L E S
P R O C E S S P R O B L E M # 1
Slide 5
Slide 5 text
• 6 months to get a normal, low-risk change into
production due to gates & manual testing, but…
Slide 6
Slide 6 text
Build
Artifacts +
Isolation
Tests
Automated
Acceptance
Tests!
(Cucumber,
Selenium)
Pushbutton
Deploy AWS
Smoke Test
Source
Control
Automated
Security &
Quality
Scans
Pushbutton
Deploy
Internal
Data Center
Smoke Test Production!
Build
Environment!
(Chef)
Slide 7
Slide 7 text
S E T U P F O R
C O N T I N U O U S
D E L I V E RY
• Team Co-location
• Small Features
• Three Amigos (ATDD)
• Continuous Integration
• Pushbutton Deployments
• Automate Everything
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
S L O W H A R D WA R E P R O C U R E M E N T
P R O C E S S P R O B L E M # 2
Slide 12
Slide 12 text
B E F O R E
1. Write business case - 1 day
2. Wait for approval - 1 week
3. Order Server - 1 day
4. Wait for delivery - 1 week
5. Install Server in Rack - 1 week
6. Install Software - 2-3 weeks
Total: 6+ weeks
Slide 13
Slide 13 text
A F T E R
1. Decide I need a server - 5
minutes
2. Log in to AWS and create
server - 5 minutes
3. Wait for server to start (5
minutes)
4. Run Chef Cookbooks (5
minutes - 2 hours)
Total: < 3 hours
Slide 14
Slide 14 text
S T I L L N E E D S
W O R K
• Production deployments
still occurring in internal
data center…
• So new production servers
still have a long lead time
Slide 15
Slide 15 text
T E C H N O L O G Y R E V I E W B O A R D
P R O C E S S P R O B L E M # 3
Slide 16
Slide 16 text
• Become familiar with the process
• Quickly submit any new desired technologies
• If it meets a business need, use it.
• Never deselect technology because it “isn’t on the
list”
Slide 17
Slide 17 text
S E C U R I T Y R E V I E W S
P R O C E S S P R O B L E M # 4
Slide 18
Slide 18 text
B E F O R E
• Code:
• Team level code reviews
• Pre-deployment scans
• DB:
• Manual updates by DBAs
• Server
• Manual updates by SAs
Slide 19
Slide 19 text
A F T E R
• Code:
• Paired Programming
• Scans integrated into CI
• DB:
• Versioning & Automation
(Flyway)
• Server
• Versioning & Automation
(Chef)
Slide 20
Slide 20 text
S T I L L N E E D S
W O R K
• Paired Programming not
occurring 100% of time
• Database replication
causing some issues with
automation
• Internal Data Center has
some manual work to
create servers
Slide 21
Slide 21 text
C H A N G E M A N A G E M E N T
P R O C E S S P R O B L E M # 5
Slide 22
Slide 22 text
• Address root regulations rather than accept standard
practices
• Build process around best & most lightweight tools
possible
Slide 23
Slide 23 text
P E O P L E
P R O B L E M S
• Command & Control
Leadership
• Changing Team
Dynamics
• Siloed Skill Sets
• Shared Operations Staff
Slide 24
Slide 24 text
C O M M A N D & C O N T R O L L E A D E R S H I P
P E O P L E P R O B L E M # 1
Slide 25
Slide 25 text
• Problem: Repeated disappointments lead to lack of
trust in teams to deliver.
• Solution: Demos every 2-3 weeks showing running,
tested, features. No Mockups!
Slide 26
Slide 26 text
• Problem: Desire to build “ilities” framework - security,
configurability, scalability
• Solution: Define specific examples of these in the
context of a feature using the INVEST mnemonic
Slide 27
Slide 27 text
I N V E S T
• I - Independent: is self contained
• N - Negotiable: can be changed until started
• V - Valuable: for the end user
• E - Estimable: have some idea of how big it is
• S - Small: no more than 3 days development effort
• T - Testable: must know whether it works. (automate!)
Slide 28
Slide 28 text
• Problem: Desire to develop a process that can be
dropped in to other teams
• Solution: Continuous education about the core
principles of agile
• http://j.mp/nayan-agile-principles
• https://speakerdeck.com/nhajratw/agile-from-
principles-to-practice
Slide 29
Slide 29 text
I T ’ S A B O U T T H E J O U R N E Y
Slide 30
Slide 30 text
• Problem: Desire to have a fixed scope, fixed date
solution
• Solution:
• Never compromise on quality
• So what has to give?
Slide 31
Slide 31 text
F I X E D D AT E
• Date was arbitrary - based
on vendor contract period,
not business need.
Slide 32
Slide 32 text
F I X E D S C O P E
• Estimation Failure
• WBS does not work for
projects with high
variability.
• https://
www.youtube.com/watch?
feature=player_detailpag
e&v=GiPe1OiKQuk#t=6
• > 2 weeks does not work
Slide 33
Slide 33 text
F E AT U R E S P L I T T I N G
“We need feature X”
X
Slide 34
Slide 34 text
“Which of these smaller
features do we need?”
X1 X2
X3 X4
F E AT U R E S P L I T T I N G
Slide 35
Slide 35 text
“We really only need
feature X1 and X4”
X1
X4
F E AT U R E S P L I T T I N G
Slide 36
Slide 36 text
C H A N G I N G T E A M D Y N A M I C S
P E O P L E P R O B L E M # 2
Slide 37
Slide 37 text
S U P P LY T H E B E S T T O O L S AVA I L A B L E
Slide 38
Slide 38 text
• Involve them in decisions about WHAT needs to be
built
• Ensure they know WHY it needs to be built
• Empower them to decide HOW to build it.
Slide 39
Slide 39 text
S I L O E D S K I L L S E T S
P E O P L E P R O B L E M # 3
Slide 40
Slide 40 text
• Pairing different roles
• ATDD - Three Amigos again
• Ran into problems with organizations outside sphere
of influence
Slide 41
Slide 41 text
S H A R E D O P E R AT I O N S S TA F F
P E O P L E P R O B L E M # 4
Slide 42
Slide 42 text
• Attempted to alleviate work by cross-training others so
backups have sufficient capability
• Root cause of this is the organization’s focus on
maximizing utilization
Slide 43
Slide 43 text
Time In Process
0
75
150
225
300
Utilization
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
:-|
:-)
:-D
:-(
Slide 44
Slide 44 text
A G I L E & T H E V E RY
L A R G E O R G A N I Z AT I O N :
N A YA N H A J R A T WA L A - N A YA N @ C H I K L I . C O M
T W I T T E R : @ N H A J R A T W
K C P C S P C S D C S M C J P
A P E R F E C T M A T C H