Connecting university systems, maximizing API reuse, delivering new mobile experiences, orchestrating cross-departmental functions, and constantly innovating to deliver great student experiences - it's a tough challenge for any university CIO. Join Sidney Fernandez, CIO for the University of South Florida (USF), along with MuleSoft partner Appian, to learn how to take a comprehensive approach to digital transformation to conquer all these challenges. Sidney will share how USF accelerated application development, connected PeopleSoft and other enterprise systems and delivered new mobile-ready solutions with Appian's leading low-code BPM platform and MuleSoft's Anypoint Platform.

1. and Other Stories of AGILE Mobile Development

2. About USF
• The University of South Florida System is a high-impact, global research system dedicated
to student success. The USF System includes three institutions: USF; USF St. Petersburg;
and USF Sarasota-Manatee. The institutions are separately accredited by the Commission
on Colleges of the Southern Association of Colleges and Schools. All institutions have
distinct missions and their own detailed strategic plans. Serving nearly 48,000 students,
the USF System has an annual budget of $1.5 billion and an annual economic impact of
$4.4 billion. USF is a member of the American Athletic Conference.
• USF Health USF Health is the partnership of the University of South Florida Morsani
College of Medicine, the College of Nursing, the College of Public Health, the College of
Pharmacy, the School of Physical Therapy and Rehabilitation Sciences; and the Doctors of
USF Health.

3. OUR STORY BEGINS…
In January 2015…

4. • 100+ small and large projects
• Long list of new requests

5. • 100+ small and large projects
• Long list of new requests
• Burnt out programmers
• Diminishing return (from our clients point of
view)
• Needed new way of delivering ‘apps’

6. …to build
…to use
…to change
works on all devices
scalable & secure
always current
easy + powerful + unified
a single environment
across applications
for agile digital business transformation
What we needed?

7. Works on All Devices

8. SO WE BEGAN OUR JOURNEY
Since August 2015

9. Feature Onboarding of student employee
Problem  Paper driven
 No transparency into process for either student, staff, or faculty
involved
Average time
to complete
6 -15 days (varied based on the physical availability of the signers)
Before moving to Archivum
Student Apt. Request Form

10. Time to
Develop
(MVP)
 8 Weeks
ROI &
Improvement
s
 Reduction in time to
complete processes
 Single source to view
information needed to make
hiring decisions
 Full transparency into
progress of process for all
parties
Archivum
Record
Created
 Student Record (enhanced)
 Staff Record
Systems
Connected
 OASIS, GEMS, FAST,
COPH Student Database
Systems
Sunset
 COPH Student Database
Student Apt. Request Form

11. Feature MCOM Advising Meeting request/scheduling
Problem  Manual coordination
 Multiple planforms used
Average time
to complete
1 week
Before moving to Archivum
Advising Meeting

12. Time to
Develop
(MVP)
 8 weeks
ROI &
Improvemen
ts
 Automated entire process
 Direct view and write into
Outlook Calendar for
students requesting
advising time
 Streamlined process and
technology used
Average
time to
complete
N/A (feature not released yet)
Archivum
Record
Created
 Student Record
Systems
Connected
 Outlook, Health Banner
Systems
Sunset
 N/A
Advising Meeting

13. Feature MCOM 4th Year Lottery
Problem  Paper driven
 No transparency into process for Students and the Registrar
 Significant manual activities
 Available tools did not meet the complex need
 Could not be done with custom dev?
Average time to
complete
3 months
Before moving to Archivum
4th Year Lottery

14. Time to
Develop
 12 weeks
ROI &
Improveme
nts
 Automated entire process
 True randomization of
student selection
 Significant reduction in
time to complete
 90% first choice match
rate
Average
time to
complete
1 month (including time for
student applying)
Archivum
Record
Created
 Student Record
Systems
Connected
 Health Banner
Systems
Sunset
 All manual processes
sunseted
4th Year Lottery

15. 4th Year Lottery

16. Reporting Examples

17. ONE YEAR LATER
from Apps to a Platform

