Frequently asked questions about our internal Scrum process:
| 1. | Q | When is a buddy testing task considered complete? |
| A | Buddy testing tasks are not complete until any bugs found have been confirmed closed. If you have completed a round of buddy testing and found bugs, you should move your buddy testing task to the "Blocked" column, and adjust the hours remaining to reflect the time you think it will take to complete additional passes, and to close out the bugs you've filed. | |
| 2. | Q | When is a feature/story considered complete? |
| A | A story is not complete until any bugs that would prevent release have been closed out. | |
| 3. | Q | Where do I add additional stories for future sprints? |
| A | New items should be added to the Product Backlog, and ordered appropriately in relation to other stories for the same contract. The Product Backlog is for internal LabKey use only; please contact us with any questions about upcoming features. |
|
| 4. | Q | How can I find a list of stories completed in previous sprints? |
| A | A list of completed items can be found in the "Completed Items" worksheet of the Product Backlog. The Product Backlog is for internal LabKey use only; please contact us with any questions about completed features. |
|
| 5. | Q | When should the "Sprint" field be used? |
| A | Normal sprints: During a sprint, any bugs found in the course of testing one of that sprint's commitments that would block release should be marked with the number of that sprint. Stabilization sprint: Currently, the last sprint in a release cycle is primarily used for stabilization. Bugs should be flagged with the number of the stabilization sprint when a developer has committed to fixing the issue before the release is completed. |
|
| 6. | Q | How are Deliver / Accept & Reject / Deploy used? |
| A | Here is the progression:
|
| previousnext |
| expand allcollapse all |
