Managing Work in Progress

This guide explains how to track the progress of your tickets, communicate with developers, and handle scope changes during the development process.

Tracking Ticket Progress

Dashboard Visibility

You can monitor the progress of all tickets through the GitStart dashboard:

• Ticket Page: View detailed status updates for individual tickets
• Agent/Instance Homepage: See an overview of all tickets and their current status
• PR Links: Access direct links to associated pull requests in your repository

Ticket statuses automatically update based on PR activity, giving you real-time visibility into the development process.

Communication Channels

In addition to dashboard updates, you’ll receive progress notifications through your configured communication channels:

• Slack/Teams Updates: Regular status updates for important events
• Email Notifications: Alerts for significant status changes
• PR Comments: Technical discussions and clarifications

For more details on communication setup, refer to our Communication and Team Collaboration Guide.

Developer Communication

Clarifications and Questions

When developers need additional information about a ticket:

1. They’ll comment directly on the PR with specific questions
2. You’ll receive a notification in your configured communication channel
3. Your responses help developers stay on track without interrupting their workflow

Timely responses to these inquiries ensure continuous progress and reduce development delays.

Providing Feedback

You can provide feedback at any time through:

• PR comments in your repository
• The shared communication channel
• Direct messages to your Technical Project Manager

For the smoothest experience, we recommend designating a dedicated team member who is familiar with the codebase to respond to developer questions and review PRs promptly.

Managing Scope Changes

Definition of Scope Change

A scope change is any modification to the ticket requirements after it has been assigned to GitStart. This includes:

• Adding new features or functionality
• Removing previously requested features
• Significantly changing implementation requirements

Handling Minor Scope Changes

For small adjustments that can be reasonably accommodated within the current development cycle:

1. Comment on the PR with the requested changes
2. Developers will assess if they can incorporate them without significant disruption
3. If approved, changes will be implemented at no additional cost

Handling Major Scope Changes

For substantial changes to requirements:

1. Create a new ticket with the revised scope
2. This maintains clear tracking of requirements and avoids disrupting ongoing work
3. The cost will be adjusted to reflect the new scope

If maintaining the same ticket is critical, contact your project manager or support@gitstart.com to discuss options for creating a new pull request under the existing ticket.

Best Practices for Efficient Progress

To ensure smooth progress throughout the development process:

• Respond promptly to developer questions and PR reviews
• Be explicit about prioritization and deadlines
• Consolidate feedback to minimize review cycles
• Maintain clear documentation of any requirement changes

For guidance on optimizing your first month of collaboration, see our Optimizing Your First Month guide.

Need Help?

If you have questions about tracking progress or managing scope changes, contact our support team at support@gitstart.com.