Open helayoty opened 3 years ago
A good user story should be (I-N-V-E-S-T principle)
*As a cobalt user, I'd like Cobalt to support the new terraform version 0.14, in order to be able to use the new terraform functionality
Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)
Also, here are a few points that need to be addressed:
Technical Design Document Mockups
Stories are intended to be completed in a single sprint; if task breakdown creates additional work then the team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)
Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)
Assignee should break down work into tasks here
A good user story should be (I-N-V-E-S-T principle)
Description
*As a cobalt user, I'd like Cobalt to support the new terraform version 0.14, in order to be able to use the new terraform functionality
Acceptance Criteria
Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)
Also, here are a few points that need to be addressed:
Resources
Technical Design Document Mockups
Tasks
Stories are intended to be completed in a single sprint; if task breakdown creates additional work then the team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)
Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)
Assignee should break down work into tasks here