How to create simple, robust project plans

Great project plans are more than a list of what to do and when


When most people hear “project plan,” they typically imagine a schedule—a laundry list of what to do and when. But that’s only a tiny part of it. A good project manager develops a plan that covers not only the problem they are trying to solve but also its scope, deliverables, risks, and project dependencies—charting a path to project success.

When there’s no project plan, team members can find themselves lost in a maze of complexities. They might not know where to begin, or even worse, they might dive into their tasks without clearly understanding how and when their work fits into the bigger picture.


Project planning is the process of defining the objectives, scope, and activities required to complete a project. It’s a fundamental aspect of project management that involves setting clear goals, identifying resources, estimating costs, and developing a roadmap for project success.

Project planning lays the foundation for effective execution, monitoring, and control. This process enables project managers and teams to align their efforts and resources, reducing uncertainty and increasing the chances of delivering a project on time and within budget.

What is a project plan?

A project plan is the tangible outcome of the project planning process. It is a comprehensive document that outlines the project’s key elements, including its goals and objectives, scope, schedule, resource requirements, risks, and dependencies.

A project plan serves as a roadmap for all stakeholders, providing a clear understanding of the project’s purpose, milestones, and expected outcomes. It names team members, specifies necessary project planning tools, and details the steps required to succeed.

A well-structured project plan not only guides project execution but also serves as a communication tool to keep everyone informed and aligned throughout a project’s lifecycle.

Benefits of project planning

  1. Clarity and alignment: Project planning provides a shared understanding of project objectives and scope, ensuring all team members and stakeholders are on the same page. This clarity reduces misunderstandings and conflicting expectations.
  2. Resource allocation: It helps in identifying and allocating the required resources, whether they are human, financial, or material. This optimizes resource utilization and prevents overallocation.
  3. Risk management: Project planning allows for the identification and assessment of potential risks. By planning for risks, the project team can proactively address and mitigate them.
  4. Time management: A well-structured project plan includes a timeline with milestones and task dependencies, making it easier to manage project schedules and meet deadlines.
  5. Cost control: By estimating project costs during a project’s planning phase, organizations can track and control expenses more effectively.
  6. Improved communication: The project plan serves as a communication tool that keeps all stakeholders informed, ensuring that everyone is aware of project progress, changes, and issues.
  7. Quality assurance: Planning can include quality standards and processes to ensure that the project delivers high-quality results.
  8. Increased accountability: Project plans designate task owners, making it clear who is responsible for specific activities, promoting accountability.
  9. Efficient decision-making: Planning helps define decision-making processes, making it easier to address issues and make critical decisions as they arise during the project.

Project planning process (with steps)

Using a step-by-step approach to creating a project plan might seem like putting a hat on a hat, but it’s critical to building a solid and successful strategy. Before diving into the planning process, take some time to reflect on your team, organization, available resources, and project goals. It’s essential to foster a shared understanding with your team right from the beginning of the project planning phase.

Step 1: Think of your project plan as a map


  • 目標は何ですか?
  • プロジェクトが完了したことを、どうやって知れますか?
  • このマップに従うのは誰ですか?
  • What milestones will they pass along the way?
  • どのような障害に直面する可能性がありますか?
  • Are there any alternate routes available?

ステップ 2: 関係者を知る

Get a read on organizational politics, difficult personalities, and possible debate points that may arise during the project management process. Larry W. Smith, PMP, Project Manager at the Software Technology Support Center, stresses the importance of stakeholder analysis. According to Smith, everyone wants the project to succeed, but forgetting to meet the needs of just one influential stakeholder could derail even the best-laid plans.

Smith 氏は、時間を取って次のことを行うように推奨しています。

  • プロジェクトの関係者は誰かを明確にする
  • 関係者が期待することと影響の度合いを理解する
  • プロジェクトを進めながら、同僚と関係者からのフィードバックをどのように取り入れるかを決定する
  • すべてのニーズと期待を、リスク計画とリスク対応アクティビティに関連付ける
  • プロジェクトに関するコミュニケーション戦略すべてを入念に計画する

You can't overstate the importance of clear communication. That’s why Bernie Ferguson, Atlassian’s resident project leadership expert, starts communicating with stakeholders in the earliest stages of a project:

“We use the Project Poster technique to build a shared understanding amongst team members and stakeholders. What are we doing? What’s the value to customers and to the business? Why do we think this is the right solution? We get feedback on the answers to all these questions before anything hits the team’s roadmap.” —Bernie Ferguson, Atlassian

ステップ 3: 楽観的な考えを捨てて、タイムラインを詳細に策定する。

Project managers often make the mistake of being overly optimistic. Rather than focusing on the best possible outcome, PMs should consider problems that might arise and how they impact the project management timeline.

Performing essential due diligence, holding a “pre-mortem” workshop, or conducting one-on-one meetings with key stakeholders is a great way to identify potential roadblocks.

Consider sketching out a timeline by asking other project managers how long similar projects took to plan. Meet with teams you’ll work with to understand how long specific project tasks will take. Use project management tools and search project archives for old project schedules.


Emphasize the importance of communication by reiterating its significance. Keep all relevant parties informed about the project’s details because, after all, wouldn’t you want to be in the know? Simplified Gantt charts are an effective way of visualizing a project’s timeline so it’s easy for everyone to understand.

