1 / 20

Automating Government With Quickbase

Automating Government With Quickbase. Chris Willey Interim CTO District of Columbia Government. Quickbase. The Need. Lots of small to mid-size business problems Time to market Little or no budget Normal solution: unmet needs. The Solution. Manageable by business user Cloud-based

elan
Télécharger la présentation

Automating Government With Quickbase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automating GovernmentWith Quickbase Chris Willey Interim CTO District of Columbia Government

  2. Quickbase

  3. The Need • Lots of small to mid-size business problems • Time to market • Little or no budget • Normal solution: unmet needs

  4. The Solution • Manageable by business user • Cloud-based • Secure • Cheap • Not just for “throwaway apps”

  5. Quick Stats • In About 18 Months: • 3,200 active users • 12+ agencies • 225 database applications • 2.3GB of data • 39GB of file attachments • ………all for about $250,000

  6. Quick Stats 2 • $8M+ in savings overall • Majority of apps built by same developer • One example: • 1 day, $0 vs. 30 days, $70k

  7. Rethinking The SDLC • Sub-100% solution viability • Implementation simplicity rules • Hyper-agile

  8. Standard Process • Gather requirements up front working with business users • Technical resources develop code • Technical resources test code with input from business users • Deploy to production, final signoff from business users • Maintenance/bug-fix cycle once application is operational

  9. Problems • Formal development process • Requires strong business need to justify effort and cost • Simple applications may not be worth implementing • Long Cycle Time • Input from Business Process mainly at inception, changes could require restarting process

  10. Co-Development Process • Initial training by OCTO consultants to help determine if this approach is appropriate and best delivery platform • Business users take primary responsibility of developing application • Application is immediately put to work and enhanced as needed • OCTO provides technical development of more complex features as well as guidance and additional training

  11. Co-Dev Advantages • Business Process drives development • Focus is on what is needed to get work done not on technical details • Business users feel empowered & engaged • Less waiting on technical resource availability • No need for formal deployment • Application is immediately useful • Additional features can be added quickly and as needed

  12. What is it used for? • Project/task management • Executive dashboards • Workflow tracking and reporting • Case management • Trouble ticket systems • Employee evaluations • Lots more……..

  13. Inventory Data

  14. Project Data

  15. Financial Data

  16. Dashboards

  17. DCPS: The Problem • Large volume of court cases • Consent decree requirements • High visibility and cost of failure

  18. DCPS: The Solution • Quickbase case management tool

  19. DCPS: The Result • Up and running in 2 weeks • Multi-dimensional view • Maintained by non-technical analyst • More secure & more collaborative

  20. Conclusion

More Related