Actions
action #137834
closedIntroduce a rule or guideline how to communicate clearly who is on the next steps size:S
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"
Updated by tinita about 1 year 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
Updated by okurz 12 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 :)
Updated by livdywan 12 months ago
- Status changed from Feedback to Resolved
New section added to the wiki
Actions