# Requirements Gathering: 6 Steps for Project Success > Learn a requirements gathering process with 6 steps, requirement types, and techniques to align stakeholders, prevent scope creep, and deliver on time. Source: https://asana.com/ja/resources/requirements-gathering ## Requirements gathering: 6 steps for project success #### Summary Requirements gathering is a critical project management process that helps teams identify, document, and manage everything needed for project success. This guide walks you through a proven six-step process, explains the different types of requirements you'll encounter, and shares practical techniques to ensure your projects stay on track and within budget. Requirements gathering may seem self-explanatory, but it rarely receives the full attention it deserves. Like stretching before exercising or brushing your teeth before bed, it's a simple task that often gets overlooked. But ignoring these seemingly straightforward things can lead to injuries, cavities, or, in project management, project risks. In this piece, we'll outline the requirements-gathering process and explain how taking time to focus on it can lead to successful project outcomes. ## What is requirements gathering in project management? Requirements gathering is the process of identifying, documenting, and managing all the requirements needed to complete a project successfully. It typically occurs during the [project initiation](/resources/project-initiation) phase, often as part of the [project brief](/resources/project-brief) or [kick-off meeting](/resources/project-kickoff-meeting), and continues throughout the [project timeline](/resources/create-project-management-timeline-template). During requirements gathering, you'll answer key questions such as: - How long will our project schedule be? - Who will be involved in the project? - What risks may we face in this project? Requirements gathering shouldn't be complex, but it's an important component of the project initiation process. ## Why is requirements gathering important? Requirements gathering is essential because it helps you prevent common project risks like running out of resources, exceeding your budget, or underestimating timelines. When you invest time in this process upfront, you set your project up for success. There are many benefits of requirements gathering, which include: - **Improves stakeholder satisfaction:** When you follow an effective requirements-gathering process, you improve stakeholder satisfaction by delivering more on-target project deliverables. Your stakeholders will be happy when they know what to expect with your project. - **Increases project success rate:** Requirements gathering also increases your project success rate because the more prepared you are for your upcoming project, the less likely you are to encounter project risks. - **Reduces project costs:** Project risks can increase costs. By implementing [risk mitigation](/resources/risk-mitigation) strategies early, you can reduce costs and stay within budget. - [記事: プロジェクトの予算を作成する (固守する) 方法](/resources/project-budget) ## Types of project requirements Before you begin the requirements gathering process, it helps to understand the different types of requirements you'll encounter. Categorizing requirements correctly ensures nothing gets overlooked and helps your team prioritize effectively. ### Business requirements vs. technical requirements Requirement type Definition Example **Business requirements** Define what your organization wants to achieve, its strategic goals, desired outcomes, and stakeholder value Increase customer retention by 15% through a new loyalty program **Technical requirements** Explain how the project must be built, including specifications for systems, infrastructure, security, and integrations The loyalty program must integrate with your existing CRM platform ### Functional requirements vs. nonfunctional requirements Requirement type Definition Example **Functional requirements** Describe what a product or system should do, including specific features, behaviors, and functions Users should be able to filter search results by date **Nonfunctional requirements** Describe how a system should perform, including speed, security, scalability, and usability The search function must return results within two seconds Understanding these distinctions helps you ask the right questions during stakeholder meetings and ensures your requirements document captures the full picture of what your project needs to succeed. ## The 6-step requirements gathering process To gather your requirements, use the following six-step process. Once you're finished, you should have a comprehensive requirements document outlining the resources you need to move forward through the [project phases](/resources/project-management-phases). ### Step 1: Assign roles The first step in requirements gathering is to assign roles in your project. This is when you identify your [project stakeholders](/resources/project-stakeholder). A stakeholder is anyone invested in the project, whether internal or external. Identifying these roles first helps you determine who should analyze your [project scope](/resources/project-scope). Key roles to document in a [stakeholder register](/templates/stakeholder-register) include: - **Internal stakeholders:** Department managers, board members, and executives - **External stakeholders:** Customers, vendors, and partners - **Project team:** [Project manager](/resources/become-a-project-manager), [project administrator](/resources/project-administrator), designers, product testers, and developers While you may feel tempted to jump headfirst into your project and start listing everything you know you'll need, this can be a mistake. Slow down and stick to the process, and you'll have a better chance of preventing [project risk](/resources/project-risks). ### Step 2: Meet with stakeholders Once you've identified your project stakeholders, meet with them to understand what they're hoping to get out of the project. Understanding what stakeholders want matters because they're ultimately the ones you're creating your deliverables for. Some questions you can ask include: - What is your goal for this project? - What do you think would make this project successful? - What are your concerns about this project? - What do you wish this product or service would do that it doesn't already? - What changes would you recommend about this project? The stakeholders are the people you're ultimately developing the project for, so you should ask them questions that can help you create your list of requirements. ### Step 3: Gather and document Step three occurs simultaneously with step two, as you ask stakeholders questions, document everything so you have all the answers you need to start your project. Use a [project management tool](/uses/project-management) to collect and document this information. That way, you can keep your project plan, project requirements, and project communication all in one place. Some examples of what you might document include: - Stakeholder answers to interview questions - Stakeholder questions - Stakeholder requests - Stakeholder comments - Questions and comments that arise during interviews You don't have to use every answer you receive, but having everything documented can help you see all of your stakeholders' perspectives, which will help with requirements management. Documentation is part of gathering requirements. A [technical documentation template](/templates/technical-documentation) helps the team record requirements, definitions, and materials in one centralized location, so that everyone works from the same source. - [プロジェクト立ち上げテンプレートを作成する](/templates/project-initiation) ### Step 4: List assumptions and requirements Now that you've completed the [intake process](/resources/project-intake-process), create your [requirements management plan](/resources/requirements-management) based on the information you've gathered. Consider the questions you initially set out to answer during the requirements gathering process. Then, use them to create your requirements goals, including: - **Length of project schedule:** Map out your project timeline using a Gantt chart to visualize requirements that depend on [project milestones](/resources/project-milestones). Some requirements will apply for the full duration of the project, whereas others may only apply during distinct project phases. - **People involved in the project:** Identify exactly which team members will be involved in your project, including how many designers, developers, or managers you'll need to execute every step. People are part of your project requirements because if you don't have the team members you need, you won't be able to complete the project on time. - **Project risks:** Understanding your project risks is important for identifying project requirements. Use a [risk register](/resources/risk-register) to determine which risks are of highest priority, such as stakeholder feedback, timeline delays, and lack of budget. Like [SMART goals](/resources/smart-goals), your project requirements should be actionable, measurable, and quantifiable. Try to go into as much detail as possible when listing out your project budget, timeline, required resources, and team. ### Step 5: Get approval Once you formalize your project requirements, you'll need stakeholder approval to establish your [project baseline](/resources/project-baseline) and ensure you're meeting user needs. Developing a [scope management plan](/resources/scope-management-plan) and encouraging clear communication can prevent [scope creep](/resources/what-is-scope-creep) by ensuring that your stakeholders are aware of the project's limits from the outset. You can then proceed with your [implementation plan](/resources/implementation-plan), which may include acquiring resources and assembling a team. ### Step 6: Monitor progress The last part of the process is [monitoring the progress of your project](/resources/how-project-status-reports). You can use project management software to track your project budget and other requirements as you move through project execution. The benefit of project management software is that you can see changes to your project in real-time and take immediate action when things go awry. - [Read: How to write a software requirement document (with template)](/resources/software-requirement-document-template) ## Requirements gathering techniques Sometimes, stakeholders won't know exactly what a project needs. When input is incomplete, use a [business requirements document template](/templates/business-requirements-document) to organize what you know and identify remaining gaps. To make sure you're fully ready for the project life cycle, try these research techniques. - **Questionnaires:** Questionnaires can be beneficial if you need to ask stakeholders the same question across the board. Share the questionnaire with stakeholders in advance and give them time to respond to questions about project requirements. While questionnaires can be valuable for gathering requirements, they're not very effective for executive stakeholders, who may be too busy to complete them. - **Use case scenarios:** A use case scenario is a written description of how you think your team members will execute the project. Sharing a use case scenario gives stakeholders a clear picture of the [project roadmap](/resources/project-roadmap) and planned deliverables. Stakeholders then have something to respond to if the use case doesn't meet their expectations. - **Mind mapping:** Mind mapping is a visual form of brainstorming that's particularly helpful for assessing what project requirements you need. In the center of your mind map, place your main [project objective](/resources/how-project-objectives). In bubbles branching off from the main objective, list categories of things you need until you've captured all of your project requirements. - **Prototyping:** Interviewing your stakeholders may be unsuccessful if they don't know exactly what they want from the project. Try creating prototypes to show stakeholders what the potential deliverables could look like. This can help your stakeholders define what they do and don't like, so you can identify the exact requirements you need to launch the project. If none of these techniques feel quite right, check out other online tools to help you gather information, such as an [idea board](/resources/idea-board), a focus group, user stories, or a [decision matrix template](/resources/decision-matrix-examples). ## Streamline requirements gathering with project management software Requirements gathering is an important part of project planning. Whether you're interviewing stakeholders or conducting other research to compile your list of project requirements, having project management software that can hold all your information and seamlessly move it into the next phase will go a long way. When your stakeholders and team members share access, you can communicate and collaborate from project start to finish, reducing the risk of setbacks. [Get started](/create-account) with Asana to bring your project requirements, stakeholders, and team communication together in one place. - [Asana でプロジェクトタイムラインを作成](/product) ## Frequently asked questions about requirements gathering #### What is an example of requirements gathering in action? A marketing team launching a new website might interview stakeholders to define goals (like increasing leads by 20%), document technical needs (CMS integration), and identify resource requirements (budget and team members). #### What is another term for requirements gathering? Requirements gathering is also called requirements elicitation, requirements discovery, or [needs assessment](/templates/needs-assessment). #### Who is responsible for requirements gathering? The project manager or business analyst typically leads the process, with collaborative input from stakeholders, subject matter experts, developers, designers, and end users. #### How long should requirements gathering take? For smaller projects, requirements gathering takes a few days to a week; larger initiatives may require several weeks. Investing adequate time upfront helps you avoid scope creep and costly changes later. - [プロジェクト管理](/resources/project-management) - [プロジェクト管理ツールの選び方: おすすめ 11 選 (最新版)](/ja/resources/best-project-management-software) プロジェクト管理 コラボレーション (Collaboration) 生産性 プロジェクト計画 ゴール アジャイル #### コンテンツライター プロジェクト管理ツールとは？プロジェクト管理ツール (プロジェクトマネジメントツール) は、チームにおける仕事の整理、追跡、実行を効率化するツールです。簡単に言うと、プロジェクト管理ツールとは、インタラクティブなワークスペースであると言えます。そこでは、作業、コラボレーション、そしてメンバーとのコミュニケーションの方法を調整できます。しかし、優れたプロジェ ... - [明確なプロジェクトの要旨を作成するための 5 つのステップ](/ja/resources/project-brief) プロジェクト計画 プロジェクト管理 #### ライター プロジェクト関係者に、あなたのプロジェクトに関する重要な情報の要約を簡単に確認してもらう必要があります。何を送ったらいいでしょうか？何を送ればいいかわからない場合は、プロジェクト概要 (プロジェクトブリーフィング) が必要かもしれません。プロジェクト概要があれば、それはプロジェクトの主要な情報がまとめられた、チーム全体にとっての信頼できる唯一の情報源となり ... - [リスクマネジメントの基本と 6 つのステップを徹底解説](/ja/resources/project-risk-management-process) プロジェクト計画 #### ライター 的確な計画と管理を実施することで、プロジェクトは順調に進みます。また自分たちのプロジェクト管理スキルを伸ばしたり、効果が実証済みのプロジェクト管理戦略やリスク対策を取り入れたりすれば、より効果的でしょう。しかし、どんなに入念に計画されたプロジェクトにも、リスクは必ず存在します。これまで何かのプロジェクトに携わったことがあるなら、過去に想定外のリスクに見舞わ ... - [SMART 目標とは？設定方法とヒント、具体例を紹介](/ja/resources/smart-goals) ゴール プロジェクト管理 プロジェクト計画 #### ライター 素晴らしい成果を挙げたチームは、どのチームも、結果を出すためにまず目標を設定する必要がありました。目標を設定することで、疾病治療、より効率的で持続可能な設備の開発、クジラやイルカにとって海洋の安全を高めることなどが実現されます。目標があれば、目指す場所と、そこに到達するための最適な道筋を視覚化できるのです。しかし、大胆な目標を達成することとは、ただ空の星を ... - [プロジェクトを成功へ導く要件収集の 6 つのステップ](/ja/resources/requirements-gathering) プロジェクト計画 プロジェクト管理 アジャイル - [コンテンツライター](/author/team-asana) Requirements gathering may seem self-explanatory, but it rarely receives the full attention it deserves. Like stretching before exercising or brushing your teeth before bed, it's ...