I’ve heard variations of this so many times: “What is this even for?”, “Why do we need it?”, “This isn’t my job — I’m not here to sit in tasks.” I’ve heard it both directly from developers and from project managers who constantly complained about their stubborn teams.
And every time, it seemed to me that the real problem wasn’t Jira itself (it’s just a tool, even if not the most user-friendly one), but rather that PMs didn’t have the time to explain why it matters — and developers never really had the chance to understand its purpose.
That’s how the idea was born: to create a simple, lightweight guide for developers on how to work with this mysterious creature — not in theory, but specifically for our project. And most importantly, to explain why using it properly matters, especially in the context of distributed (outsourced) development.
This presentation is now used to onboard all new team members at The Outsource Band (Art outsource and co-development studio).
Thank you.
