-
Notifications
You must be signed in to change notification settings - Fork 98
Best Practices
What are the data.gov best practices?
This usually involves research, asking internal/external team members questions, and evaluating approaches. This can be specific (looking at available open source tools for data catalog/data warehouse) or general (we need to know how to best handle security and what options are available to us at GSA)
This usually involves a document of some sort, defining exactly the outcomes that need to be achieved. This is true for epics and for user stories, which is why our "defining" of what an acceptance criteria will look like doesn't mean that the ticket is well scoped.
This is the "sketch" part of a current ticket, picking a design and sketching it out. This may involve pseudo code, a diagram, and may involve prototyping to prove a path forward is viable
Exactly what you think, actually code/config/create the solution, bring it to life
This may involve release process, PR review, and any manual steps to make it a reality. Also may involve outreach and/or documentation.
The ongoing support for, documentation updates, security updates, tweaks, etc necessary for a code or feature to continue.