Siirry sisältöön

Evästeasetukset

Käytämme evästeitä varmistaaksemme sivuston perustoiminnot ja parantaaksemme sen käyttökokemusta. Voit määrittää sallimiesi evästeiden käytön ja muokata näitä asetuksia milloin tahansa.

Välttämättömät

Mieltymykset

Analytiikka ja tilastot

Markkinointi

Muutokset kohteessa "Secosol Website"

Profiilikuva: Kei M Larios Kei M Larios

Kuvaus (English)

  • -<p>Every time you have a report please put your name, a title for the report, the name of the costumer and in the description out the following report requirements if needed:</p><p>For Most projects developers and business managers will use User stories to report to costumers.</p><p>For developers, there may be some instances where they need to provide proof of work through code reviews and 360* degree review from a colleague.</p><p>Here are some requirements for user stories:</p><ol><li><p>Role: Who needs the feature? ( customer, admin, developer).</p></li><li><p>Goal: What action/outcome does the user want?</p></li><li><p>Benefit: Why is this valuable?</p></li></ol><p>Here are some requirements for Developer-focused reports:</p><ul><li><p><strong>Progress</strong> </p><pre><code>- **Delivered**: [List completed user stories].
  • +<p>(Replace this with the introduction of the project and the user story of this project</p><p>Every time you have a report please put your name, a title for the report, the name of the costumer and in the description use Agile to ensure quality/readability of the report.</p><p>For Most projects developers and business managers will use User stories to report to costumers.</p><p>Here are some requirements for user stories:</p><ol><li><p>Role: Who needs the feature/ Who is working on this project? ( customer, admin, developer).</p></li><li><p>Goal: What action/outcome does the user want?</p></li><li><p>Benefit: Why is this valuable?</p></li></ol><p>For developers, there may be some instances where they need to provide proof of work through code reviews and 360* degree review from a colleague.</p><p>Here are some requirements for user stories:</p><ol><li><p>Role: Who needs the feature? ( customer, admin, developer).</p></li><li><p>Goal: What action/outcome does the user want?</p></li><li><p>Benefit: Why is this valuable?</p></li></ol><p>Here are some requirements for Developer-focused reports:</p><ul><li><p><strong>Progress</strong></p><pre><code>- **Delivered**: [List completed user stories].
  • - **Blockers**: [Bug #123, PR #456].
  • - **Next Steps**: [Prioritize tech debt]. </code></pre></li></ul><ul><li><p><strong>Proof of Work</strong> (File upload/links):</p><ul><li><p>Nextcloud screenshots (CI/CD logs or Deployment proof).</p></li><li><p>Git PR/commit links.</p></li></ul></li></ul>

Vahvista

Kirjaudu sisään

Salasana on liian lyhyt.

Jaa