-
Notifications
You must be signed in to change notification settings - Fork 25
Team composition
This product is being built by a blended team lead by CMS staff. CMS ultimately owns the product. Fearless and other contracting groups are here to support the goals that CMS outlines.
- Nick Aretakis – executive sponsor, CMS
- Jerome Lee – product owner/manager, CMS
- Caryn Schwartz - SME/team support, Health Management Associates/MeT
- Jenn Downs - UX Design Lead, A1M Solutions
- Akua Amponsah - UX Designer, Fearless
- Tiffany Forkner – Dev Lead, Fearless
- Bill Brooks - DevOps, Fearless
- Nicole Zonnenberg - Full Stack Developer, Fearless
- Tyler Bolt - Frontend Developer, Fearless
- Darren Mirano - Test Engineer, Fearless
- Dio Obijaku - QA, Theta, LLC
- Michael Knoll - Backend Developer, Fearless
- Greg Walker – full stack developer, 18F
- Laura Poncé – UX designer, 18F
- Nikki Lee – product manager, 18F
- Heather Battaglia – front end developer, 18F
- Austin Hernandez – visual designer, 18F
- James Hupp – content designer, 18F
- Jennifer Thibault – visual designer, 18F
- Aviva Oskow, visual designer, 18F
- Ron Bronson, content designer, 18F
- Brendan Sudol, front end developer, 18F
- Nicole Fenton, content designer, 18F
- Meghana Khandekar, UX designer, 18F
- Paul Phillips - full stack developer, Fearless
- Jesse James - Designer, Fearless
- Richard Davis - Backend Developer, Fearless
- Nichole Weems - Scrum master, Fearless
- Sara Ansari - SME/team support, A1M Solutions
The product owners set our vision and goals, help the team get around blockers, and keep the team on course to deliver value.
The product manager helps the product owners set clear goals, navigates internal blockers, and helps the product owners ensure that the team is on course. In many ways, the product owners fill a lot of the traditional product management role and the product manager helps them do that.
The UX designers help define the behavior of the product and shape the use of language in the product in order to make it as understandable, usable, and useful as possible. The design team does primary research, UI and UX explorations, and usability testing, as well as helping inform the strategy of the product.
The developers write the actual code that powers the product. Normally, the front end developer is responsible for building the parts of the website that people directly interact with, while the back end developer works on the machinery under the hood. However, some developers have both front end and back end skills (they are full stack developers), which leads to a less black and white division of labor.
- Team Working Agreement
- Team composition
- Workflows and processes
- Testing and bug filing
- Accessing eAPD
- Active Documentation:
- Sandbox Environment
- Glossary of acronyms
- APDs 101
- Design iterations archive
- MMIS Budget calculations
- HITECH Budget calculations
- Beyond the APD: From Paper to Pixels
- UX principles
- User research process
- Visual styling
- Content guide
- User research findings
- eAPD pilot findings
- User needs
- Developer info
- Development environment
- Coding Standards
- Development deployment
- Infrastructure Architecture
- Code Architecture
- Tech 101
- Authentication
- APD Auto Saving Process
- Resetting an Environment
- Hardware Software List
- Deploying Staging Production Instances Using Scripts
- Terraform 101 for eAPD
- Provisioning Infrastructure with Terraform
- WebSocket basics
- Operations-and-Support-Index
- Single Branch Deployment Strategy
- Ops and Support Overview
- Service Level AOI
- Incident Response Plan
- On-Call Policy
- Infrastructure Contingency Plan
- Updating CloudFront Security Headers
- Requesting and Installing TLS Certificates