You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our team at Railsware uses checklists quite heavily in a variety of cases. For example, we use them to automatically add the Definition of Done to ensure that the engineering team knows about the criteria they aim to meet at all times.
Alternatively, we use them to make the Acceptance Criteria much more defined and visible. This way it is not cramped inside the body of the ticket where it gets lost among other details.
Onboarding is yet another example of how a checklist template can make a series or repetitive yet sometimes intricate steps much more manageable.
The list of use cases can easily go on but what I am actually curious about is how do you use checklists in your processes?