Common Workflows

ClientFlow is a CRM built into GitScrum for agency owners. It centralizes client relationships, proposals, invoices, and change requests in one place.

Access ClientFlow from the sidebar. The Dashboard shows total revenue, pending invoices, active proposals, and recent client activity.

Creating a Client

Open ClientFlow and select Clients. Click Create Client and enter the company name, contact person, email, and billing address. Clients can be linked to one or more projects for tracking billable work.

Sending a Proposal

Go to the Proposals section and create a new proposal. Add deliverables, timeline, and pricing. GitScrum generates a public link for client review. Clients can approve and sign proposals electronically without logging in. The proposal status updates automatically when signed.

Generating Invoices

Create invoices from the Invoices section. Link time entries from project tasks to show billable hours. Add fixed-price line items if needed. Send the invoice via email or share the payment link. GitScrum tracks payment status and sends reminders for overdue invoices.

Handling Scope Changes

When a client requests changes outside the original scope, create a Change Request. Document the requested change, cost impact, and timeline adjustment. Send for client approval before starting work. Approved change requests link back to the original proposal for audit trail.

ClientFlow is available only to users with the Agency Owner role. Managers and developers cannot access financial data.

Developers work primarily on the Kanban board and with time tracking. This workflow covers a typical day from start to finish.

Morning Check

Open the Kanban board from your project. Tasks assigned to you appear highlighted. Check the In Progress column for any tasks started yesterday. Review new tasks in the To Do column that may have higher priority.

Starting Work

Drag a task to In Progress. Before writing code, start the time tracker. Click the timer icon on the task card or use the status bar timer. The timer runs until you stop it, logging time automatically.

During Development

Add comments to tasks as you work. Attach screenshots, code snippets, or links to pull requests. If you find blockers, mention team members in comments. GitScrum sends notifications so they respond faster.

Code Review

When code is ready for review, move the task to the Review column. Link the pull request in the task description. Reviewers see the task status change and can check your work.

Completing Tasks

After approval, move the task to Done. Stop the time tracker. The time entry stays linked to the task for billing and reporting.

Using VS Code Extension

Install the GitScrum extension for VS Code. The status bar shows a timer you can start and stop without leaving the editor. The sidebar shows your tasks across all projects. Open the Board panel to drag tasks between columns. All changes sync with the web app instantly.

Sprints organize work into time-boxed iterations. GitScrum supports sprint planning, estimation, and tracking with burndown charts.

Creating a Sprint

Go to the Sprints section in your project. Click Create Sprint and set the start and end dates. Typical sprints run 1 to 4 weeks. Give the sprint a name that reflects the main goal.

Building the Backlog

User Stories live in the backlog until assigned to a sprint. Create user stories with clear acceptance criteria. Group related stories under Epics for larger features. Prioritize the backlog by dragging stories up or down.

Estimation

Use story points to estimate complexity. GitScrum includes Planning Poker for team estimation. Create a planning session and invite team members. Each person votes on story points independently. Reveal votes simultaneously to avoid anchoring bias. Discuss outliers and revote until consensus.

Sprint Planning Meeting

During the planning meeting, drag stories from the backlog to the sprint. The sprint capacity shows how many points the team can handle based on historical velocity. Avoid overcommitting. Assign stories to developers based on skills and availability.

Daily Standups

The Team Standup feature captures daily updates. Team members answer three questions: what they did yesterday, what they plan today, and any blockers. Standup notes are visible to the entire team and can be reviewed later.

Sprint Execution

During the sprint, the burndown chart shows remaining work. Update it daily by completing tasks. If a story cannot finish, move it to the next sprint rather than extending the current one.

Sprint Review and Retrospective

At sprint end, review completed work with stakeholders. Document retrospective notes in the Wiki for future reference. Close the sprint to lock it from further changes.

Time tracking connects developer work to agency billing. Every minute logged links to a task, project, and client.

Starting the Timer

Click the timer icon on any task card. The timer runs in the background while you work. You can also start the timer from the VS Code extension status bar. The running timer appears in both the web app and VS Code.

Manual Time Entry

For work done offline or forgotten timers, add manual entries. Go to Time Tracking in the project sidebar. Click Add Entry and specify the task, date, and duration. Add notes to describe what you worked on.

Reviewing Time

