Theme

Tracking process

Written by

in

(синяя звезда) Time Doctor / Jira integration

  • Integrate Time Doctor with Jira using following instructions https://cheitgroup.atlassian.net/l/cp/RK7J0pns

  • PM must make sure all devs, QA from your teams completed the integration and using TD tracking in Jira and give integration instructions for new people in the team

For Chrome users is recommended to install the plugin – TimeDoctor Classic, it helps to track time directly in the issues without switching applications

  • During Issue goes through the Workflow, it should be assigned to the specific person and set with current status before start tracking

  • In some specific cases, time from the issue could be edited manually in the TD – Edit time

(синяя звезда) Planning & Reporting

  • Each project should be divided by Sprints (exception is some unstable Support projects)

  • Planning meeting should take place at the beginning of each Sprint

Sprint planning meeting:

  • The whole team should be invited to the meeting – dev, QA, PM, stakeholders (if needed)

  • Sprint goals should be discussed, presented by PM (if it’s a beginning of the new project, additional meeting with tasks decomposition, estimation, Sprints planning is required)
    *Link for the Start Project doc would be added soon

  • Each Issue MUST contain: Description, Links / Screenshots, Original Estimated time*, QA Scope (Acceptance Criteria), Sprint, Assigned person before Sprint starts
    *Pay attention that Original Estimated time for each Issue includes Dev, QA, Code Review, PM time (in some cases this time could be divided in separate tasks for each role)

  • PM should make sure that each team member understands the Scope

  • Sprint time should be set up (1-2 weeks, depends on Project’s estimated time)

  • Each Sprint should also contain at least 3 Communication tasks (if needed for each team member separately as sub-tasks): Communication with the Client, Daily Meetings, Tasks Discussions / Communication with the team AND all time should be tracked by each team member in these Issues

  • Tasks for QA in some cases could be created separately, but MUST be included to the Sprint

  • PM can start Sprint when all above steps are completed

  • All additional issues could be added to the Sprint ONLY by PM

  • PM’s responsibility is to check each Issue progress, time spent and control the Project’s budget; dev/QA MUST communicate all risks related to the “In Progress” Issue, including over-budgeting on Daily meetings
    *For easier monitoring, we are working on the Reports system – will be presented soon

  • PM should communicate all risks to the Client ASAP

(синяя звезда) Tracking rules for the team

  • (синяя звезда) The whole time spent on the Project should be added to the Project

  • All tasks should be added to Jira and tracked through the TD/Jira integration, avoiding manual creation of the tasks by dev/QA
    Please notice that project in TD would be created automatically and named JIRA: Name_of_Project

  • The whole dev, QA, PM work on task MUST be tracked to the specific Jira Issue

  • When Dev, QA starts to work on the Issue by getting acquainted with the Issue – it should be tracked to the specific Issue

  • If there is no left tasks in the Sprint, dev/QA should communicate it in the Project’s channel; if there is no tasks which could be assigned to the dev/QA PM should notify the #pm channel
    In the meantime dev/QA could track their time in Design&Development (this project is only for internal company tasks)

  • Daily meetings must be tracked in “Daily meetings“ task, created for each Sprint by each team member

  • Calls / communication in Slack with team regarding tasks must be tracked in the “Tasks Discussions / Communication with the team“, created for each Sprint by each team member

Comments

Leave a Reply

More posts