Found on Hackernoon. We are switching how our department is organized and will need to increase our use of JIRA tickets.
Why we write tickets
- So if we get sick, a teammate can help us out
- To help us decompose our work into small pieces
- As a placeholder for a real-life conversation
- To keep track of how we resolved the issue
- To make our standups effective
- To point out dependencies
- To reflect on the mix/makeup of our work during retros
- Self-discipline. Don’t take on too much. Try to do one thing at a time
Why we DON’T write tickets
- To track our time
- To compete with other team members
- To show managers we’re busy
- To make managing people possible
- To report status, or % complete
- Because Jira is fun to use
- External discipline
More from Seth Godin’s Blog, :
If you’re seeking to create positive change in your community, it’s almost certain you’ll be creating discomfort as well.
Want to upgrade the local playground? It sounds like it will be universally embraced by parents and everyone who cares about kids. Except that you now bring up issues of money, of how much is enough, of safety. Change is uncomfortable.
It’s way easier to talk about today’s weather, or what you had for lunch.
Usually, when we’re ready to launch something, we say, “this is going to help people, this is well crafted, I’m proud of it.”
What’s a lot more difficult (but useful) is to say all of that plus, “and this is going to make (some) people uncomfortable.”
We try more to profit from always remembering the obvious than from grasping the esoteric. It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent.”