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?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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