Talk:9.1.0 requirements: Difference between revisions
Jump to navigation
Jump to search
(start discussion about #1 top priority) |
(elaborations) |
||
| Line 1: | Line 1: | ||
== Words of Wisdom == |
== Words of Wisdom (regarding priorities) == |
||
\\//_ Priorities (pluralized) is an oxymoron. _\\// |
\\//_ Priorities (pluralized) is an oxymoron. _\\// |
||
| Line 11: | Line 11: | ||
(Who chooses the #1 top priority?) |
(Who chooses the #1 top priority?) |
||
== |
== Top Priority candidates for 9.1.0 == |
||
* new datastore |
* new datastore |
||
* new filesystem to replace jffs2 |
* new filesystem to replace jffs2 (or make jffs2 work better?) |
||
* system security |
* system security |
||
* performance |
* performance |
||
* reliability |
* reliability |
||
* document existing stuff |
|||
* document future stuff |
|||
* new features |
* new features |
||
* fix known bugs |
* fix known bugs |
||
* software update tools |
* software update tools |
||
* identify, attract, or acquire development resources |
|||
* remove impediments to progress |
|||
* reduce memory footprint |
|||
* reduce work-in-progress |
|||
* take out the garbage; clean up the house; improve the work environment |
|||
Choose a top priority that has few blockers, a high probability of success, that contributes to short-term and long-term survival, that will ultimately make many customers happy, and that makes the next successor priority easier to accomplish. |
|||
Revision as of 08:39, 23 September 2008
Words of Wisdom (regarding priorities)
\\//_ Priorities (pluralized) is an oxymoron. _\\//
\\//_ Two priorities is no priorities. _\\//
At any point in time, the team should have exactly one top priority. Each team member should focus on that one top priority, unless somehow blocked. The top priority will normally only change when something is substantially finished.
What is the #1 top priority for 9.1.0 right now ?
(Who chooses the #1 top priority?)
Top Priority candidates for 9.1.0
- new datastore
- new filesystem to replace jffs2 (or make jffs2 work better?)
- system security
- performance
- reliability
- document existing stuff
- document future stuff
- new features
- fix known bugs
- software update tools
- identify, attract, or acquire development resources
- remove impediments to progress
- reduce memory footprint
- reduce work-in-progress
- take out the garbage; clean up the house; improve the work environment
Choose a top priority that has few blockers, a high probability of success, that contributes to short-term and long-term survival, that will ultimately make many customers happy, and that makes the next successor priority easier to accomplish.