The latest articles on DEV Community by Fabian (@iamfabs). https://dev.to/iamfabs https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F400088%2Faa1d7d3d-e312-477f-8a89-043394dbf556.jpg https://dev.to/iamfabs en Fabian Mon, 01 Feb 2021 20:01:15 +0000 https://dev.to/iamfabs/definition-of-ready-dor-and-definition-of-ready-dod-templates-2bdh https://dev.to/iamfabs/definition-of-ready-dor-and-definition-of-ready-dod-templates-2bdh <p>Defining when a task can be started or when the task is completed is a basic activity that helps the development team to control the flow of tasks and avoid getting stuck when requirements are not clearly defined. It also prevents sending uncompleted changes into the development branch</p> <h2> Definition of ready DOR </h2> <p>First definition helps the team to validate if a task is ready for starting the development. Next is a basic list of validations than can help the team determining if a task has the necessary information:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>├── Is ready to start? │ └── acceptance criteria is correctly described? │ ├── If is a user interface, are the prototypes well defined and the gherkins written? │ ├── If is an API, are all the entities and their attributes defined? │ └── if (task cannot be started) │ ├── add a comment │ ├── move to parking lot │ ├── assign to the person responsible for solving │ └── end ├── update task status │ ├── check estimated story points │ ├── move the task to in progress │ ├── create branch to work │ └── create a pull request └── end </code></pre> </div> <h2> Definition of done DOD </h2> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>├── basic validation │ ├── follows TDD required structure? │ ├── do structure follows CQRS structure? │ ├── were all requirements completed? │ ├── follows the required graphical design? │ ├── are transactions tracked in AI? │ └── are resources translated? │ └── was static code analysis performed? ├── before sending a pull request │ ├── validate that all automated tests are working │ ├── static code analysis passing │ ├── format code if needed │ ├── check comments grammar │ ├── remove any commented code │ └── remove visual studio warnings ├── developer test environment validation │ ├── commit changes │ ├── merge changes from the integration branch │ └── send pull request </code></pre> </div> Fabian Wed, 01 Jul 2020 18:01:40 +0000 https://dev.to/iamfabs/scripts-for-using-agile-with-a-team-2i0m https://dev.to/iamfabs/scripts-for-using-agile-with-a-team-2i0m <p>Defining when a task can be started or when the task is completed is a basic requirement that helps the development team to control the flow of tasks and avoid getting stuck when requirements are not clearly defined</p> <h2> Definition of done DOR </h2> <p>First definition helps the team to validate if a task is ready for starting the development. Next is a basic list of validations than can help the team determining if a task has the necessary information:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>├── Is ready to start? │ └── acceptance criteria is correctly described? │ ├── If is a user interface, are the prototypes well defined and the gherkins written? │ ├── If is an API, are all the entities and their attributes defined? │ └── if (task cannot be started) │ ├── add a comment │ ├── move to parking lot │ ├── assign to the person responsible for solving │ └── end ├── update task status │ ├── check estimated story points │ ├── move the task to in progress │ ├── create branch to work │ └── create a pull request └── end </code></pre> </div> <h2> Definition of done DOD </h2> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>├── basic validation │ ├── follow TDD required tests? │ ├── do structure follows CQRS structure? │ ├── test that every jira requirement was completed? │ ├── follows the required graphical design? │ └── are resources translated? │ └── was static code analysis performed? ├── developer local tests │ ├── validate that all automated tests are working │ ├── check static code analysis results │ ├── format code if needed │ ├── check comments grammar │ ├── remove commented code │ ├── remove visual studio warnings │ └── test with other required services ├── developer test environment validation │ ├── commit changes │ ├── merge changes from the integration branch │ ├── remove static analysis reported errors │ └── send pull request │ └── basic integrated tests </code></pre> </div> agile