agile€¦ · growing importance of ux specialist roles build services with our users, not for our...
Post on 18-Jun-2020
0 Views
Preview:
TRANSCRIPT
AgileConsiderations for Government Projects
January 24, 2019
Tony Fortenberry | Director of Education Services
Agile Government Leadership Association CivicActions
● OSI Deputy Director at Child Welfare Digital Services (CWDS)● CTO at Communication Service for the Deaf● CIO at City of Northglenn, Colorado
Introduction - Tony Fortenberry
Agile Considerations for Government Projects
Agile Overview
Agile Considerations for Government Projects
● It takes a village○ Executive, Budget, Oversight, Procurement, Legal, Project, Technical, User
● Embrace digital services culture○ Empowerment, collaboration, product focus
● Build services with our users, not for our users○ Human-centered design, continuous participation
● Small is the new big○ Agile, modular, iterative
● Default to open○ Transparency, shared solutions, free/open source software (FOSS)
5 Lessons
Agile Considerations for Government Projects
● Executive● Budget● Oversight● Procurement● Legal● Project● Technical● User
It takes a village
Agile Considerations for Government Projects
● Signal-noise, detecting patterns in the chaos● Inclusive vs exclusive knowledge (triage)● Effort vs Impact
○ Project manager - manage to a process○ Product manager - manage to an outcome
● Symmetrical vs Asymmetrical communication○ On demand information○ Persistent status○ Transparency
● Modern tools for collaboration○ Simplicity + universal access (Trello) vs complex + limited access (Project)○ Avoid obscuring your data
Embrace digital services culture Empowerment, collaboration, product focus
Agile Considerations for Government Projects
Authority● Firm● Control● Static
Empowerment● Porous● Influence● Collaboration● Agile
Authority vs. Empowerment
Agile Considerations for Government Projects
Empowerment
Authority
New Ideas
Team Input
Corrections
Failure
Opportunity
● Users are poor software designers, but excellent software critics
● Enable continuous user participation● User involvement improves relationship with stakeholders● Agile is not a series of small waterfalls● Growing importance of UX specialist roles
Build services with our users, not for our users
Agile Considerations for Government Projects
CI/CD Pipeline Example
Agile Considerations for Government Projects
● Complexity modeling● Risk management via reducing scope● Working software is the primary measure of progress● Roadmap vs schedule● Capability vs Requirements● Definition of done
Smallify: If it feels like you can’t do something,just make it smaller until you cannot NOT do something.
Small is the new big Agile, modular, iterative
Agile Considerations for Government Projects
1. Understand what people need2. Address the whole experience, from start to finish3. Make it simple and intuitive4. Build the service using agile and iterative practices5. Structure budgets and contracts to support delivery6. Assign one leader and hold that person accountable7. Bring in experienced teams8. Choose a modern technology stack9. Deploy in a flexible hosting environment
10. Automate testing and deployments11. Manage security and privacy through reusable processes12. Use data to drive decisions13. Default to open
https://playbook.cio.gov/
USDS - Digital Services Playbook
Agile Considerations for Government Projects
Design
Delivery
Technology
Transparency
● Work in the open● Open standards technology● Software licensing● Free/Libre software● Store public data in non-proprietary formats
Default to open Transparency, shared solutions, free/open source software (FOSS)
Agile Considerations for Government Projects
The value of openBy emphasizing the use and distribution of open technologies, the California open source policy:
● Champions a civic culture of openness, transparency and accountability● Facilitates statewide technology collaboration● Enhances technology recruitment and talent development opportunities● Decreases redundant technology expenditures● Improves technology security● Eliminates vendor lock-in● Increases public reuse for exponential innovation potential
California Open Source & Code Reuse Policy
Agile Considerations for Government Projects
● Greater opportunity in success○ Perception of scarcity○ Local vs global resources
● The responsibility is greater than the privilege● The function of leadership is to produce more leaders, not more
followers● Public organizations should create public goods
○ Consumers → Creators
● (Digital services) = (Design + Technology + Experience)● Don’t get distracted
Final Glorious Big Some Thoughts
Agile Considerations for Government Projects
Conversation
Tony Fortenberry
Director of Education ServicesCivicActions
+1.916.625.6150 | tony.fortenberry@civicactions.com | civicactions.com | @civicactions
Contact
Agile Considerations for Government Projects
top related