RisksAndMitigation
Every project runs risks. By defining, assessing, and prioritizing them, you can try and make sure the project stays succesfull. This document needs to stay current, by reviewing it once a month.
Each risk has a measurment of impact (how much does it affect us), on a scale from 0 to 9, and an likelyhood (how likely is the risk to affect us). Multiplied these two values indicate a priority.
Unclear requirements
Impact: 9, Likelyhood: .9
Therequirements are unclear. A GUI application is also something different from an HTML interface. Mitigate by both IRC brainstorm sessions and using an iterative development cycle, with clear monthly milestones, so that the functionality and architectural structure emerges and can be pinned down.
Mozilla interface (widgets) unstable
Impact: 7, Likelyhood: .9
Mozilla's CSS/XBL defined widgets are controlled by the Mozilla group. Combined with skin switching this makes for a very unstable enviroment for a 3rd party app. Mitigate by contacting the Mozilla XUL team and other 3rd party Mozilla app developers, with a some proposals on a seperate skin for Mozilla based apps.