I have been nominated for developing a project management tool for my organization where all project related information, check list and related information to be stored (as of now, no concrete requirements are listed). With reference to that, how shall I start listing requirements? Basic requirements I've listed are, project information (where scope, objective, title and other related information to be saved), checklist mapping with the entitled project, Task, reports, etc... What are the other requirements which could be part of this project? What approach do I need to follow? Any reference or open source PM tools?
closed as too broad by Marv Mills, Sergey Kudryavtsev, Mark C. Wallace, Joel Bancroft-Connors, Tob Jul 18 '15 at 5:15
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Requirements flow from desired business capabilities. So first step is to engage your stakeholders/internal customers to figure out what business capabilities they want. For example, is this a tool for PMs to manage schedule and budget better? Or is it intended to support timely reporting to senior management? Is monitoring risk a big thing or a little thing? What about long term benefits realization? And is there an off-the-shelf solution that can deliver the business capabilities that I need?
You also need to consider what requirements exist outside of mere systems, in other words what processes does the tool support and how do the tool and processes relate to your organization. Remember that this is just a tool, if you don't have an effective way to use it or if it isn't aligned with your organization the tool could be worse than useless.