openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-01-18T09:29:47ZopenSUSE Project Management Tool
Redmine QA - action #123289 (Resolved): SUSE Hack Week 22 in the SUSE QE Tools team size:Shttps://progress.opensuse.org/issues/1232892023-01-18T09:29:47Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>SUSE conducts a Hack Week and we should use the opportunity for us in the SUSE QE Tools team efficiently.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Every tools team member has a hack week project</li>
<li><strong>AC2:</strong> Critical roles, e.g. alert duty, are still occupied and executed during Hack Week</li>
<li><strong>AC3:</strong> Results of Hack Week project work by team members have been presented</li>
<li><strong>AC4:</strong> Nobody has to attend regular calls during Hack Week (one can still join e.g. the daily of course)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Ask everybody to think about and decide for a Hack Week project</li>
<li>Optional: Everybody mention their Hack Week project in the ticket (but can also be shared with the team differently)</li>
<li>Ask for volunteers for the critical roles for the Hack Week period</li>
<li>Suggest when and where to present results, e.g. weekly coordination meeting or the Monday after hackweek</li>
<li>Await the presentation of results</li>
<li>Conduct a hackweek daily instead of the non-infra daily</li>
</ul>