Our organization recently adopted SharePoint and our team is tasked with maintaining the platform itself but also to develop solutions using SharePoint.
I initially set up JIRA so that the SharePoint product is one project and all solutions we develop are their own respective projects. I created a category called SharePoint so I could report across all our initiatives.
We have one scrum team to perform all the work, so I created a scrum board for the SharePoint category as opposed to one per project. This way, we see everything we need to do in one place and our platform owner can prioritize our work for us.
The challenge we are facing is versioning. At the end of our sprint, we deploy a package. Custom code, content, configuration files. We would like to version that package but versions are not associated to categories.
Should we just have one giant project and use components to list all the solutions built in it?
What are the best practices for platform projects like this?
Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk! We’d love to hear your thoughts on the pros and ...
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