Timeline for What is "swarming"?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 12, 2017 at 4:40 | comment | added | Erik Reppen | @RobertHarvey It's more the needing to have a single source of thinking-holistically. | |
| Oct 11, 2017 at 15:19 | comment | added | Robert Harvey | @ErikReppen: Seems like merge conflicts would become a nightmare. | |
| Oct 11, 2017 at 13:48 | history | edited | Oleksi | CC BY-SA 3.0 |
added 1 character in body
|
| Oct 11, 2017 at 0:18 | comment | added | Erik Reppen | I don't recommend this on the front end web. | |
| Jan 2, 2013 at 10:10 | comment | added | Giorgio | @CodeWorks: One problem you can face is that testers cannot begin to test until implementation is finished. | |
| Jan 2, 2013 at 3:41 | history | edited | Jim G. | CC BY-SA 3.0 |
added 4 characters in body
|
| May 10, 2012 at 5:50 | vote | accept | Jay Bazuzi | ||
| May 8, 2012 at 4:14 | comment | added | Matthew Flynn | Ideally, QA is inside the team and capable of assisting in business analysis, design, and/or coding. They're part of the swarm. | |
| May 7, 2012 at 20:46 | history | edited | Oleksi | CC BY-SA 3.0 |
deleted 2 characters in body
|
| May 7, 2012 at 20:36 | comment | added | Oleksi | @CodeWorks, Not at all. In fact, it probably increased it. Because everyone was working so closely together, there were less blockers that surfaced. When something came up, at least someone on the team knew how to solve it, and were able to do so right away since it had their full attention. Also, context-switching is generally bad for your productivity. Just ask you CPU. :P | |
| May 7, 2012 at 20:33 | comment | added | CodeART | Did it have a negative impact on a throughput of your team? | |
| May 7, 2012 at 20:33 | comment | added | Oleksi | @JayBazuzi Yeah, pretty much. Having full-team support is also important though. | |
| May 7, 2012 at 20:32 | comment | added | Oleksi | @CodeWorks Yes. We have used it where I currently work to some success. It's a pretty fun way to develop, because it's feature oriented. Everyone is working towards the same goal at the same time, so I found that it fosters teamwork really well. | |
| May 7, 2012 at 20:31 | comment | added | Jay Bazuzi | Another way of saying it is "have as few works-in-progress as possible", right? | |
| May 7, 2012 at 20:29 | comment | added | CodeART | +1. Interesting. Have you seen this work in practice? | |
| May 7, 2012 at 20:21 | history | answered | Oleksi | CC BY-SA 3.0 |