Spreadfirefox 30 post morteum
From MozillaWiki
Spread Firefox milestone 3.0 post-morteum
- What went well:
- Launch process:
- Having IT & Buchanan on site worked well
- Content & functionality tracker to double check site against
- Had a lot of prep time to get site up there
- Alex's scripts moved almost all setting and content changes over. Very little to do manually.
- Made right decision to wait and have a better quality release
- Project management:
- Good communications & frequency of meetings
- Milestones for bug tracking
- Weekly triaging
- Great teamwork
- QA:
- Outstanding!
- Great work on finding bugs, checking user experience
- Design:
- Mockups worked well to double check site
- Looked great
- Designer worked quickly to make changes
- Launch process:
- What didn't go so well:
- Not scoped properly -- was sold as a light design.
- Launch:
- Need much more accurate estimates on timing -- slipped from March 4 to April 30
- Should have had a cut off for changes, including final fixes
- Design:
- Should have had a final
- No front end design involved since Neil wasn't hired :(
- Didn't look at them until Feb when they were received on Dec. 4
- Files:
- No concessions for the "fluidity" of the web -- changes had to be made to make it work in a real world situation.
- Not layered properly
- Too graphics & pixel heavy
- Files not organized well nor labeled
- Feeling that we didn't get TRO's A game
- Didn't look at them until Feb when they were received on Dec. 4
- Affiliates:
- Order of the steps wasn't clear/what was contingent on one another.
- Required quick turnaround
- What to improve:
- Better scope
- Better time estimates that build in time for things to go wrong or slip
- More upfront involvement with webdev & QA
- Have more collaborative relationship with designer - have them review the staging site.
- Develop a project roadmap
- Centralized messaging repository to collect comments or push files and comments to the wiki.
- Layout a specific schedule for QA -- when xbrowser testing can start.
