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

content for definition-of-ready #59

Closed
charleszipp opened this issue Jun 20, 2019 · 1 comment · Fixed by #214
Closed

content for definition-of-ready #59

charleszipp opened this issue Jun 20, 2019 · 1 comment · Fixed by #214
Assignees
Labels
agile Agile topic

Comments

@charleszipp
Copy link
Member

This is for the new proposed outline in #53

This content should define the criteria a team should use to determine if a story is ready to pull into a sprint. Example is, team understands the implementation, how to prove work meets acceptance, estimated, etc.

@fnocera fnocera added agile Agile topic and removed agile Agile topic labels Jan 16, 2020
@fnocera fnocera changed the title add conceptual content for team-baselines/definition-of-ready content for definition-of-ready Jan 16, 2020
@fnocera fnocera added the agile Agile topic label Jan 16, 2020
@fnocera fnocera added this to To do in Engineering Playbook Backlog via automation Jan 16, 2020
@fnocera
Copy link
Contributor

fnocera commented Jan 16, 2020

@madossan01 madossan01 moved this from To do to In progress in Engineering Playbook Backlog Mar 10, 2020
@madossan01 madossan01 self-assigned this Mar 10, 2020
@TessFerrandez TessFerrandez linked a pull request Mar 11, 2020 that will close this issue
Engineering Playbook Backlog automation moved this from In progress to Done Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agile Agile topic
Development

Successfully merging a pull request may close this issue.

3 participants