Changing the title, I'm tired of being "demoralized". I want to improve the state of our JIRAs and planning overall by building upon my previous remarks (cf. "RE: Demoralized over JIRA state" above).
If we wanted to apply an Agile/Scrum process to Mahout development, we could: * Identify a "Product Owner" to develop "epic" JIRAs to focus our development and to prioritize our backlog by quarterly release. Each release would then have a theme and would be a complete set of concrete enhancements with user-centric goals. Perhaps even a users@ member could take on this role, IMHO it does not need to be a developer, but someone who can work to establish and communicate a vision and a roadmap. * Identify a "Scrum Master" to drive the creation of specific "story" JIRAs and guide development. This is a bit more like herding cats than managing people. This probably needs to be a committer as it has much more technical content and knowledge of the code base. We are all doing Mahout part-time so the schedule will be less predictable. But with Agile metrics computable if points are assigned to the stories we could at least measure our velocity quarterly. Burndowns anybody? Jeff
