My situation, we have a team of 1 analist, 3 front-end developers and 3 back-end developers.
We are going to release next week the first version of a e-commerce website. The first release will contain the basic features of our e-commercice website. This year was our planning not always so clear, but next year we are planning to work more feature-based and releasing (at least) every month.
At this moment we have defined 9 features. We are going to break down each feature in concrete and well defined tasks. The workload/duration of each tasks is limited to max. 2 weeks. This way of working we have a rough estimate how long a feature will take to implement. Before we start implementing a task, we are planning to break down this task in smaller tasks.
But now, how can I map the above situation in Jira.
I hope that you understand my problem and can give me advice in how I should setup/add the above situation in Jira,
Note we have a license of Portfolio.
Nice description of your case! Nevertheless, it will always be difficult to give proper, well founded advise on this with only a small one pager.
Just a few points on your questions:
Hope this helps already. If you are in the process of this, might not be a bad advise to call in some expert consultancy to help you get your process set up right. Always willing to help if needs be.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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