Project management:Current tasks

Welcome to the current tasks of the project management department!

Right away

 * Definition of done
 * User stories
 * Add most important epics to the product backlog with zenbitz
 * How does the proposal concept we use fit into the Scrum framework? How should proposals be used in sprints?
 * Set up release wiki templates
 * Product backlog
 * A release consists of
 * Prior release feedback evaluation
 * Initial priorization meeting (determining which PBI to tackle first)
 * 2-4 sprints to tackle for the next release
 * Sprints improve: features, tools, asset pipeline/documentation
 * Release preparation (checklist)
 * Actual release
 * Work on features / tools should be always based on actual user stories from the product backlog
 * How can we ensure that contributors primarily focus on the actual sprint goals? Should we try to ensure this at all?
 * Brainstorming: what kind of information should the How_to_contribute article actually contain?
 * Proposed proposal >> Drafted proposal (implement via ReplaceText)
 * Give UI designers a pointer that we'll need a solid fleshed out inventory UI spec / proposal before implementation can start
 * Add constructive contribution guidelines to Communication
 * User story format for feature & tool request PBIs at Trac!

Set back

 * Take care of Wiki maintenance tasks
 * Add commit guidelines to how to use SVN articles of the departments; how about revert guidelines? when should we try to revert changes?
 * Sepearate How to use Trac articles for each department; featuring information how trac is utilized in this specific department and providing templates for common trac tasks
 * Take into account that the workflow might be slightly different for developers with SVN write access and occasional contributors who send in their code/assets
 * Incorporate "one username prefered" policy into contribution guidelines
 * Items: description + backstory (writing department) & stats (mechanics department)
 * Department philosophy: HOW do we want to create it? Why do we approach the process in the way we do?
 * Department-specific wiki editing guidelines
 * Do further research on dual licensing assets (baked vs. raw ones)
 * Flesh out long term proposal to switch to Distributed version control software; incorporate feedback given here:
 * http://www.gamedev.net/community/forums/topic.asp?topic_id=589797
 * http://stackoverflow.com/questions/4389578/can-artists-realistically-cope-with-distributed-version-control-in-an-open-sour