Project

General

Profile

Actions

action #137834

closed

Introduce a rule or guideline how to communicate clearly who is on the next steps size:S

Added by tinita 6 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Organisational
Target version:
Start date:
2023-10-12
Due date:
% Done:

0%

Estimated time:

Description

https://progress.opensuse.org/issues/137834
Introduce a rule or guideline how to communicate clearly who is on the next steps size:S

Motivation

See #136007 . To ensure it's clear in communication, tickets, etc., what can be expected we should communicate clearly who is on the next steps, e.g. who is doing what until when

Acceptance Criteria

  • AC1: The team knows about this suggested best practice and follows it in daily work

Suggestions

  • Discuss with members of the team how to phrase and where to put it
  • Extend https://progress.opensuse.org/projects/qa/wiki/Tools
  • Tell everybody in the team with a link to the wiki
  • Ask our Scrum Master to check that we actually execute our work accordingly
  • Consider examples of great communication or where things are ambiguous
    • A link to an MR or PR on its own (could be ambiguous)
    • "I need to work on another urgent task, putting this back in Workable"
    • "PLanning to make a draft and ask for feedback"

Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure - action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:SResolvedtinita

Actions
Actions #1

Updated by tinita 6 months ago

  • Copied from action #136007: Conduct "lessons learned" with Five Why analysis for network protocols failures on multimachine tests on HA/SAP size:S added
Actions #2

Updated by tinita 6 months ago

  • Target version deleted (Ready)
Actions #3

Updated by okurz 6 months ago

  • Target version set to Ready
Actions #4

Updated by livdywan 6 months ago

  • Subject changed from Introduce a rule or guideline how to communicate clearly who is on the next steps to Introduce a rule or guideline how to communicate clearly who is on the next steps size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #5

Updated by okurz 6 months ago

Extended wiki section https://progress.opensuse.org/projects/qa/wiki/Tools#SLOs-service-level-objectives-internal already. I will leave the other steps to others as a training opportunity :)

Actions #6

Updated by okurz 6 months ago

  • Priority changed from Normal to High
Actions #7

Updated by livdywan 6 months ago

  • Tags set to collaborative-session
  • Status changed from Workable to Feedback
  • Assignee set to livdywan

Let's discuss it together this Thursday 13.00

Actions #8

Updated by livdywan 5 months ago

  • Status changed from Feedback to Resolved

New section added to the wiki

Actions

Also available in: Atom PDF