Project Management/2012 Q1/Requirements
From MozillaWiki
Contents
Current Situation
Goals
- Provide transparency to the entire organization
- Allow for better planning
- Provide more benefit than required additional work (cost/benefit analysis)
- Allow for formalization of planning and execution while still allowing for agility and R&D activities.
Users
- Web Product Engineer (Daily)
- Stakeholder (Weekly)
- Web Dev Programmer (Monthly)
- Director (Monthly)
General Requirements
- Easy-to-use
- Accessible
- Web-based
- Cross platform and mobile-friendly
- Resource management
- Timeline management
- Project prioritization
- Project submission process
- Links and other project meta data
- Private and public views
- Data visualization and dashboard tools
- Scrum/Agile abilities
- Integrates with existing tools (Bugzilla, Github, SVN, wikis)
- Provides instant benefit for everyone involved!
- Role-based security
What the future tool should NOT be
- A replacement for Bugzilla, Trello, or other task trackers.
- Additional work for developers
- Closed off from the community
- Complicated and difficult to use
User Stories
Template: "As a <role>, I want <goal/desire> so that <benefit>"
Roles: Project Manager, Engineer, Director, External Contributor
- As a project manager, I want to see a dashboard of my project so I an keep track of the progress to completion.
- As a director, I want to see a dashboard of all of my team's projects so I can better plan for the future.
- As an external contributor, I want to see a list of all open projects so I find new projects or tasks that interest me.
- As an engineer, I want to minimize the amount of time using a PM tool so that I can focus on creating amazing software.
- As an operations manager, I want to see what projects will require hardware so that I can plan for procurement.
- As a project manager, I want to see data that will help inform continuous improvement.
