You are a seasoned project management consultant specializing in Agile methodologies for software development.  Your task is to generate a detailed project management template suitable for a team of 5-10 developers working on a medium-sized software project (estimated duration: 6-12 months).  This template should be suitable for use in a collaborative environment using project management software such as Asana, Trello, or Jira.  The template should cover all key aspects of project management, including but not limited to:</p>
<p>**Phase 1: Initiation &#038; Planning (approx. 1 week)**<br />
*   Project Goals &#038; Objectives (SMART goals): Clearly define the project&#8217;s purpose, deliverables, and measurable success criteria.<br />
*   Project Scope Definition: Detail all included and excluded tasks, features, and functionalities.<br />
*   Stakeholder Identification &#038; Analysis: List all key stakeholders and their roles, expectations, and communication preferences.<br />
*   Risk Assessment &#038; Mitigation Plan: Identify potential risks and develop strategies to mitigate them.<br />
*   Resource Allocation: Assign team members to specific tasks, outlining their responsibilities and timelines.<br />
*   Budget Allocation &#038; Tracking: Outline the project budget and establish a method for tracking expenses.<br />
*   Communication Plan: Define communication channels, frequency, and reporting methods.</p>
<p>**Phase 2: Execution (approx. 10-11 months)**<br />
*   Sprint Planning: Outline tasks for each sprint (e.g., 2-week sprints), including acceptance criteria for each.<br />
*   Daily Stand-up Meetings: Provide a template for conducting efficient daily stand-up meetings.<br />
*   Task Tracking &#038; Progress Reporting: Outline methods for tracking progress and generating regular reports.<br />
*   Issue &#038; Bug Tracking: Describe the process for identifying, documenting, and resolving issues and bugs.<br />
*   Change Management Process: Define a process for handling requests for changes to the project scope.</p>
<p>**Phase 3: Closure (approx. 1 week)**<br />
*   Project Review &#038; Evaluation: Detail the process for reviewing the project&#8217;s success against its objectives.<br />
*   Lessons Learned: Capture insights and lessons learned throughout the project lifecycle.<br />
*   Documentation &#038; Archiving: Outline how project documentation will be archived and maintained.</p>
<p>**Output Format:** The template should be presented as a structured document with clear headings, subheadings, and tables where appropriate.  Include placeholders for specific project details (e.g., project name, start date, end date, etc.).  The template should be concise, easy to understand, and adaptable to different project contexts.  Ensure the language is professional and suitable for a technical audience. The template should be comprehensive enough to be used as a standalone document but also flexible enough to be adapted to different project needs and contexts.  Focus on providing a practical, actionable template that can be immediately implemented in a real-world project setting.</p>
<p>**Validation:** The generated template should be easily adaptable to various software projects, provide a clear structure for managing tasks, and include comprehensive sections for risk management, communication, and progress tracking.