Citizen Portal. Citizen Portal: Vision For Government Agencies Who Want To Promote Civic Engagement;...
-
Upload
colin-carroll -
Category
Documents
-
view
216 -
download
4
Transcript of Citizen Portal. Citizen Portal: Vision For Government Agencies Who Want To Promote Civic Engagement;...
Citizen Portal
Citizen Portal: Vision
For Government Agencies Who Want To Promote Civic Engagement; Citizen Portal will
allow the Agencies to bring all business processes and information online in one place And
provide access to citizens, when, where and how they want.
Unlike Other Products Which Are Completely Canned Citizen Portal will allow The Agencies
To utilize Full Power Of Civic Platform for citizen facing services. This supports our
company strategy of Bringing Trust And Flexibility To Citizen Interaction With Government
And Reinstates Our Belief That Engagement Makes All The Difference.
Citizen Portal: Vision Highlight
Utilize full Power Of Civic Platform for citizen facing services and bring all business processes and information online in one place.- Integrated all Accela/ 3rd party products- turnkey solution- Unified behavior/ look & feel- Single Authentication for citizens- Delivery mechanism – tiered approach- Agency branding – tiered approach
Provide access to citizens, when, where and how they want- Mobility/ device agnostic- Browser agnostic- Responsive/ adaptive design- UX
Citizen Portal: Agency Segments
Broad classification based on Agency budgets:
1. Tier 1 & 2
2. Appetite for custom portal development
3. Use own portal/ UI
4. Enterprise delivery is preferred
1. Tier 3 & below
2. No appetite for custom portal development
3. Accela’s UI/ portal
4. SaaS delivery is preferred
Deductions:
1. One solution may not fit both2. Consider both segments for system design3. Focus on 1 for development & delivery
Citizen Portal: All New Citizen Portal
Proposed Focus Areas:
1. Design for the cloud
2. Decoupled application (can have its own deployment strategy/ release cycle)
3. Find a better balance between customizability and UI/UX control
4. Citizen Portal dictates the UI, not a common AA template that gets strip down. But: Source
of Data/Permissions/Business Logic is still AA.
5. Civic ID integration
6. Use AA REST (new architecture)
7. If successful, the product becomes a SaaS offering and existing ACA becomes an ACA
Enterprise. Both products coexist, for different customers ACA is there if you need total
control or customization.
Citizen Portal: All New Citizen Portal
Proposed Components:1. Home Page
• Centered around discovery• Customizable via predefined widgets/tiles. The page has hooks to include widgets • An API makes it possible to include custom widgets outside the AA/ACA release cycle
2. The app acts as a host of micro apps. These apps:• Handle in-take forms and display of record details• Handle exposing a presentation screen to be included as a widget/tile in the front
page• Have access to an authentication method (isRegistered or hasPermissions) that
allows for UI control but permissions live in AA3. A User dashboard
• “My Applications” / Applications Pending / Notifications4. A common UI framework
• UI Framework provides consistent look and feel across apps• It provides a framework for micro apps.
• For example. A PageFlowController that handles navigation in your forms
Citizen Portal: All New Citizen Portal - MVP
Proposed MVP Scope:
1. What: A prototype that has:
• a customizable home page
• 1 app that can demonstrate functionality end-to-end (intake forms and display its
data)
• user dashboard.
2. When: User’s Conference/Summer(?)
3. Needs: Eng/UX resources/ Cross team dependency
Citizen Portal: Execution Approach
• Longer term vision for citizen portal to be flexible and scalable
• Read and Post data from all Accela and 3rd products
• Development team focus areas and room for innovation
CBX• Productize electric orange
approach for UI• Responsive pages?• Customer Commitments• Bug fixes/ defects
CB1
Hold the market!- User Interface theme for 8.0 release- Ongoing Customer Commitments, Fixes/ Defects - Do we need responsive design in 8.0?
Execution Approach:- 2 development tracks for Citizen Portal- CB1 (7.3.3.0 – Intermediate release in Jan 2015)- CBX (the zing thing) – revolutionize the citizen portal
Build a Great product!- Longer term vision for citizen portal to be flexible and scalable- Development team focus areas and room for innovation- SaaS
Necessary Considerations
Citizen Portal: Approach
• Use this development track to revolutionize the Citizen Portal
• Onsite/ offshore team for better coordination during iterations
• Accela engage 2015 – MVP (Internal) release• Decision Points• Fix Stuff and release all new Citizen Portal
CBX
• Use this development track to continue supporting our existing Citizen Portal customers.
• Offshore team works on this• Work on existing code base• Avoid major feature
enhancements
CB1W
ork
Tac
tics
Mile
sto
ne
s
MVP• Release CBX MVP for internal audience• Monitor CBX progress; consider releasing MVP
before Accela engage 2015
GA• Initially targeted for new customers• Identify breaks/ expectation gaps• Fill gaps/ merge with CB1 feature set• Release all new/ revolutionized Citizen Portal –
iterate and release
CBX
8.0• Electric orange• Customer Commitments• Bug fixes
8.1• Customer Commitments• Bug fixes
CB1
Citizen Portal: Agile Dev Roadmap for 2015
CBX
CB1
8.0
GA
8.1
GA
MVPGA
• Feedback loop with Internal Audience
• Customer Success• Sales – SCs/ COE• Customer Support• Professional
Services• Advisory Board/
Champs• Validate MVP and make
post MVP decision
MVPInt
Re-skin Intake formsCustomer CommitmentsProduct Enhancements
Bug fixes
StartHere
8.x
GA• Fix stuff• Incorporate feedback• Merge CB1 features• Initial release for new
customers• Migration path for
existing customers
Maint
What’s Next?
Release Planning