Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OKR4-2: Document MVP Requirements for website projects #30

Closed
Tracked by #73
celestehorgan opened this issue Jul 20, 2021 · 0 comments · Fixed by #84
Closed
Tracked by #73

OKR4-2: Document MVP Requirements for website projects #30

celestehorgan opened this issue Jul 20, 2021 · 0 comments · Fixed by #84
Assignees

Comments

@celestehorgan
Copy link
Contributor

Problem: When we get requests for website help, we don't have a solid "definition of done", so team members tend to get wrapped up in many-months cycles with projects and handoff takes time.

Proposed solution: Create a document in this repo that specifies what a "complete" website looks like at different stages of project maturity. Provide examples based on existing projects. When new projects come in, evaluate against this definition of done.

@celestehorgan celestehorgan self-assigned this Jul 20, 2021
@celestehorgan celestehorgan changed the title OKR1-1: Scope all incoming website projects against MVP requirements OKR4-2: Document MVP Requirements for website projects Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants