...
Definition of Done Example:
You Type | You Get |
|---|
| Code Block |
|---|
# Definition of Done
- Code produced (all ‘to do’ items in code completed)
- Code commented, checked in and run against current version in source control
- 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 requirements
- Any build/deployment/configuration changes implemented/documented/communicated
- Relevant documentation/diagrams produced and/or updated
- Remaining hours for task set to zero and task closed |
|  Image Modified |
Acceptance Criteria Checklists
...
Acceptance Criteria Example:
You Type | You Get |
|---|
| Code Block |
|---|
# Acceptance criteria
- **Given** my bank account is in credit, and I made no withdrawals recently,
> **When** I attempt to withdraw an amount less than my card's limit,
> **Then** the withdrawal should complete without errors or warnings |
|  Image Modified
|
User Story Implementation Plan Checklists
...
You have a defined list of things that have to be performed on a task.
You are involved in handling the repeatable tasks/processes.
You work with a lot of data that has to be processed (collected or analyzed).
You are looking for a good way to better organize your tasks and keep track of their progress.
The steps you have to complete as part of the project or task do not require going into details and so - creating subtasks.
ToDo List Example:
You Type | You Get |
|---|
| Code Block |
|---|
# 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 |
|  Image Modified
|
Release Checklist example:
You Type | You Get |
|---|
| Code Block |
|---|
# Release instructions
## Preparation
+ Add feature permissions
+ Send `internal` announcement with presentation
~ Prepare branch
> * merge feature to master
> * set tag
> * update [changelog](https://www.google.com)
## Deploy
- Deploy master to prod
- Deploy new login page
- Test and confirm successful deployment
- Send `external` announcement to customers |
|
Image Removed Image Added
|
Onboarding is a standard process that happens and repeats every time a new person joins the company. If you are working at an organization with a number of internal policies and procedures in place, most likely that the onboarding process will take time and involve some actions from the Human Resources department. In order to make sure that everything goes well, you can create a Smart Checklist template for Onboarding and use it for every new employee that comes in.
...
Some Smart Checklist customers deploy the tool to handle frequent Service Desk tickets that may arrive once a week. The Smart Checklist user creates a ticket, imports the ready template, and, by checking off every item on the list, ensures that the task is closed on the very day.
...
| Insert excerpt |
|---|
| Get Started |
|---|
| Get Started |
|---|
| name | support-email (checklist-server) |
|---|
| nopanel | true |
|---|
|