Timeline for Where does Scrum or Agile Manifesto say that we should avoid stages (development, then testing)?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2021 at 13:34 | history | edited | Sarov | CC BY-SA 4.0 |
added 4 characters in body
|
| Aug 9, 2021 at 9:30 | comment | added | Erik | @Lolums the difference is you can't say "it's in testing, so it's no longer my problem, and it's their fault if we don't make the sprint". Sort of like "make sure they are in the same team" but re-emphasising that even if they are in the same team, make really sure they are in the same team. | |
| Aug 8, 2021 at 20:08 | comment | added | Lucien |
...Meaning devs and testers are not to be treated as distinctly different entities. You don't have 2 devs and 2 testers. You have 4 Development Team members, whom have different specialties. What's the difference?
|
|
| Aug 7, 2021 at 6:18 | comment | added | Frank Hopkins | "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation." logically says nothing about how the information transfer is structured. A meeting is a face-to face conversation. This quote does not imply anything ongoing. (Yes, it is in the agile spirit to not leave open issues unanswered, but if you have phases and hand-overs that doesn't mean you cannot talk in addition when issues arise - you should easily trigger that at the daily for instance.A feature can still be in testing phase and therefore in QA responsibility) | |
| Aug 6, 2021 at 13:53 | history | edited | Sarov | CC BY-SA 4.0 |
added 232 characters in body
|
| Aug 6, 2021 at 13:47 | history | answered | Sarov | CC BY-SA 4.0 |