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 on estimation #58

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

content on estimation #58

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

Comments

@charleszipp
Copy link
Member

This is for the new proposed outline in #53

This content should guide a new team in how to establish how they will be doing estimation.

  • Agreed scale (i.e. fibonacci)
  • Conversion ration of points in scale back to unit of time (i.e. 1 point = 1 day for 1 contributor)
  • Establishing baseline stories (i.e. pick story that represents a 5 and one that represents 2 if using fibonacci)
@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

Content on Estimation best practices to be added here: https://github.com/microsoft/code-with-engineering-playbook/tree/master/sprint-planning/estimation

@fnocera fnocera changed the title complete conceptual content for team-baselines/estimation content on estimation Jan 16, 2020
@bsherwin bsherwin linked a pull request Feb 20, 2020 that will close this issue
@bsherwin bsherwin moved this from To do to In progress in Engineering Playbook Backlog Feb 26, 2020
@TessFerrandez TessFerrandez moved this from In progress to Needs review in Engineering Playbook Backlog Mar 3, 2020
Engineering Playbook Backlog automation moved this from Needs review to Done Mar 11, 2020
bsherwin added a commit that referenced this issue Mar 11, 2020
* Added content for estimation in planning
* Added comments about durable teams.
* addressing comments for tools and remote teams
* added space after commas

Co-authored-by: Brian Sherwin <Brian.Sherwin@microsoft.com>
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.

2 participants