Product Owner Training Guide (Tinggit Platform)¶

Audience: Product Owners
Purpose: Teach Product Owners how to use Redmine correctly to plan, prioritize, and release product value

• Table of contents
• Product Owner Training Guide (Tinggit Platform)
  • 1. Your Role as Product Owner
  • 2. Managing the Product Backlog
  • 3. Sprint Preparation (Before Sprint Open)
  • 4. During the Sprint
  • 5. Sprint Review & Sprint Close
  • 6. Product Releases
  • 7. Handling Exceptions
  • 8. Common Product Owner Mistakes (Avoid These)
  • 9. Final Reminder

---

1. Your Role as Product Owner¶

As a Product Owner, you own:

• Product vision and outcomes
• Backlog ordering and prioritization
• Sprint goals (WHY, not HOW)
• Product releases and release notes

You do not own:

• Task breakdown
• Technical design
• Sprint execution details

Authoritative reference: Product Process Guidelines

---

2. Managing the Product Backlog¶

What you must ensure for every backlog item:

• Clear purpose (WHY)
• Business or platform context
• Acceptance Criteria
• Priority relative to other items

What you must NOT do:

• Add tasks or subtasks
• Define implementation steps
• Assign developers

Backlog items must be ready, not designed.

---

3. Sprint Preparation (Before Sprint Open)¶

Before a sprint starts, you must:

• Review sprint candidates
• Confirm items meet Definition of Ready
• Align on Sprint Goal with the team

Sprint rules:

• Sprint is a time-boxed execution container
• Sprint scope should not change casually

Authoritative reference: Sprint Open Process

---

4. During the Sprint¶

During the sprint, your responsibilities are:

• Clarify intent when questions arise
• Protect the Sprint Goal
• Reject scope creep
• Participate in Sprint Review

You must NOT:

• Reassign tasks
• Change priorities mid-sprint
• Redesign solutions

---

5. Sprint Review & Sprint Close¶

At Sprint Review:

• Validate completed work against Acceptance Criteria
• Provide feedback
• Confirm what is accepted vs not accepted

Sprint Close is a process, not a meeting.

You must verify:

• Accepted stories are truly DONE
• No sprint bugs remain open
• Sprint Goal outcome is documented

Authoritative reference: Sprint Close Process

---

6. Product Releases¶

Product Releases represent business value shipped.

As a Product Owner, you:

• Decide release scope
• Own Release Versions
• Write Product Release Notes
• Close releases only after validation

You do NOT:

• Track deployments
• Manage service versions
• Control CI/CD pipelines

Authoritative reference: Release Management Process

---

7. Handling Exceptions¶

For hotfixes, rollbacks, or emergencies:

• Do not force work into sprints
• Follow exception workflows
• Preserve history at all costs

Authoritative reference: Edge Case & Exception Handling

---

8. Common Product Owner Mistakes (Avoid These)¶

• Treating sprints as deadlines
• Adding work mid-sprint
• Mixing sprint and release concepts
• Closing releases without validation

---

9. Final Reminder¶

bq. As a Product Owner, your power comes from clarity, not control.

Your success is measured by:

• Predictable delivery
• Clean history
• Trust in data