Think of it as the difference between a single-threaded system, and multi-threaded. In other words, instead of every developer working independently on a story, the team focuses on a more limited set of stories/tasks together and get each item done sooner. The core concept is to "quit starting, and start finishing". Swarming, in its simplest form, means that teams work collaboratively on items (stories) and work them to completion. It is not something that is done "when there are problems". Swarming is actually a central concept to agility. "Swarming" is nothing more than a fancy term for "hey, let us help you with that". They got a free lunch, I got work done early that could have dragged on due to it's dull nature, and the team got ahead of their sprint. They got the work done and out of the way early, then each team member went back to whatever they were working on. I gave the team a small incentive (pizza) and deadline (end of the day) to finish the work, so they swarmed on the story and knocked out at least a couple days of work in one afternoon. We recently had a small number of stories that was some fairly boring, uninteresting work. If someone is falling behind, or if there's a desire to finish a task or story early, other people will stop working on other tasks and "swarm" to complete the task, which means they all work together on a single task or story until it is completed. Typically, each member of my team works on a different task and/or different story. In my experience this isn't something you do often. Swarming just refers to the fact that multiple people work together to complete a task or story.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |