Practical tips for establishing distributed teams in QPack

This post describes the steps required for building your team

System Setup

Define workflows

Fro requirements, tasks, defects, etc.

Define work items layout

Build each work item layout – means the attributes for each work item

Define groups

Define the groups and groups permissions such as Project manager, Tester, Developer, etc.

Add QPack users

Now you need to add users to the system.

Define the chat permissions when adding user (allow private/public)

Relate users to groups

Relate users to groups. User can be related to several groups (for example, user can be related to Tester and Developer groups, in one project he can be a tester, in another project he can be developer)

Relate users to projects

Now relate users to projects using a specific group (user is connected to project via group)

Manage data sharing and settings

This allows more control of what to expose for each group or each project in terms of applications, modules, work items, fields, etc.

Build filters

For now, filters are added in QPack desktop. Add filters such as All items, My items, My open bugs, etc.

Define email notifications

You can build email templates based on events. Build email template for new bug, or for bug that is fixed and requires verification, all my tasks past due date, etc.

Build filters for end users and filters for managers

Define alerts

Based on the filter – define daily/weekly alerts to notify users on items they need to handle, such as tasks past due date, or open bugs waiting for me

Daily work with QPack collaborative environment

Now, that everything is setup and in place, how do we work on daily basis

The specific working methodology can be different from one company to the other, as one company manage system requirements, and the other doesn’t.

The principals are the same. This is just a basic description of simple process, this article will be updated in the future

  • Add your high level design documents
  • By the workflow – only when a high-level requirement is ready for development (for example, status=”Approved”) – send email notification to development team manager so he will add tasks, and QA team to write test cases
  • Add tasks and assign them to developers
  • Developers perform tasks and mark as finish
  • When all tasks finished for specific requirement – test cases for approved requirements can be executed
  • If bugs found – report bugs and assign to developers
  • Developer fix bugs and QA needs to verify bugs again by re-run the test cases

Leave a comment