Prashant KolaseProject Manager| Volkswagen Financial ServicesMumbai, Maharashtra, India
I have been assigned a Project for an application which is already ongoing. It is somewhere in the requirement gathering stage. What documentation shall i ask from the organisation in order to take it forward. Saving Changes...
Sort By:
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
Ask for everything, and hope you get enough that you don't have to start over. Saving Changes...
Suppose you are doing form scratch. What would you do and what would you need? Ask and look for them. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
I would gather, read and analyze all information that is available, written or verbal (talk to people!).
For that I normally start with the orgchart. It should show you key stakeholders to consider (and talk to). Understand the environment (your project as part of the total picture) to understand your level of freedom.
Do you have a set approach or can you adapt your project methodology? For SW applications and requirements, agile concepts might be appropriate.
The times I've inherited a project, I found it necessary to review the scope and desired outcomes of the project - what was documented and in discussions with the sponsor and stakeholders. I've found, more than once, that some course correction was needed. The gap was often due to changing business needs, not that somebody missed something important, but that happened, too. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Like Aaron, when I take over an in-progress project, I go through a re-planning exercise. This has the dual benefit of immersing me in the project while performance my due diligence. Saving Changes...
On some programs there can be so many documents and files, most of which are not useful and haphazardly stored in various shared locations like servers, that finding what you need is difficult.
I start by looking for high level summary type information documents like a charter, high level SOW, and schedule. That helps you prioritize what other information is going to be most useful to you. Then you can talk with the stakeholders more intelligently to help address questions you already have, and they can tell you the not so obvious things that you will need to consider.
In addition to re-planning as mentioned above, it's sometimes very useful to reorganize the key data or at least document some kind of map for where all the important and most current project data is located. That can save you a lot of time in the future looking for specific things buried deep in some document or program. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Remember that project manager is accountable for project requirements, not for product requirements. Product requirements are in charge of business analyst. If you are performing the last one then there is a lot of documention that can help you. My recommendation , just to mention something related to PMI, is going to PMI´s business analysis practice guide: https://www.pmi.org/pmbok-guide-standards/...siness-analysis Saving Changes...
Community Champion
