From Black Box to Open Book: Transitioning to Open Solutions Government Can Control
Speaker: Sean Lehane
Join us, and dive deep on the most relevant challenges and lessons-learned facing a digital transformation from proprietary-to-open. You are sure to come away with some tips that will aid you in planning for and keeping your large-scale and mission-critical projects on track. Some highlights include:
1. Establishing and maintaining trust, accountability, and a teamwork-oriented relationship between a government organization and their technical partners
2. Dealing with urgency in the context of government bureaucracy
3. Evaluating and selecting open source alternatives
4. Identifying and promoting the key benefits of open source to government clients
5. Balancing reliability with innovation in replacing a utility-grade component without end users noticing a difference
6. Working agilely within a waterfall contract structure
7. Ensuring compliance with established and emergent requirements
8. Keeping on-track and on-task among a flurry of conflicting priorities
We’ll provide real world examples from a recent project with the Metropolitan Transport Commission: 511.org shares transportation information with over 7.7 million residents and visitors of the San Francisco Bay Area. It was relying on an increasingly unstable and unmaintainable proprietary system for gathering upstream data. It failed regularly, causing major, costly outages. All stakeholder groups were negatively impacted. This is the story of how to successfully replace such a legacy application with a maintainable, expandable open source platform that can adapt in real time with the fast-changing needs of stakeholders of all kinds.
This session will be useful to you if you are considering, or in the midst of a technological transformation or a partnership between a government agency and technical partner. No matter your role, we think you’ll come away with some immediately useful tips to apply to your circumstance.
Join us, and dive deep on the most relevant challenges and lessons-learned facing a digital transformation from proprietary-to-open. You are sure to come away with some tips that will aid you in planning for and keeping your large-scale and mission-critical projects on track. Some highlights include:
1. Establishing and maintaining trust, accountability, and a teamwork-oriented relationship between a government organization and their technical partners
2. Dealing with urgency in the context of government bureaucracy
3. Evaluating and selecting open source alternatives
4. Identifying and promoting the key benefits of open source to government clients
5. Balancing reliability with innovation in replacing a utility-grade component without end users noticing a difference
6. Working agilely within a waterfall contract structure
7. Ensuring compliance with established and emergent requirements
8. Keeping on-track and on-task among a flurry of conflicting priorities
We’ll provide real world examples from a recent project with the Metropolitan Transport Commission: 511.org shares transportation information with over 7.7 million residents and visitors of the San Francisco Bay Area. It was relying on an increasingly unstable and unmaintainable proprietary system for gathering upstream data. It failed regularly, causing major, costly outages. All stakeholder groups were negatively impacted. This is the story of how to successfully replace such a legacy application with a maintainable, expandable open source platform that can adapt in real time with the fast-changing needs of stakeholders of all kinds.
This session will be useful to you if you are considering, or in the midst of a technological transformation or a partnership between a government agency and technical partner. No matter your role, we think you’ll come away with some immediately useful tips to apply to your circumstance.