Development process improvement: Difference between revisions
→Status updates and notes: +1 link |
some more links |
||
| Line 27: | Line 27: | ||
=== Communications === |
=== Communications === |
||
* [http://eiximenis.wikimedia.org/TechAnnouncements Tech announcements discussion] |
|||
=== Tools === |
=== Tools === |
||
| ⚫ | |||
== Software design document == |
== Software design document == |
||
| Line 56: | Line 59: | ||
* [[:mw:Tracker/PM tool|Tracker/PM tool]] |
* [[:mw:Tracker/PM tool|Tracker/PM tool]] |
||
* [https://wiki.mozilla.org/Bugzilla:Project_Management_with_Bugzilla Summary of discussions] with people at Bugzilla about using Bugzilla for Project |
* [https://wiki.mozilla.org/Bugzilla:Project_Management_with_Bugzilla Summary of discussions] with people at Bugzilla about using Bugzilla for Project Management |
||
| ⚫ | |||
Revision as of 22:30, 10 August 2010
|
Tech processes improvement
Increase transparency and organize Wikimedia Foundation's engineering efforts more efficiently
|
Project justification
With the Wikimedia Foundation Tech department growing at the pace that it is, we need to figure out ways of communication with each other and the rest of the world about what we're doing, and how we're doing it. The communication & collaboration mechanisms we come up with should be appropriate for the scale of organization that we are, and facilitate collaboration with community volunteers to both increase the impact of Wikimedia Foundation employees, as well as ensure focus on issues that matter to the community.
Project deliverables
- Document summarizing the current situation, detailing the requirements, offering recommendations and outlining an implementation plan.
User goals
- « Community »
- understanding of what the Wikimedia Foundation is investing in
- ability to provide input into ongoing initiatives
- opportunity to identify and volunteer in areas where they are likely to have the greatest impact and assistance from the Wikimedia Foundation
- Wikimedia Foundation employees and management
- ability to see the quick summary of how things are going; when intervention is needed and when things are sailing along smoothly.
Specifications
Processes
Communications
Tools
Software design document
Test plan
Documentation plan
User interface design docs
Schedule
A couple of different people have been thinking about this over the past few months. There was a formal evaluation process done by Rob Lanphier in May-June 2010.
This was a relatively short process that started back in May, and is nearly complete. We're currently working on implementing the communication improvements now.
Task management
- Bug list related to our bugzilla setup
Release management plan
Community management plan
Status updates and notes
- Tracker/PM tool
- Summary of discussions with people at Bugzilla about using Bugzilla for Project Management