Step 4: Recruit friends and colleagues

As the project manager, it’s up to you to deliver the project plan (and, ultimately, the project). But this isn’t about you going off into a cubicle and writing the thing. As you develop the project plan, you must keep all key stakeholders involved. Stay in near-constant contact. You’ll find they’re excellent resources.

By gathering your team’s thoughts and brainstorming ideas together, you can arrive at meaningful conclusions quickly. Team collaboration fosters a sense of communal support and, therefore, yields better project plans.

At Atlassian, we use templates to reduce the overhead associated with the planning process and trigger discussions essential to project-planning best practices. Project plan templates are an excellent way to get people to think about aspects of project management that they may have yet to consider.

Having a good elevator pitch for your project is one thing, but creating a robust and effective plan is an entirely different undertaking. Let’s face it: Mapping out project risks and dependencies isn’t much fun. Atlassian’s powerful templates and helpful prompts allow project managers to think methodically about project plan creation, leading to fewer oversights and enhanced productivity.

チェックマークcheckmarkヒント: プロジェクト計画テンプレートは無料で、どなたでもご利用いただけます。メールアドレスを入力する必要すらありません。こちらで PDF を取得できます


Step 5: Think through goals and project scope

Create a problem statement that defines, in no uncertain terms, exactly what you’re trying to accomplish. Next, develop a hypothesis that states what you think should happen due to solving your problem. Then, provide a brief overview of the project’s context and any relevant data or insights that support it. Finally, establish the key metrics you will use to gauge the project’s success. These success metrics are likely to influence various aspects of your plan, shaping its direction and focus.

Ask your team members what they need, as opposed to what’s nice to have or unnecessary. Establishing a clear understanding of the project’s scope early in the planning process, including what is explicitly excluded, minimizes the risk of stakeholder miscommunication. It also aids in determining the appropriate time allocation for project contributors. This clarity makes it easier to identify and manage any changes in the project’s scope as they arise.

Step 6: Anticipate surprises

Nearly all project plans include details about budgets, project schedules, and scope. But a great plan also answers essential questions about your project, including:

  • Resources: What types of skills does the project demand? Who’s available? What’s our budget?
  • Decisions: Who will make recommendations? Who will approve or disapprove requests?
  • Communications: Who will be responsible for communicating progress and roadblocks?
  • Risk: What should team members watch out for? What’s the process for logging and tracking threats?
  • Reviews: How are you going to gather feedback before the project ships?
  • 承認:他にこのプロジェクトを承認する必要があるのは誰ですか?最終的な意思決定者は誰ですか?
  • タイミング:チーム・メンバーの作業スケジュールはプロジェクトのタイムラインに合っていますか?どのようにして締め切りを選びましたか?


チェックマークCheckmarkヒント: プロジェクトに関する確実な意思決定を適時に行うための DACI 手法を使用します。

ステップ 7:プロジェクト管理アプローチを選ぶ

ほとんどの PM は、プロジェクト管理にウォーターフォール・アプローチまたはアジャイル・アプローチのどちらかを選択します。アジャイル・アプローチは、プロジェクトの計画、要件、結果を継続的に評価する反復プロセスを利用して、迅速に結果を出します。この方法では、時間とリソースは固定したものと見なします。


ステップ 8: 計画を書いてレビューする



  • プロジェクト名
  • 実施日
  • 予算
  • 計画の目標
  • 重要なマイルストーンと期待される測定可能な影響
  • 各タスクの予定開始日と完了日
  • 個別のタスクの所有者を強調するコールアウト
  • 何が行われるべきかを明確に示す、タスクの詳細とメモ
  • 遅延を防ぐための、互いに依存関係にあるリスクおよびタスク (またはチーム) のコールアウト



ステップ 9:計画を周りの人と共有しましょう!






  • プロジェクトの目標と目的
    • ブランドの視認性を 20% 向上させます。
    • 3 か月以内に 1,000 件の見込み客を生み出します。
    • 春のシーズン中、売上高を 15% 増加させます。
  • スコープ
    • オンラインとオフラインの一連のマーケティング資料を作成します。
    • 新しい製品ラインを立ち上げます。
    • デジタル広告キャンペーンを実施します。
  • プロジェクトのスケジュール
    • フェーズ 1(1 か月目と 2 か月目):キャンペーン戦略とコンテンツ制作。
    • フェーズ 2(3 か月目):発売とマーケティング展開。
  • リソース
    • マーケティング・チーム(メンバー 4 名)。
    • 広告と資料の予算 $50,000。
  • リスク
    • 屋外イベントに影響を与える予測不能な天候。
    • 市場の競争は価格競争につながります。
  • 依存関係
    • 製品開発の完了(キャンペーン開始前)。
    • マーケティング資料の入手可能性(広告を出す前)。
  • 品質保証
    • 質の高いコンテンツを確保するための定期的なレビューとフィードバック・セッション。
  • タスク所有者
    • キャンペーン戦略:Sarah
    • コンテンツ制作:John
    • 製品発売:Emily
    • 広告キャンペーン:Mark







プロジェクトチームと利害関係者の連携を維持する、1 ページのコラボレーション資料です

プロジェクト管理テンプレート コレクション

この Confluence テンプレートのコレクションを使用して、プロジェクトを作成し実行します

Confluence で、すべてのチームのコンテンツ コラボレーションがより迅速になります