Our company is an events, paper and digital publishing company (ie not specialist software house!).
We use JIRA and Greenhopper ondemand. We have numerous small, but often complex, projects.
Our problem is knowing how to use stories to best effect. Here's our workflow
The problem is we don't really know what to do with the stories once we have created the tasks - they just seem to get in the way.
Are we missing something?
Please can you suggest the best way for us to utilise stories in the life cycle?
The main thing here is to do away with the Stories right? Either you resolve them or don't include them in the board.
What I can recommend is to do away with the Tasks and use Stories only. Create two boards. One board captures the 1st half of your process/workflow and the 2nd board captures the 2nd part of the workflow.
If that's the case, you don't add stories to the board. You have 2 boards. You can use the Script Runner (https://jamieechlin.atlassian.net/wiki/display/GRV/Script+Runner) add on to create validators on when you can resolve issues based on another issue.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs