Hey folks, I’m trying to wrap my head around the Agile process using Jira and Greenhopper. I’ve done some research, but I’m still confused about the best way to set things up.
From what I understand, we start with Stories and Epics. But I’m not sure about the next steps:
- Do we create a story or epic first with a non-technical description?
- Should we add subtasks to the story? Right now, I only have technical subtasks.
- For actual development work, do we make new tickets (bugs, features, etc.) and link them to the story?
This is how I think it works, but I have a couple of questions:
- If we’re making separate development tickets and linking them, what’s the point of subtasks in a story?
- Is there an easier way to create dev tickets in Greenhopper? Or do we have to make them separately and then link them?
I’d really appreciate some clarity on this. Thanks in advance for any help!
I’ve been using Jira and Greenhopper for a few years now, and I’ve found that flexibility is key. While there’s no one-size-fits-all approach, here’s what works well for my team:
We start with epics to outline major features or objectives. Then we break these down into stories, focusing on user value. For development work, we use subtasks within stories. This keeps everything organized and traceable.
We rarely create separate dev tickets. Instead, we use story points on subtasks to estimate effort. This approach simplifies our workflow and reporting.
Greenhopper’s board view is great for creating and managing stories and subtasks on the fly. It takes some getting used to, but it’s a real time-saver once you’re familiar with it.
Remember, the goal is to make the tools work for you, not the other way around. Experiment and find what suits your team best.
hey neo_stars, i’ve been using jira for a while now. from my experience, start with epics first, then break em down into stories. subtasks are great for dev work within a story. no need for separate tickets usually.
greenhopper can be tricky but once you get the hang of it, it’s pretty smooth. just create stories and subtasks directly in the board view. hope this helps!
In my experience with Jira and Greenhopper, the workflow benefits from a clear hierarchy. Typically, epics are created first to set broad objectives, and stories follow to define more granular tasks. Technical work is best handled as subtasks within these stories, which helps avoid redundancy by reducing the need for extra development tickets. The key is to leverage Jira’s flexibility to adapt the process to your team’s needs. Although Greenhopper may seem complex initially, a steady approach to its board view usually leads to a more streamlined setup.