Timeline for Extreme Programming: how long are iterations supposed to be?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 29, 2015 at 1:58 | comment | added | Evgeny Danilenko | Ok so its like, the iterations can be implicit sometimes. Only the developers are able to see the iterations in detail but the customer cant. sort off? I just started researching extreme programming as its part of my assignment. I of course need to keep researching on the subject in order to fully understand the process, but i very much appreciate your help :) | |
| Dec 29, 2015 at 0:46 | comment | added | Thomas Owens♦ | @EvgenyDanilenko Depending on the level of control, some things may not be visible to the customer / project manager / outside entities. For example, a customer may only see releases as final things and iterations as previews (beta releases, for example). Yet the team may work on a more fine-grained view. I'm not really sure the best way to explain it other than that... | |
| Dec 28, 2015 at 17:45 | comment | added | Evgeny Danilenko | However, what do you mean by "But just because an iteration doesn't exist at the project level doesn't mean that..."? specifically the "iterations don't exist on a project level" | |
| Dec 28, 2015 at 17:05 | vote | accept | Evgeny Danilenko | ||
| Dec 28, 2015 at 12:10 | history | edited | Thomas Owens♦ | CC BY-SA 3.0 | added 519 characters in body |
| Dec 28, 2015 at 12:05 | comment | added | Thomas Owens♦ | @DocBrown That's a good point. I'm going to edit to reflect that. | |
| Dec 28, 2015 at 10:50 | comment | added | Doc Brown | @Giorgio: see air.mozilla.org/continuous-delivery-at-google, "8 minutes after you commit code it's live in production" | |
| Dec 28, 2015 at 8:37 | comment | added | Giorgio | @DocBrown: So they make a release each time they change the label of a button? Or do they have several larger features that are developed in parallel and are released each time they get finished? I.e.: the individual features may be non-trivial but since several features are developed and completed in parallel you get a continuous flow of releases. | |
| Dec 28, 2015 at 8:13 | comment | added | Doc Brown | "From a business perspective, it doesn't make sense for a project to operate on iterations shorter than 1 week ", of course, for lots of projects, products, or organizations, that is true. But at least some companies are practicing continuuos deployment, with several releases to the customer per day. The best known examples here are Google and Facebook, and they seem to be very successful with their approach. | |
| Dec 28, 2015 at 2:48 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |