Working with Civic Studio

Your point of contact is Ryan Wold.

• Project scoping & Initial Kickoff · a 2-4 hour meeting between the Civic Studio Principal and Delivery Team, and the Client's assigned Point of Contact and Delivery Team.
• Establish Continuous Integration - Part 1 · Ensure Developers have ability to code a change, commit it, run automated tests against the product, and deploy the code to a Staging environment.
• Continuous Integration - Part 2 · Ensure the ability to reliably deploy a build to both Staging and Production environments. Sometimes a `Demo` environment is also created and maintained. Sometimes each developer has their own instance as well.
• Support · Potential extended engagement, based on how we're working together and how much value we're delivering.
• Handoff · Transition work and operations from Civic Studio to the client organization or team.

We'll be building software together. We want you and your users click through it — to use it!

Working cadence

• Civic Studio staff work a specified number or hours per week (up to 40).
• Up to 4 core hours can be specified on days when staff is working. Often 2 hours overlap is sufficient to keep forward momentum.
• Staff work location is considered to be remote, unless otherwise specified.

Formal work rituals

• 30 minutes - Weekly Project check-in - between Civic Studio Principal and Client Point of Contact
• 30 minute Product Review - every other week. Typically Fridays. Product Team demos the product, openly.
• 1 hour sprint retro - every other week. Typically, shortly after Product Review. Just the working team, unless the team requests other participants.
• Communicate via Slack - daily
• Communicate via Email - less

General Pricing

Description	Duration	Time	Cost Estimate
Quick call and consult	1 hour	Hourly	$150
Prototyping	1-160 hours	1-4 weeks	$45,000
Systems Development & Consulting	160–720 hours	1-6 months	$45,000 – $108,000

Estimated Total Time: 2-4 weeks for a basic prototype with CI, 3 months+ for additional iterations to build features based on feedback

Deliverables are based on time & labor. The pace of software development varies because software is custom and not necessarily a commodity.

Additional features are estimated on a User Story basis.

Common software features include:

• Log in / Authorization
• Profile management
• Image upload
• Data exports
• Manage records - List records in a database table (pages and forms to Create, Read, Update, Delete)
• Visual Charts
• API calls

Supporting Web services

• Web hosting
• Domain registration and management
• Email hosting and configuration

Purus morbi dignissim senectus mattis adipiscing. Amet, massa quam varius orci dapibus volutpat cras. In amet eu ridiculus leo sodales cursus tristique. Tincidunt sed tempus ut viverra ridiculus non molestie. Gravida quis fringilla amet eget dui tempor dignissim. Facilisis auctor venenatis varius nunc, congue erat ac. Cras fermentum convallis quam.

Working assumptions

• Custom software is like a garden, in that it needs intention and continuing attention.
• Software is never done.
• Assume good intentions.
• Work in the open - open source repositories, shared channels where possible. Limit silos. Reduce temporarl coordination costs.
• Be aware when documents are used for force and when personal interactions would build trust.
• Do what works. Do the right thing. Be kind.

Other services offered

• General consulting around digital strategy and operations.
• Design Research - conduct structured User Interviews with intended and potential users.
• Rapid Prototyping - a sketch visual of the screens, elements, and workflow (relationship between pages) - to get a better sense of what a full product build may entail. These are like an architect's sketch rendering, rather than a blueprint.