Websites/Firefox Flicks/meetings/Retrospective
< Websites | Firefox Flicks
Intro
You're invited to participate in a release retrospective for Firefox Flicks. Let's discuss the nitty gritty in a constructive way (no finger pointing!) and help make future projects run more smoothly. To get a comprehensive review of all aspects of the project lifecycle, topics are broken down by phase and/or stakeholder. For each item below we will discuss “what went well” and “what can be improved” as well as the specific questions pertaining to each item.
Attendees
- cmore
- fred
- raymond
- chelsea
- jen
- lee
- mkelly
- jd
- Milos
Agenda / Notes
Intro
- (Re)introduce the team
- Provide general overview and recap of the project.
Planning
Questions
- Were there clear requirements and a solid understanding of the website from the start?
- Were goals and success metrics clearly defined?
Feedback
- some requirements were very clear (e.g. like video uploading)
- other things we didn't think about (like searching)
- some items were known to some, but not communicated to others (like social sharing)
- would have liked more design / ux / functionality reviews
- understood on a general level, but needed more working through the workflow
- project seemed to be larger than first thought
Design
Questions
- Were there sufficient user stories?
Feedback
- See previous section.
Resources
Questions
- Were roles / responsibilities clear?
- Were there sufficient resources to execute all phases smoothly within the project scope and schedule?
Feedback
- Opps, we skipped this section somehow.
Schedule
Questions
- Was the schedule realistic?
- Did anything cause the schedule to slip?
Feedback
- QA was unsure of schedule. Stage wasn't working for a while.
- Was uncertaintly around when the launch date was.
- Schedule conflicts like PTO, and work week.
- Anything that requires responsive design needs to have more time.
- Utilize IRC topics to announce key dates
- Know work weeks.
Development
Questions
- Was code freeze respected?
- Other?
Feedback
- No, see previous section regarding schedule.
QA testing
Questions
- Did development adhere to QA’s checklist?
Feedback
- Looking through https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist, felt like they pretty much did <3
- Nothing major from this checklist.
- Need to assign QA owner early on
- Make sure to add qa for tracebacks
IT / Deployment
Questions
- Were there any issues getting the app onto dev?
- Were there any issues getting the app onto stage?
- Were there any issues getting the app onto production?
- How did launch go?
Feedback
- getting dev live should have been prioritized higher
- dev/stage/prod used different push/update script and this caused issues
- l10n script breaks update script so it's not enabled until project is ready for that
- should specify physical location of hosting (e.g. engagement cluster for engagement projects)
Security
Questions
- Were there any issues in the security review process?
Feedback
- Security not present, will follow-up outside of this meeting.
L10N
Questions
- Were there any issues in the localization process?
- Was string freeze respected?
Feedback
- zh-TW defaulting to zh-CN
- already had many translations and didn't utilize them
- improperly encoded strings
- need to identify who will check english strings - visual check to make sure there are no issues on website
- issues come from generating copy in rich text programs (like Word)
- default should be that zh-tw should never fall back to zh-cn (should fall back to english instead)
- need to make sure that _final_ copy is handed to l10n on time; if not, be aware that release might need to be postponed
Communication:
Questions
- Were the channels of communication between all the stakeholders established from the start?
- Was there anything that blocked or hindered communication?
Feedback
- complicated project that happened very quickly and everyone did a good job keeping in touch about what they were working on
Summary
Action items
- ckoehler: follow-up with security and ux for specific feedback
- ckoehler: add traceback info to it dev/stage/prod bug
- ckoehler: update irc topic with relevant deadlines
- everyone: email t-shirt sizes to chelsea