We believe JIRA and most other project management tools have evolved from the core use case of issue tracking. While they might be great for tracking issues and ad hoc work items, when it comes to product development, bug tracking is only a part of the equation.
We believe 2 key aspects make product/feature development different.
- Unlike bug tracking, a feature needs to be conceptualized and the form-based interface of these tools make it ridiculously difficult to spec out the requirements for a feature.
- Shipping a feature involves multiple disciplines and rarely follows a single fixed workflow.
Our approach to solving these two problems is,
- A text editor like interface that lets you specify your features and making it super simple to change or update items.
- Multiple boards per project to capture every discipline and the flexibility to move items across these boards as per your use case.
We believe its painfully hard for product teams to plan and ship features using JIRA and that's why we have created Zepel.