| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
1 | Priority | User story | Status | Story Points | In Sprint | Done when: | Acceptance criteria |
2 | |||||||
3 | Done | Create UI-mockups | Accepted by Customer | 5 | Sprint 0 | every Scrum-team member creates at least one UI-sketch | |
4 | Brainstroming of UI-sketches | ||||||
5 | Provide a few more trimmed proposals (remember reasoning of the selected / not selected proposals) | ||||||
6 | Select the Scrum-team proposal | ||||||
7 | Done | As a user, I can create a rule with a name | Accepted by Customer | 4 | Sprint 1 | User can create a new rule | |
8 | Rule is saved to database | ||||||
9 | System gives a infomessage about success / failure | ||||||
10 | Done | As a user, I can delete a rule with a name | Accepted by Customer | 2 | Sprint 1 | User can delete a single rule | |
11 | System asks confirmation about operation | ||||||
12 | System gives a infomessage about success /failure | ||||||
13 | Done | As a user, I can edit a rule with a name | Accepted by Customer | 3 | Sprint 1 | User can edit a single rule | |
14 | Changes are saved to database | ||||||
15 | System gives a infomessage about success /failure | ||||||
16 | Done | As a user, I can create a rule with different conditions | Accepted by Customer | 8 | Sprint 2 | User has can form a condition from different parts | |
17 | User can create an rule "if recipient is a coworker and day is a weekday and time is between 9 and 5, then allow access" | ||||||
18 | Rule has to be saved in database | ||||||
19 | |||||||
20 | Done | As a user, I can delete a rule with different conditions | Accepted by Customer | 4 | Sprint 2 | When user clicks the delete button of a rule and confirms the deletion the rule is permanently deleted | |
21 | The rule list is updated and the deleted rule is not shown anymore | ||||||
22 | The systems informs the user of successful deletion | ||||||
23 | Done | As a user, I can edit a rule with different conditions | Accepted by Customer | 6 | Sprint 2 | When user clicks the edit button of a single rule a edit view is opened | |
24 | When user clicks the save button the edited rule is saved | ||||||
25 | When user clicks the cancel button unsaved changes are cancelled | ||||||
26 | Done | As a user, I want the UI to look pretty | Accepted by Customer | 4 | Sprint 2 | UI looks similar to our UI mockups | |
27 | |||||||
28 | |||||||
29 | Done | As a user, I want to see all rules with their conditions | Accepted by Customer | 4 | Sprint 2 | User can see all rules with their conditions | |
30 | All rules and their conditions are shown as text | ||||||
31 | Done | As a user, I can see only my rules | Accepted by Customer | Sprint 2 | User can see only those rules that she/he has created | ||
32 | Users are distinguished by using cookies | ||||||
33 | |||||||
34 | Done | As a user, I can select if rule's conditions allow or deny access to location | Accepted by Customer | 3 | Sprint 3 | Rule edit view has allow/deny selection | |
35 | Allow/deny info on a rule is saved to database | ||||||
36 | Allow/deny info is shown on a single rule on rule list | ||||||
37 | Done | As a user, I can select if any or all conditions have to apply | Accepted by Customer | 3 | Sprint 3 | Rule edit view has any/all selection | |
38 | Any/all info on a rule is saved to database | ||||||
39 | Any/all info is shown on a single rule on rule list | ||||||
40 | Done | As a user, I want an error message if I enter nothing in text boxes in conditions | Accepted by Customer | 5 | Sprint 3 | Error message is shown to user when he's trying to save rule if there's conditions with empty text boxes | |
41 | Rule is not saved to database | ||||||
42 | User stays at the rule edit screen | ||||||
43 | Done | As a user, I want to UI to look like the mockups | Accepted by Customer | 5 | Sprint 3 | Style different UI components to look more like mockups | |
44 | Done | As a user, I want rule names to be unique within rules of a single user | Accepted by Customer | 4 | Sprint 3 | Error message is shown to user if he's trying to save a rule with same name than other his/her rules | |
45 | Rule is not saved to database | ||||||
46 | User stays at the rule edit screen | ||||||
47 | Done | As a user, I want an warning message if I have a rule with same conditions | Accepted by Customer | 6 | Sprint 3 | Warning message is shown to user if he's saving a rule with same conditions and any/all | |
48 | Warning message is shown to user in rule list view if there's rules with same conditions and any/all | ||||||
49 | Done | As a user, I first land to welcome page when accessing the application | Accepted by Customer | 4 | Sprint 3 | Welcome page is shown to user when he enters the application | |
50 | Welcome page has a "continue" button which redirects the user to rule list view | ||||||
51 | Done | As a user, I can click "Done" on rule list view and then get taken to ending page | Accepted by Customer | 5 | Sprint 3 | Rule list view has a "done" button which redirects the user to the ending page | |
52 | When user enters the ending page, he can't see his rules again | ||||||
53 | |||||||
54 | |||||||
55 | Done | As a user, I can select that rule applies if none of it's conditions apply | Accepted by Customer | 1 | Sprint 4 | User can select "none" in the any/all dropdown selection | |
56 | "none" is saved to database | ||||||
57 | Done | As a user, I can't edit my rules after I have clicked done | Accepted by Customer | 3 | Sprint 4 | User has no way to access his/her rules when he has clicked done | |
58 | User is redirected to "done" page when accessing the application after clicking done | ||||||
59 | Database is not accessable for users that have clicked done | ||||||
60 | Done | As a user, I can't save rule if it is a duplicate | Accepted by Customer | 4 | Sprint 4 | When user creates a rule that is duplicate to existing rule, the save button is disabled | |
61 | When user edits a rule in a way that it becomes duplicate to an existing rule, the save button is disabled | ||||||
62 | Error message is shown indicating that rule has become a duplicate | ||||||
63 | Done | As a user, I want the done button to be at the bottom | Accepted by Customer | 1 | Sprint 4 | Done button is in the bottom of the page | |
64 | Done | As a user, I want allow/deny to be taken into account when detecting duplicates | Accepted by Customer | 2 | Sprint 4 | Allow/deny if taken into accound when detecting duplicates | |
65 | Done | As a user, I want the disabled buttons to be more distinguished from active buttons | Accepted by Customer | 1 | Sprint 4 | Disabled buttons look more gray | |
66 | Done | As a user, I have wide selection of different conditions available | Accepted by Customer | 5 | Sprint 4 | Condition parts are added into the system | |
67 | Done | As a user, I want the welcome and goodbye pages to contain helpful text | Accepted by Customer | 1 | Sprint 4 | Welcome and goodbye pages have helpful text | |
68 | Done | As an admin, I want to be able to select the language of the system easily | Accepted by Customer | 5 | Sprint 4 | All texts of the system are localizable | |
69 | Localizations can be edited from a text file | ||||||
70 | Admin can select the current localization of the system | ||||||
71 | Done | As an admin, I can log in | Accepted by Customer | 7 | Sprint 4 | Application has an admin panel | |
72 | If credentials are incorrect, error message is shown | ||||||
73 | If credentials are correct, admin is redirected to admin panel | ||||||
74 | Credentials are asked when entering admin panel | ||||||
75 | Done | As an admin, I can see list of all users that have entered rules to system | Accepted by Customer | 5 | Sprint 4 | Admin can click on a single user on user list | |
76 | Rules of a single user are shown to admin | ||||||
77 | |||||||
78 | Done | As an admin, I can see all rules of a single user | Accepted by Customer | 5 | Sprint 4 | Admin panel has a list of all users that are done with their rules | |
79 | Done | As a user, I want not to able to save rule when it has duplicate conditions within it | Accepted by Customer | 4 | Sprint 5 | Error message is shown when rule has duplicate conditions | |
80 | Save button is disabled when rule has duplicate conditions | ||||||
81 | Done | As a user, I want save button to be disabled until I have changed something in conditions | Accepted by Customer | 1 | Sprint 5 | Change default condition to be something with text box | |
82 | Done | As a developer, I have to get feedback about the application | Accepted by Customer | 4 | Sprint 5 | Feedback from users is stored in the wiki | |
83 | Done | As an admin, I want the application to work flawlessly on top of MySQL | Accepted by Customer | 3 | Sprint 5 | Application is verified to work when using MySQL as a database | |
84 | Done | As a user/developer, I want the application to be polished | Accepted by Customer | 5 | Sprint 5 | Application is polished | |
85 | Done | As a user, I want to create a duplicate of an existing rule | Accepted by Customer | 3 | Sprint 5 | Rule list view has "create duplicate" button next to rules | |
86 | Duplicate of rule is opened in edit view when button is clicked | ||||||
87 | Done | As a user, I want the UI to look like Sameer's "mockup" | Accepted by Customer | 5 | Sprint 6 | "Create a new rule" button is both top and bottom of the rule list | |
88 | "Done"-button is at the bottom and centered horizontally | ||||||
89 | Done | As a user, I want the error messages in edit view to be on separate line | Accepted by Customer | 1 | Sprint 6 | Error message appears at separate line above "Save"-button | |
90 | Done | As an admin, I want a list of wanted features that were not implemented | Accepted by Customer | 3 | Sprint 6 | List of wanted features exists in documentation | |
91 | Done | As a user, I want to be able to specify rule to apply always | Accepted by Customer | 5 | Sprint 6 | User has a way to specify a rule to apply always without creating any conditions | |
92 | Done | As an admin, I want to have installation documentation | Accepted by Customer | 6 | Sprint 6 | Required software is documented | |
93 | Installation procedure to Linux/MySQL system is documented | ||||||
94 | |||||||
95 | Done | As an admin, I want to have administration documentation | Accepted by Customer | 4 | Sprint 6 | Changing and editing application locale is documented | |
96 | Usage of admin panel is documented | ||||||
97 | Editing condition parts is documented | ||||||
98 | Done | As an admin, I want to have architecture documentation | Accepted by Customer | 6 | Sprint 6 | Architecture of the application is documented? | |
99 | Done | As an admin, I want to have testing documentation | Accepted by Customer | 3 | Sprint 6 | ||
100 | Done | As an admin, I want the localization of admin panel to be separate from the user interface | Accepted by Customer | 4 | Sprint 6 | Localization of admin interface is selectable |