Managers can view all time entries from the workspace Time Trackings section. Filter by project, team member, or date range. Export reports as CSV for external billing systems.

Billing Workflow

Agency owners create invoices in ClientFlow. When creating an invoice, select a project and date range. GitScrum imports all logged time entries for that period. Review entries and adjust if needed. Add your hourly rate to calculate totals. Send the invoice to the client directly.

Reports

The Reports section shows time distribution across projects. See which clients consume the most hours. Identify developers with unusual time patterns. Use reports for capacity planning and pricing adjustments.

GitScrum provides multiple ways for teams to communicate without leaving the platform.

Discussions

Every project has a Discussions section. Create discussion threads for decisions, brainstorming, or announcements. Team members receive notifications for new discussions and replies. Pin important discussions to the top for visibility.

Wiki

The Wiki stores persistent documentation. Create pages for onboarding, coding standards, architecture decisions, and meeting notes. Wiki pages support markdown formatting. Version history tracks all changes.

Documents

Upload files in the Documents section. Store design files, contracts, specifications, and assets. Files are organized by project and accessible to all team members.

NoteVault

NoteVault provides personal note-taking space. Notes are private by default. Use it for meeting notes, task planning, or brainstorming before sharing with the team.

Comments and Mentions

Every task supports comments. Mention team members with @ to notify them directly. Attach files, screenshots, and code blocks to comments. Comments thread under tasks for context.

Notifications

GitScrum sends notifications for assignments, mentions, due dates, and status changes. Configure notification preferences in account settings. Notifications appear in the app and optionally via email.

Agencies typically create one workspace containing all client projects. This structure keeps everything organized.

Workspace Setup

Create a workspace for your agency. The workspace contains all projects, team members, and settings. Go to Settings to configure workspace name, billing, and integrations.

Creating Projects

Each client or engagement becomes a separate project. Create projects with clear names that identify the client and work type. Set project visibility to control who sees it.

Team Roles

Assign roles when inviting team members. Agency Owner has full access including billing and ClientFlow. Manager can create and manage projects but not access billing. Developer works on assigned tasks only. Client role has read-only access to their project.

Project Settings

Configure each project independently. Enable or disable features like Sprints, Time Tracking, and Wiki. Create custom Kanban columns for your workflow. Add labels for task categorization.

Manager Overview

The Manager Overview in the workspace dashboard shows health metrics across all projects. See which projects are on track, at risk, or blocked. Monitor team velocity and workload distribution.

Stats by Project

View detailed statistics for each project. Track tasks completed, time logged, and sprint velocity. Use stats to estimate future work and set client expectations.

The GitScrum VS Code extension lets developers stay in their editor. All essential features work without opening the browser.

Installation

Search for GitScrum in the VS Code extensions marketplace. Install and authenticate with your GitScrum account. Sign in with GitHub, Google, Facebook, or email.

Explorer View

The sidebar shows your workspaces and projects. Expand a project to see tasks organized by status. Click a task to view details in a panel.

Board Panel

Open the Board panel from the command palette or sidebar. The full Kanban board appears inside VS Code. Drag tasks between columns. Create new tasks. Changes sync immediately.

Time Tracking

The status bar shows a timer. Click to start or stop tracking time on the current task. Switch tasks without losing logged time. View all time entries in the Time Tracking panel.

Sprints and User Stories

View sprints and user stories in dedicated panels. See the current sprint progress and remaining stories. Add new stories directly from VS Code.

Wiki and Discussions

Read wiki pages and discussions without leaving the editor. Reference documentation while coding. Reply to discussions from the panel.

Create Project

Create new projects from VS Code using the command palette. The extension handles authentication and setup. New projects appear in the explorer immediately.

Recurring tasks automate repetitive work. Set them up once and GitScrum creates new tasks on schedule.

Creating Recurring Tasks

Go to Recurring Tasks in the workspace settings. Create a task template with title, description, and assignee. Set the recurrence pattern: daily, weekly, monthly, or custom intervals.

Use Cases

Weekly status reports. Monthly invoicing reminders. Daily backup verification. Sprint retrospective setup. Security review checklists.

Execution

GitScrum creates new tasks based on the schedule. Tasks appear in the backlog or specified column. Assignees receive notifications. Complete tasks normally.

Managing Recurrence

Edit recurring tasks to change the pattern or content. Pause recurrence without deleting the template. Delete if no longer needed.