Introduction to Sprints

A sprint is like a "work sprint" for teams - focusing on completing a curated set of tasks within 1-4 weeks to deliver usable outcomes.

With AngusTester sprint management, your team will gain:

• ✅ Clearer work planning
• ✅ More efficient team collaboration
• ✅ Faster product delivery
• ✅ Stronger adaptability

What is a Sprint? A Team's "Work Sprint Cycle"

Think of a sprint like cooking a complex dish:

• Preparation phase: Plan this week's menu (sprint planning)
• Cooking phase: Focus on completing a few steps daily (daily work)
• Tasting phase: Invite guests for feedback on weekends (demo)
• Improvement phase: Adjust the recipe based on feedback (retrospective)

Key characteristics of sprints:

Real-world case:
An e-commerce team using AngusTester for sprint management:

• Each sprint lasts 2 weeks
• Delivers 3-5 core features per sprint
• 60% increase in customer satisfaction
• 75% reduction in response time to change requests

Five Core Values of Sprints

1. Clear Planning - Know "What to Do This Week"

Like planning a weekly menu to avoid blind work:

• Monday morning: Team jointly selects tasks (sprint planning)
• Daily follow-up: Standup confirms daily priorities (daily scrum)
• Tool support: AngusTester board visually displays task status

2. Team Collaboration - Harmony Like an Orchestra

Sprints promote cross-functional collaboration:

3. Transparent Communication - Everyone Aligned

AngusTester provides real-time visualization:

• Burndown chart: Shows remaining work
• Daily auto-reports: Email updates on progress
• Mobile notifications: Instant alerts for important updates

4. Flexibility - Pivot When Needed

Sprints make teams agile like surfers:

• Weekly adjustments: Optimize plans based on feedback
• Quick response: Urgent requests can join next sprint
• Risk alerts: Early problem detection

5. Quality Assurance - Deliver Ready-to-Use Outcomes

Each sprint delivers "potentially shippable" results:

• Continuous testing: Features tested upon completion
• Customer acceptance: Real feedback every sprint
• Quality gates: Automated code quality checks

The Four-Step Sprint Cycle

Step 1: Planning Meeting (1-2 hours Monday morning)

1. **Product Owner** → Presents high-priority requirements
2. **Team estimation** → Discuss implementation approaches and effort
3. **Joint commitment** → Agree on delivery goals
4. **Task breakdown** → Split into executable items

AngusTester tip: Use "story point estimation" for quick effort assessment

Step 2: Daily Standup (15 minutes daily)

**Three questions per person:**
1. What was done yesterday?
2. What's planned for today?
3. Any obstacles?

**Standup rules:**
- Start on time (recommended 9:30 AM)
- Stand up (keep it brief)
- Record issues (solve after meeting)

Step 3: Demo (1 hour Friday afternoon)

**Demo content:**
- New feature demonstrations
- Technical breakthroughs
- Test reports

**Participants:**
- Development team
- Product Owner
- Customer representatives
- Other stakeholders

Best practice: Record demo videos for archives

Step 4: Retrospective (30 minutes Friday afternoon)

**Discussion focus:**
- 👍 What went well (keep doing)
- 👎 Problems encountered (improve)
- 💡 Suggestions (action items)

**Outcomes:**
- 1-3 specific improvements
- Assigned owners
- Implemented next sprint

AngusTester feature: Auto-generates retrospective minutes

Sprint Permission Management (Ensuring Data Security)

Permission Scenarios

Scenario	Requirement	AngusTester Solution
Confidential project	Restrict access	Enable "permission control" mode
Cross-team collaboration	Share partial data	Specify sharing scope
Fully open project	Open to all	Default "no permission control"

Three-Step Permission Setup

Access levels:

• 👀 Viewer: View sprint info only
• ✏️ Editor: Update task status
• ⚙️ Admin: Modify sprint settings

Security tip: Enable "operation logs" for sensitive projects

Unique Sprint Management Features

Smart Planning Assistant (TODO)

• Auto-recommendations: Task suggestions based on historical data
• Risk alerts: Identify task dependencies and conflicts
• Balance check: Ensure balanced workload across functions

Real-Time Progress Tracking

Automated Reports (TODO)

• Daily progress summaries
• Sprint completion reports
• Quality analysis briefs

Success Story: E-Commerce Team Sprint Management

Results:

• Completed 6 core features in 2 weeks
• 300% increase in system capacity
• Zero failures during major promotions

Start Your First Sprint Now

Three-Step Quick Start

1. Create sprint

   • Login to AngusTester → Tasks → Sprint module → Click Add Sprint

2. Add tasks

   • Drag tasks from Backlog to sprint
   • Or create new tasks manually

   [Recommendation] Select 5-8 medium-sized tasks for first sprint

3. Start sprint

   • Set start/end dates
   • Invite team members
   • Click "Start Sprint"

Pro tip:

• Treat first three sprints as adaptation period - focus on establishing processes rather than workload
• Sprints aren't sprints, but a team rhythm dance - find your groove

Sprint Field Information

Parameter	Field Name	Type	Required	Length Limit	Description
ID	id	bigint	Conditional	/	Unique sprint ID; mandatory when modifying
Project ID	projectId	long	Yes	/	Parent project ID
Sprint Name	name	string	Yes	≤200	Sprint name
Authorization Control	auth	boolean	No	/	Enable permission control (default false)
Start Date	startDate	datetime	Yes	/	Sprint start time
Deadline	deadlineDate	datetime	Yes	/	Sprint end time
Owner ID	ownerId	long	Yes	/	Sprint owner ID
Task Prefix	taskPrefix	string	No	≤40	Task code prefix
Effort Estimation Method	evalWorkloadMethod	enum	Yes	/	Task estimation method (see below)
Attachments	attachments	list	No	/	Sprint attachments
Acceptance Criteria	acceptanceCriteria	string	No	≤2000	Software delivery conditions
Additional Info	otherInformation	string	No	≤2000	Supplementary information
Sprint Status	status	enum	Read-only	/	See below Sprint Status
Owner Name	ownerName	string	Read-only	/	Owner name
Owner Avatar	ownerAvatar	string	Read-only	/	Owner avatar URL
Meeting List	meetings	list	Read-only	/	Sprint meeting details
Tenant ID	tenantId	long	Read-only	/	Tenant ID
Creator ID	createdBy	long	Read-only	/	Creator ID
Creator Name	createdByName	string	Read-only	/	Creator name
Creation Time	createdDate	datetime	Read-only	/	Creation time
Last Modifier ID	lastModifiedBy	long	Read-only	/	Last modifier ID
Last Modifier Name	lastModifiedByName	string	Read-only	/	Last modifier name
Last Modified Time	lastModifiedDate	datetime	Read-only	/	Last modification time
Task Count	taskNum	long	Read-only	/	Total tasks in sprint
Valid Task Count	validNum	long	Read-only	/	Valid tasks (excluding canceled)
Progress	progress	object	Read-only	/	Progress statistics
Member List	members	list	Read-only	/	Sprint participants

Sprint Status (status)

Enum Value	Description
PENDING	Pending - Not started
IN_PROGRESS	In Progress - Active
COMPLETED	Completed - All tasks done
BLOCKED	Blocked - Cannot proceed due to issues

Effort Estimation Method (evalWorkloadMethod)

Enum Value	Description
WORKING_HOURS	Hours - Actual time estimates in hours
STORY_POINT	Story Points - Complexity-based method for agile