-
Notifications
You must be signed in to change notification settings - Fork 0
User Stories
As a customer, I would like to receive an email anytime the error percentage is over 50%.
Units (story points): 2
Priority: 1
As a customer, I’d like to be able to receive an email anytime anyone uploads any changes.
Units (story points): 1
Priority: 2
As a customer, I would like to be notified of all line numbers that have been changed since the last build.
Units (story points): 100
Priority: 3
Tasks:
- Access strings from the file of the current build
- Access strings from the file of the previous build
- Compare the strings of the current and previous build, and track which match and which do not
As a customer, I’d like to be able to select which projects I want to be notified for and which to put on mute.
Units (story points): 4
Priority: 4
As a customer, I would like to choose whether to send emails to just the relevant developers or everyone involved in the project.
Units (story points): 2
Priority: 5
As a customer, I would like to be able to let the user add an email address to the mailing list.
Units (story points): 4
Priority: 6
As a customer, I would like to be able to remove an user the mailing list.
Units (story points): 5
Priority: 7
As a customer, I would like be able to select a target percentage at which to be notified if my code has errors greater than that percentage.
Units (story points): 8
Priority: 8
As a customer, I would like to be notified which lines of code are causing the error.
Units (story points): 40
Priority: 9
As a customer, I’d like to be able to receive a progress report email at the end of every week.
Units (story points): 13
Priority: 10
As a customer, after someone makes changes to the project, I would like to receive a notification about how much the code coverage changed by from last iteration.
Units (story points): 13
Priority: 11
As a customer, I would like to receive an email congratulating everyone if the code coverage reaches 100%.
Units (story points): 2
Priority: 12
Hours per Unit: 0.5 hours Hours per Week: 20 hours for the team; 5 hours per person
-
Iteration 1: ** Week 1: Name: Error Percentage Over 50 (ID 3) ** Week 2: Name: Changes Made (ID 1) Name: Notifications and Mutes (ID 7)
-
Iteration 2: ** Week 3: Name: Add Email (ID 8) Name: Remove Email (ID 9) ** Week 4: Name: Relevant Developers or All (ID 5) Name: Select Target Percentage (ID 4)
-
Iteration 3: ** Week 5: Name: Lines of Code Causing Error (ID 10) Name: Weekly Progress Report (ID 2) ** Week 6: Name: Line Numbers Changed (ID 11) Name: Code Coverage Percent Change (ID 6) Name: Congratulations Message (ID 12)