18. Benefits of thinking Platform
• Reusability of data
• Solving multiple business problems at a
time
• Collaborative planning
• Enterprise architecture planning
• Alignment of strategic goals and roadmaps
• Everyone gets ‘something’ each iteration
img source: hongkiat.com

19. Features  Create a Travel request
 Capture and upload bills from a mobile device
 Create an Expense report
 Approve Expense reports
 Create Cash advances
 And many more
Travel features added to the platform
Travel@ USF

20. PeopleSoft driven workflows
Problem  Modifications to baseline PeopleSoft
 Significant delays in travel reimbursement
 Complex UX for travelers and their travel delegates
 No performance reporting and analytics of process and
bottlenecks
Average time
to complete
3 weeks
Before moving to Archivum
Travel @ USF

21. Travel @ USF

22. Travel @ USF

23. Features  Look up basic information on a student
 Look at students graduation indicators
 Capture notes and add notes from Mobile devices
 Open up a case on a student
 Potentially look up travel for the student
 And many more
Student case worker (staff) features added to the platform
Student Case Management @ USF

24. Feature Fully manual process between multiple parties and the student
Problem  No communication between various parties in supporting the
student
 Unclear point of contact for student
 No alignment of strategy to help the student successes
Average time
to complete
Varied (untrackable due to problems stated above)
Before moving to Archivum
Students Case Management @ USF

25. Students Case Management @ USF

26. Students Case Management @ USF

27. Students Case Management @ USF

28. DIGITAL TRANSFORMATION
Needs Cultural and Technology changes to succeed

29. Measurable Goal Driven Delivery
• Big picture planning can be done
• Roadmap vs GPS?
• Impact Mapping (https://www.impactmapping.org/)
• Ensure value of everything delivered

30. What is Minimally Viable?
• Identify a MVP that works for both
Team(s) & Stakeholder(s)
• Take into consideration:
• Team Agile Maturity level
• Realistic deliverables
• Utilize Agile Prioritization Methods
• Story Mapping, Business Value
Pointing, etc
• Differentiate between MVP vs MMP
• Do not build the Bradley!
(Youtube: Pentagon Wars – Bradley Fighting
Vehicle Evolution)

31. Key Reasons Why Agile Fails to Work
• Agile core basics are not taught/executed well
• Team Roles are not clearly defined
• Not enough skilled technical talent
• Not all Scrum Masters/Product Owners are created equal
• Not all projects to team maturity are created equal
• Team Overconfidence
• No organizational buy in from top to bottom/bottom to top
• Organizational big picture goals gets lost in the sprint by sprint deliverables
• Over scoping/Over commitment
• Partner/Vendor/Technology incompability

32. Not All SM/PO/Projects Are Created Equal
• Certifications are easy to obtain, but the soft skills are rare to come by
• There are multiple levels of Scrum Master/Product Owner maturity so
• Train them internally or
• Hire them from industry
• Match the PO/SM skill level and type to Project critical level
• There will be projects that the team is not mature enough in Agile to take on
Do you remember?...
img source: istock

33. CHANGING TECHNOLOGY
Low Code, Mobility, Platform

34. • Reusable Platform approach
• That aids in digital transformation
• Reduce siloed one-off apps
• Enterprise architecture mentality
• Iterative delivery of value
• Build your Lego city piece by piece!
• Speed to value delivery
img source: hongkiat.com
Selecting the right Technology

35. • Reusable Platform approach
• That aids in digital transformation
• Reduce siloed one-off apps
• Enterprise architecture mentality
• Iterative delivery of value
• Build your Lego city piece by piece!
Select the right Technology

36. Practicing Agile = Eternal Learning
OVERCONFIDENCE
© 2017 Gartner, Inc. and/or its affiliates. All rights reserved.

37. Delivering direct Value
• When Agile truly works…
• Happy clients who see value
delivered every two weeks
• Speed to value delivery for
stakeholders
• Laser focus on what’s
valuable vs what’s ‘waste’
• We do not ignore technical
debt
• A happy, unified, motivated
team

38. Market Factors
 Performance
 Care delivery patterns
 Capacity
 Concentration
 Regulatory influence
Questions?
Thank You!
Sidney Fernandes - @sidfernan
Alice Wei - @WeiAwei