User:Keegan (WMF)/Agreement2

Information about a product's development should be communicated when: Information about a product's development should be communicated at least towards the primary audience of the team's focus, for example the team's talk page, public mailing list, or appropriate community forum. Communication does not have to be comprehensive as long as it links to further information. Try to allow at least two weeks for feedback in each phase to allow time for volunteers to comment.
 * 1) Design research is beginning and completed - check against principles, strategy, existing plans.
 * 2) Design concepts are being considered and decided - user interaction, look and feel to the rest of the site
 * 3) A roadmap, plan, or timeline is determined - major community or WMF initiatives that may compete for time and energy from volunteers
 * 4) New iterations are made and ready for discussion - test the software as extensively as volunteers are willing to participate with you, check against findings from design research and concepts
 * 5) Translations are desired for both software and messaging - localization and internationalization are top priorities, and will help you gather feedback from non-English speakers
 * 6) Bug testing and fixes need more exposure for quality assurance - most of this work from community members comes after release into production
 * 7) Release into production - the need for use and surfacing critical bugs and/or missing/underdeveloped features