PROJECT DOCUMENTATION CAPSTONE PROJECT

PAYFLOW

Product Overview
PayFlow is a new mobile and web fintech application designed to help small
businesses:

• Accept digital payments

• Track daily sales in real time

• Generate automated invoices

• View simple financial analytics

The product is being launched by a startup aiming to release a Minimum Viable

The company has previously faced:

• Poor backlog clarity

• Lost sprint decisions

• No single place for documentation

• Knowledge gaps when developers leave

Leadership has mandated that:

“Agile documentation must be lightweight, auditable, and fully traceable — all

Team Member Role

Group/Team act as a Scrum Team, collectively covering:

• Product Owner (value & backlog ownership)

• Scrum Master (process & facilitation)

Each team member is also responsible for documentation discipline within their role.

SCRUM CONSTRAINTS

Team members must follow the Scrum Guide:

• Documentation must support Scrum artifacts

• No waterfall documents (e.g., long upfront specs)

• Everything must be tied back to:

o Product Goal

o Sprint Goal

o Increment

• Documentation must evolve iteratively

CAPSTONE OBJECTIVES

Team members must demonstrate the ability to:

1. Design an Agile documentation system in Notion

2. Document Scrum artifacts clearly and concisely

3. Maintain traceability from Product Goal → Backlog → Sprint → Increment

4. Capture decisions, risks, and changes without slowing delivery

5. Support collaboration and transparency for stakeholders

At the end of the capstone, team members must produce:

1. A Complete Notion-Based Agile Workspace

Containing:

• Product vision & goals

• Scrum artifacts

• Sprint documentation

• Decision and risk logs

• Release and retrospective documentation

2. A Live Demonstration & Explanation

• 10–15 minutes per team

• Walkthrough of how documentation supports agility

DETAILED EXECUTION PHASES

These phases give you a step-by-step guide on how to achieve your deliveries, teams
are expected to take note of the required sections to satisfy the assessment focus.
Teams are encouraged to do research to get more insight into how to accomplish these
phases. To effectively use Notion advance features, check out the Notion reference
page.

[Link]/help/reference

PHASE 1: Agile Workspace Setup

Task 1: Create the Product Home Page

Required Sections:

• Product Name: PayFlow

• Product Vision
 • Target Users

• Product Goal (per Scrum Guide)

• Release Objective (MVP)

• Current Sprint

• Quick links to Scrum artifacts

Assessment Focus:

• Simplicity

• Clarity

• Agile mindset (no over-documentation)

Task 2: Define Agile Documentation Principles

Team members must create a page titled:

“Agile Documentation Guidelines – PayFlow”

Must include:

• What will be documented

• What will not be documented

• Ownership of each artifact

• Update cadence (per sprint)

Key Question:

“Does this documentation help the team deliver value?”

PHASE 2: Product Vision & Backlog

Task 3: Product Vision & Roadmap

Team members must document:

• Value proposition

• MVP definition

• High-level release roadmap (now / next / later)

Task 4: Product Backlog (Notion Database)

Required Properties:

• User Story

• Priority

• Business Value

• Story Points

• Acceptance Criteria

• Status

Mandatory User Stories:

• As a merchant, I can accept card payments

• As a merchant, I can view daily sales

• As a merchant, I can generate invoices

• As an admin, I can manage users

PHASE 3: Sprint Planning & Sprint Documentation

Task 5: Sprint Planning Documentation

Team members must create:

• Sprint Goal

• Selected backlog items

• Dependencies and assumptions

Sprint Length: 2 weeks

Mid-Sprint Twist

The payment provider API introduces new compliance requirements.

Team members must:

• Update backlog items

• Adjust Sprint Goal (if needed)

• Document decision trade-offs

PHASE 4: Execution, Decisions & Risk Tracking

Task 6: Sprint Execution Logs

Team members must document:

• Daily Scrum notes (lightweight)

• Blockers

• Key technical decisions

Task 7: Decision Log

Scenario:

The team must choose between faster delivery or stronger fraud detection.

Team members must document:

• Options considered

• Decision made
 • Rationale

• Impact on product quality

Task 8: Risk & Dependency Log

Required risks:

• Payment provider downtime

• Regulatory changes

• Performance bottlenecks

Each risk must include:

• Likelihood

• Impact

• Mitigation

• Owner

PHASE 5: Increment, Review & Stakeholder Feedback

Task 9: Sprint Review Documentation

Team members must document:

• Delivered increment

• Stakeholder feedback

• New backlog items created

Assessment Focus:

• Transparency

• Traceability

• Responsiveness to feedback
PHASE 6: Retrospective & Continuous Improvement

Task 10: Sprint Retrospective

Team members must document:

• What went well

• What didn’t

• Action items for improvement

Constraint:

• At least one process improvement must be logged and carried forward

PHASE 7: Release Readiness & Knowledge Transfer

Task 11: MVP Release Notes

Team members must create:

• Feature summary

• Known limitations

• Support notes

• Future backlog highlights

Task 12: Knowledge Base Setup

Team members must document:

• Architecture overview (high level)

• Key integration points

• Onboarding notes for new developers