Project Workflow

The AngusTester Project Workflow provides an end-to-end R&D test management solution, covering the entire lifecycle from project creation to results reporting, helping teams achieve efficient collaboration and quality assurance.

Closed-loop Workflow Mechanism

Key Control Points:

1. Daily Standup: Sync progress/identify blockers
2. Iteration Review: Demo deliverables/collect feedback
3. Quality Gate: Code review/test coverage check
4. Milestone Audit: Phase deliverable acceptance

Complete Project Workflow

1. Create Project

Overview

Establish project framework, define management boundaries and resource allocation to provide structural support for subsequent processes.

Steps

1. Navigation Entry
   After login, go to Projects → Add Project

2. Create Project

   • Click "Add Project" button
   • Select project template (Agile/General/Testing)
   • Fill required fields: Project Name, Assign Owner, Timeline, Team Members
   • Enter project description (within 2000 characters)

3. Basic Configuration

   • Define software modules for task organization
   • Set project classification tags (e.g., Web/Mobile)
   • Plan target versions (e.g., 1.0.0, 2.0.0)

⚠️ Critical Settings:

• Project names must be unique
• Must assign project owner initially to ensure completion and progress control (e.g., issue resolution, progress tracking, team coordination)

2. Plan Iteration & Testing

Overview

Develop executable work plans, clarify task allocation and acceptance criteria, establish quantifiable goal systems.

Steps

1. Create Iteration Plan

   • Enter project details page
   • Click "Add Iteration"
   • Set iteration cycle (recommended 2-4 weeks)
   • Define iteration goals (SMART principle)

2. Develop Test Plan

   • Click "New Test Plan" in testing module
   • Configure:
     • Test scope (functional modules)
     • Test types (functional/performance/security)
     • Entry/exit criteria
     • Risk assessment matrix

3. Task Breakdown

   • Use WBS (Work Breakdown Structure) tool
   • Create main tasks → Break down subtasks
   • Set task dependencies
   • Assign owners and deadlines

⚠️ Best Practices:

• Limit task workload to ≤3 person-days
• Add buffer time for critical path tasks

3. Execute R&D Testing Activities

Overview

Implement planned tasks, monitor progress and quality in real-time, ensure deliverables meet acceptance criteria.

Key Operations

1. Task Execution

   • Developers: View tasks in "My Tasks"
   • Testers: Execute assigned test cases
   • Daily status updates (In Progress/Blocked/Completed)

2. Defect Management

   • Click "New Defect" when found
   • Complete:
     • Reproduction steps
     • Severity (Critical/Major/Minor/Suggestion)
     • Impacted module
   • Assign fix owner

3. Requirement Control

   • Initiate "Change Request" for requirements change
   • Assess impact scope (tasks/timeline/resources)
   • CCB (Change Control Board) approval

4. Test Execution

   • Execute test cases per plan
   • Record results (Pass/Fail/Blocked)
   • Link failed cases to defect tickets

⚠️ Quality Redlines:

• Critical defects must be resolved before release
• Daily builds must pass smoke tests

4. Generate Project Reports

Overview

Consolidate project data, conduct performance analysis and knowledge retention, support continuous improvement decisions.

Process

1. Progress Report

   • Go to "Report Center"
   • Select "Project Progress" report type
   • View:
     • Milestone completion rate
     • Task completion trend
     • Critical path status

2. Quality Analysis

   • Generate "Quality Report"
   • Key metrics:
     • Defect density (defects/1k LOC)
     • Defect resolution cycle
     • Test coverage

3. Performance Evaluation

   • Export "Team Performance" report
   • Analyze:
     • Requirement throughput
     • Resource utilization
     • Schedule variance rate

4. Knowledge Retention

   • Archive project documents:
     • Requirement specifications
     • Test case library
     • Defect analysis reports
   • Create lessons learned repository

⚠️ Reporting Requirements:

• Finalize report within 3 days post-project
• Key metrics must include benchmark comparisons