Skip to content
Company Our Work
Cloud Migration DevSecOps Product Engineering Interim Tech Leadership Platform Engineering System Reliability Engineering (SRE) High Performance Computing (HPC)
Approach
Connect

Our approach to problem solving

Discovery

Begins with a 2-3 day workshop for engagement leaders and ends with a reference solution architecture and actionable plan for validating the approach in the pilot phase.

1

Business Analysis – Why are we moving to the cloud? How do we measure ROI? What risks and/or challenges need to be acknowledged?

2

Gap Analysis – Inventory current platform architecture, applications, tooling, processes, and expertise. Facilitate the identification and consensus-building of a shared problem-set. Align with business drivers and model ROI.

3

POC Architecture – Create a reference solution architecture that portrays the ideal end-state incorporating the concerns of operational visibility, lifecycle management, and technology providers.  Identify lighthouse application or environment to serve as the initial POC and its success criteria.  Create a backlog that delineates work to complete the POC.

Pilot

The target for POC should represent the most common type of application of the platform, including sensitive data, but is not a foundational dependency of other applications.  The pilot phase should produce not only the architecture but the application lifecycle management tools and processes.

1

Automation – Setup infrastructure-as-code, orchestration, configuration management, artifact management, and continuous integration systems.

2

Application – Automate the deployment of the lighthouse application.

3

Operational Visibility – Setup operational visibility to express component topology in dashboards and alerting.

Roadmap

Reviews or revises the documented platform topology including an inventory of applications and their components and operational requirements.  These are translated to roadmap milestones and are prioritized by risk, value, and effort.

1

Review and revise readiness assessment assumptions as needed.

2

Roadmap – Create an iterative roadmap of phased groups of applications until migration objectives are complete.

3

Staffing Plan – Identify key resources that will be needed for Data, DevOps, Development, CloudOps, Security, and Product Owner roles across organizations.

Migrate

Typical SaaS application migrations range from six months to a year.  (12-24 iterations)

1

Infrastructure – Identify architecture and provision infrastructure.

2

Application – Setup application lifecycle management automation.

3

Data – Migrate data and tune fault tolerance options.

4

Operations – Draft and train on runbooks, test and monitor functionality alerting procedures.

5

Migrate! – Cutover production

Repeat until done

Optimize

Optimization is part of the handoff process for a migrated application.  During this phase, we confirm that the fully migrated application meets all requirements and is easily maintained in the long term.

1

Cost & Utilization – Determine utilization and right-size environment.

2

Capacity – Enable elasticity automation for high traffic or ephemeral activity events.

3

Availability – Diversify geographical presence.  Draft and test disaster recovery and business continuity procedures.

quote background

Please pass along our sincerest thanks to the entire team for everything you have done to mature our systems, and in turn, the federal government. When we began this engagement, we talked about how we had been constantly pushed to put MVPs into production, with no time to go back and iterate. Because of this, the tech debt that we incurred over the years has been significant.

I guess what I’m trying to say is THANK YOU FOR MAKING FUTURE NUNAS SANE. Your work is going to make a lasting impact.

David Maskeroni
Director, Government Services, NUNA