Timeline for What is the way to go to create tasks?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2017 at 12:03 | vote | accept | Bernd Strehl | ||
| S Sep 22, 2015 at 17:06 | history | suggested | Fuhrmanator | CC BY-SA 3.0 |
spelling, added numbering per the feedback in the comments from the OP
|
| Sep 22, 2015 at 14:04 | review | Suggested edits | |||
| S Sep 22, 2015 at 17:06 | |||||
| Sep 18, 2015 at 20:33 | comment | added | WBW | 1 Research, 2 Implementation, 3 Code Quality, 4 QA/Testing. By research I mean figuring out how to implement the story. Implementation is doing the work to meet the business requirements. Code quality tasks are non-functional requirements that align with DoD for the team. Things like refactoring or paying tech debt. QA/Testing is the domain of automated and manual testing to ensure the customer requirements are met. Also covers things like performance and load. | |
| Sep 18, 2015 at 19:51 | comment | added | Fuhrmanator | Couldn't meta-issues be used for user stories? An example of a meta-issue in GitHub is here: github.com/dart-lang/sdk/issues/23454 | |
| Sep 18, 2015 at 19:50 | comment | added | Fuhrmanator |
You said 4 groups of tasks, but it looks like maybe 5? Research Implementation Code Quality QA/Testing -- I think the word Quality is redundant... can you verify?
|
|
| Nov 20, 2014 at 13:14 | comment | added | Bernd Strehl | Since this is not going to be a big enterprise thing, but more like a learning project, I guess it will be no problem to have task and issues in the same system. Maybe I didn't express myself very well: I want to know the best practice to phrase the things we have to do and store them in the Github issue tracker. | |
| Nov 19, 2014 at 21:57 | history | answered | WBW | CC BY-SA 3.0 |