68
edits
Firefox/Projects/Tabcandy/Panorama 1 Debrief: Difference between revisions
Firefox/Projects/Tabcandy/Panorama 1 Debrief (view source)
Revision as of 19:03, 26 April 2011
, 26 April 2011no edit summary
No edit summary |
No edit summary |
||
| Line 55: | Line 55: | ||
* In any established product, there's inertia against large innovative features. For version one of such a feature, you need a dedicated strike team in order to get over that inertia. For version two, however, the feature and team needs to dissolve back into the product as a whole. | * In any established product, there's inertia against large innovative features. For version one of such a feature, you need a dedicated strike team in order to get over that inertia. For version two, however, the feature and team needs to dissolve back into the product as a whole. | ||
* It would be great if this process of introducing major innovations was more understood and had better support throughout the system. At the very least, there should be a "so you want to start a feature strike-team?" FAQ. | * It would be great if this process of introducing major innovations was more understood and had better support throughout the system. At the very least, there should be a "so you want to start a feature strike-team?" FAQ. | ||
= Original Discussion = | |||
The thoughts above have been distilled from the original chat meeting we had on the subject; you can read the [https://wiki.mozilla.org/Firefox/Projects/Tabcandy/Panorama_1_Debrief_Chat transcript] if you'd like. | |||