XXXXX Technical Redesign – Don Krapohl, 2012 Don Krapohl Strategic Architect XXXXXXXXXXXXX Intelligence Solutions Division
XXXXX Technical Redesign – Don Krapohl, 2012
Don Krapohl Strategic Architect XXXXXXXXXXXXX Intelligence Solutions Division
XXXXX Technical Redesign – Don Krapohl, 2012
Introduction
Value Proposition
System Architecture
Execution Strategy
Review
XXXXX Technical Redesign – Don Krapohl, 2012
Customer – Military Customer’s Enterprise
400,000 active users
Worldwide distribution
Context No vendor support for technology
Increasingly secure workstations
Command relocating
Inability to gain consensus
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
Solve The Current Problem Only address actual technical risk
Position the Customer Design for change
Decouple data from application
Optimize existing licensing
Select for commodity technical skills
Create Value Deliver earned value continuously
$5M, 1.5 year execution
Solve The Current Problem Total rewrite
Position the Customer Use service-oriented architecture
Create Value 1-2 massive releases
$10-12M, 3.5-5 year execution
Our Proposal Competitor Proposals
Agility Capability Value
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
Figure 1- DoDAF AV-1: Business Ecosystem
XXXXX Technical Redesign – Don Krapohl, 2012
Workstations
Locally-attached storage
COM+
COM+
Load Balancer
Static Paths
UI
Web
Tie
rB
usi
nes
s Ti
erD
ata
Tier
Relational Database
Mu
lti-
fun
ctio
nR
end
erin
gTr
ansf
orm
atio
nM
anip
ula
tio
n
Figure 2 – As-is Physical Design
XXXXX Technical Redesign – Don Krapohl, 2012
Only address actual technical risk
Design for change
Decouple data from application
Optimize existing licensing
Select for comm
odity technical skills
Deliver earned value continuously
Database and new features out of scope X X X X X
Perform literal translation of features X X X
Portable and scalable architecture X X X X X
Service-oriented and stateless X X X X X
Provide all current capabilities X X X
Maintain technical quality X X X X X
Produce product in short succession X X
Figure 3 - Summary requirements and business value correlation
XXXXX Technical Redesign – Don Krapohl, 2012
Workstations
Hypervisor
Web servers provisioned on demand
Co
nsu
mer
sW
eb T
ier
Bu
sin
ess
Tier
Dat
a Ti
er
Relational Database
Co
nsu
mer
-n
eutr
alR
end
erin
gTr
ansf
orm
atio
nM
anip
ula
tio
n
MainframesServersSmart Phones
Storage Area Network (SAN)
Storage Area Network (SAN)
Hypervisor
Business servers provisioned on demand
EntityFramework
Figure 4 – Final Physical Design
XXXXX Technical Redesign – Don Krapohl, 2012
Add Remove
UX COM, COM+
Direct database access
Build common presentation framework
Web
SAN attach, virtualize, configure hypervisor
Encapsulate UI in Presenter or View (MVC/MVP)
Business
SAN attach, virtualize, configure hypervisor
Add web services
Consume Enterprise services
Data
Inject entity framework
Figure 5 – Gap Analysis, Generalized
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
4-week offset sprints
Spri
nt
2
Spri
nt
1
Dev.
Design
Week 1 Week 2 Week 3 Week 4
Test & Release
Dev.
Design
Week 3 Week 4 Week 5 Week 6
Test & Release
Figure 6 – Development Lifecycle Relative Temporal View
XXXXX Technical Redesign – Don Krapohl, 2012
Development Process, Generalized
DB
AB
us.
Sv
cs.
Dev
UX
BI D
evB
usi
nes
s A
nal
yst
Test
erR
elea
se
Mgr
PM
Dat
a Sv
cs.
Dev
Ent.
Sv
cs.
Dev
Infr
a.
Engr
.
Scope Sprint
Analyze & Request Artifacts Code Business Logic
Code Business Logic
Write Data Svcs.
Code Enterprise Svcs.
Create Wireframes
Code UI Behaviors
Build Cubes Create Reports
Write Test Scripts
Validate Fitness
Test System
Build Infrastructure
Deploy
Figure 7 – Software Development Process
XXXXX Technical Redesign – Don Krapohl, 2012
Quality
Mean +5.0% Tier II incident increase at 7 days post-deployment Previous major release tier III ticket count at 7 days was 1000/day.
Mean +1.0% Tier III incident increase at 7 days post-deployment
Performance Mean cost/schedule variance 1.0 at closure
Acceptance Customer accepted all product on schedule
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
Situation Imminent catastrophic failure, customer immobile
Need Limited technology refresh
Technical Solution Scalable infrastructure and software design
Design for change, assume impermanence
Execution Strategy “Right” scope, agile organization, agile methods, flexible design
Outcome Project completed successfully
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
HR Resource Mgt. Training
Mobilization Ledge Maintenance Training Maintenance
Personnel Actions GAAP ledger Physical Fitness Training
Personnel Orders Ledger Reports Common Task Training
Personnel Records Maintenance RFO Weapon Qualification
Personnel Reports RFO Approvals (& Automated Order Writer) Training Calendar
Position Management Accounting Archival and Retrieval Commanders Training Assessment (CTA)
Retirement Point Accounting Civilian Maintenance
Strength Management Financial Data Export
HQ Administration RM Reports
Standard Financial System
Tour History
RSC/DRC Fund Administer
Support Table Maintenance
Figure 8 – Summarized Business Processes Redesigned
XXXXX Technical Redesign – Don Krapohl, 2012
XXXXX Technical Redesign – Don Krapohl, 2012
Sco
pe
spri
nt
An
alyz
e &
req
ues
t ar
tifa
cts
Co
de
bu
sin
ess
logi
c
Mo
dif
y d
atab
ase
Wri
te d
ata
serv
ices
Co
de
ente
rpri
se s
ervi
ces
Cre
ate
UI w
iref
ram
es
Co
de
UI b
ehav
iors
Bu
ild c
ub
es
Cre
ate
fixe
d-d
esig
n r
epo
rts
Wri
te t
est
scri
pts
Val
idat
e fi
tnes
s
Test
sys
tem
(u
nit
, in
t., r
eg.,
load
)
Pro
vid
e in
fras
tru
ctu
re
Dep
loy
pro
du
cts
Group Role 1 2 3 4 5 6 7 8 9 10
11
12
13
14
15
PM PM A I I I C R
Dev Bus. Svcs. Dev C A A I I C R A C R C C I
DBA C C A R C R C I C R
Data Svcs. Dev. C C C A I
Ent. Svcs. Dev. C C C R A C C
UX Dev. C C A C C C I
BI Dev. C C C A A R C C C C
Quality Bus. Analyst C C R C C R C A R I
Tester C A I A I
Support Infra. Engr. C C C C A R
Release Mgr. C R A
A Accountable - This role is the single role that must turn over the deliverable
R Responsible - An active contributor, usually providing a supporting artifact
C Consulted - Individuals with expert domain knowledge consulted for feedback
I Informed - Receives formal notice of the activity
Figure 9 – Responsibilities and Roles Correlated
XXXXX Technical Redesign – Don Krapohl, 2012
Step Activity Accountable Role Deliverable Completed By Completion Date
1 Scope sprint PM Schedule
WBS
Seed assignments
2 Analyze & request artifacts Bus. Svcs. Dev. TFS work queues
3 Code business logic Bus. Svcs. Dev. Middle-tier services
4 Modify database DBA DB mod scripts
5 Write data services Data Svcs. Dev. Strongly-typed service
6 Code enterprise services Ent. Svcs. Dev. Enterprise service
Updated service catalog
7 Create UI wireframes UX Dev. UI wireframe
8 Code UI behaviors Data Svcs. Dev. javascript and code behinds
9 Build cubes BI Dev. Dimensions and cubes
10 Create fixed-design reports BI Dev. Reports
11 Write test scripts Tester Test scripts
12 Validate fitness Bus. Analyst Signature on test script
13 Test system (unit, int., reg., load) Tester Executed test scripts
14 Provide infrastructure Infra. Engr. Servers, network, HVAC
15 Deploy products Release Mgr. Completed production change request
Figure 10 – Activity and Deliverables Correlated
XXXXX Technical Redesign – Don Krapohl, 2012
Figure 11 – PMBOK, SDLC, and ITIL Methodologies Correlated