Date: Fri, 29 Mar 2024 14:24:51 +0000 (UTC) Message-ID: <1917885977.3.1711722291981@38937ed3ac6c> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_779321836.1711722291980" ------=_Part_2_779321836.1711722291980 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page is intended to tell you more about the issue=E2=80=99s progres= s by accessing the results from the Agile board view. In addition, they do = not have to worry about leaving one of the DoD criteria out, since the Smar= t Checklist val= idation feature will not allow for the ticket status change while there= is at least one incomplete item on the list. Development teams can use it = to plan their activities, make proper estimations of time and resources tha= t are required for a specific task. Moreover, Smart Checklist enables addin= g details to every item on the list, and so - ensuring that an executor gai= ns a much deeper understanding of the full scope of works.
It is worth mentioning that Smart Checklist allows creating the DoD chec= klist templates and use them across all tickets per proje= ct.
Definition of Done Example:
You Type |
You Get |
---|---|
# Defin= ition of Done - Code produced (all =E2=80=98to do=E2=80=99 items in code completed) - Code commented, checked in and run against current version in source cont= rol - Peer reviewed (or produced with pair programming) and meeting development= standards - Builds without errors - Unit tests written and passing - Deployed to system test environment and passed system tests - Passed UAT (User Acceptance Testing) and signed off as meeting requiremen= ts - Any build/deployment/configuration changes implemented/documented/communi= cated - Relevant documentation/diagrams produced and/or updated - Remaining hours for task set to zero and task closed |
The Acceptance Criteria, in turn, provides a set of clearly defined cond= itions that a system should meet in order to be accepted by a user. The Acc= eptance Criteria can be applied at either Epic, Story, or Feature Level. Qu= ality Assurance specialists can use the Acceptance Criteria checklists as t= he initial information for the creation of detailed test scenarios.
Indeed, it is so easy for a user to make sure that a product is ready fo= r release by going through the Acceptance Criteria list and checking off th= e items that satisfy the previously identified =E2=80=98pass=E2=80=99 resul= ts. Just like Trello, Smart Checklist supports Markdown = syntax formatting, which is very much appreciated by our customers who = are in the process of transferring from Trello to Jira and are looking for = a Jira-based alternative to Trello checklists.
Acceptance Criteria Example:
You Type |
You Get |
---|---|
# Accep= tance criteria - **Given** my bank account is in credit, and I made no withdrawals recentl= y, > **When** I attempt to withdraw an amount less than my card's limit, > **Then** the withdrawal should complete without errors or warnings |
Companies apply the Agile User Story approach in order to review the exp= ectations an end-user has from the system. To define a User Story, the foll= owing formula may be applied: =E2=80=98A user=E2=80=99 wants =E2=80=98this = functionality in order to get this =E2=80=98benefit=E2=80=99. User Stories = facilitate communication across the team and bring in an in-depth understan= ding of the system they are building. Unlike requirements, User Stories are= less formal, providing just a general overview of the feature.
After a User Story is finalized, a dev team creates a detailed Implement= ation Plan, which will include all steps that have to be completed in order= to deliver this Story. In this case, Smart Checklist may be used to docume= nt the core points as checklist headlines, mentionin= g the additional tasks as individual items in the group.
Each User Story item may contain the Acceptance Criteria details which w= ill be checked against by a Product Owner.
Below is the brief list of points that one can review in order to unders= tand whether Smart Checklist is something that you would use at your projec= t:
You have a defined list of things that have to be performed on a task.= p>
You are involved in handling the repeatable tasks/processes.
You work with a lot of data that has to be processed (collected or analy= zed).
You are looking for a good way to better organize your tasks and keep tr= ack of their progress.
The steps you have to complete as part of the project or task do not req= uire going into details and so - creating subtasks.
ToDo List Example:
You Type |
You Get |
---|---|
# ToDo = list - Update lesson states - Final icons based on Client's suggestions - `FE` Prepare icons for Engineer - Additional icon for Photos > Design for classroom details page > Update design for lesson info - See what's up with lesson info with real data - Show how planning is going to work - Get all updated screens approved by Client |
Release Checklist example:
You Type |
You Get |
---|---|
# Relea= se instructions ## Preparation + Add feature permissions + Send `internal` announcement with presentation ~ Prepare branch > * merge feature to master > * set tag > * update [changelog](https://www.google.com) =20 ## Deploy - Deploy master to prod x Deploy new login page - Test and confirm successful deployment - Send `external` announcement to customers |
Onboarding is a standard process that happens and repea= ts every time a new person joins the company. If you are working at an orga= nization with a number of internal policies and procedures in place, most l= ikely that the onboarding process will take time and involve some actions f= rom the Human Resources department. In order to make sure that everything g= oes well, you can create a Smart Checklist template for Onboarding and use = it for every new employee that comes in.
One may also be involved in recurring projects that have to do with
Some Smart Checklist customers deploy the tool to handle frequent