Free Agile Project Sprint Planning Template
Agile Project Sprint Planning
|
Prepared by: |
[YOUR NAME] |
|
Company: |
[YOUR COMPANY NAME] |
|
Email: |
[YOUR COMPANY EMAIL] |
|
Address: |
[OUR COMPANY ADDRESS] |
|
Phone: |
[YOUR COMPANY NUMBER] |
|
Website: |
[YOUR COMPANY WEBSITE] |
I. Sprint Overview
|
Sprint Goal |
Define the specific objective for the sprint, linked directly to the product roadmap. |
|---|---|
|
Sprint Duration |
Start Date: [June 1, 2050] | End Date: [June 14, 2050] |
|
Key Milestones |
[June 3, 2050]: Initial Review |
|
Sprint Budget |
Allocate a budget for sprint resources and unexpected expenses. |
II. Team Composition
|
Role |
Name |
Responsibilities |
Contact Information |
|---|---|---|---|
|
Product Owner |
[Team Member Name] |
Defining the product backlog and ensuring the team understands the sprint goals. |
[Team Member Email] |
|
Scrum Master |
[Team Member Name] |
Facilitating the sprint, addressing hurdles, ensuring adherence to Agile practices. |
[Team Member Email] |
|
Development Team |
[Team Member Name] |
Implementing functionality, developing code, and unit testing. |
[Team Member Email] |
III. Sprint Backlog
-
Analyze user needs and requirements.
-
Design system architecture.
-
Develop software components.
-
Integration of components and system testing.
-
Deployment and post-deployment support planning.
IV. Daily Standup Schedule
Time: 9:00 AM every day
Location: [Virtual Meeting Link/Physical Location]
Each team member will answer:
-
What did I accomplish yesterday?
-
What will I work on today?
-
What obstacles are impeding my progress?
V. Sprint Review and Retrospective
Sprint Review Date: [June 15, 2050]
Retrospective Date: [June 16, 2050]
Objective:
-
Review completed work and adapt the product backlog.
-
Discuss what went well, what could be improved, and plan improvements for the next sprint.
VI. Definition of Done
A list of criteria which must be met before a product increment is considered "done":
-
Code complete with peer review.
-
All unit tests pass.
-
Acceptance criteria met.
-
Functional testing signed off.
-
Documentation updated.
