|
Size: 3008
Comment:
|
Size: 3013
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| = User needs evaluation = | = Evaluation of user needs = |
| Line 10: | Line 10: |
| Title:: User needs evaluation | Title:: Evaluation of user needs |
| Line 13: | Line 13: |
| State:: Not started | State:: Not started, Confidence D |
| Line 19: | Line 19: |
| Time estimated:: ? infinite iterations. | Time estimated:: 100md |
Evaluation of user needs
- Title
- Evaluation of user needs
- State
- Not started, Confidence D
- Time used
- Time estimated
- 100md
Description
Overall analysis work to begin by reading available documentation from "the Mjølner experience", this should give some insight into the users needs.
Leveraging the user-base as experts that can tell us what they need, stress that anything is possible, and don't worry real people don't ask for P=NP solutions. Users just want a tool that works for their tasks, not for all tasks.
The below image is not only meant as a joke but also as a reminder, most prefer simple and easy.
Sub tasks
| Title | State | Time used | Time estimated | |
| Tasks/34/1/0 | Analysis of existing system and documentation | Not started, Confidence A | 5md | |
| Tasks/34/1/1 | Determine the needs of the users | Not started, Confidence A | 0 | 11md |
| Tasks/34/1/2 | Exposing search results | Not started, Confidence A | 5md | |
| Tasks/34/1/4 | Integration to other systems | Not started, Confidence A | 2.5md |
Documentation
Progress history
| Iteration | Time used | Status | Notes | Tasks adressed |