Currently I work on an 80+ person project. The project is made up of roughly 10 teams. 70% of the teams have some overlap with another team (i.e. a tools team supporting a feature team, etc.). I wanted to know the following:
Thank you for your time.
Update: I don't have enough points to respond to two comments.
Thanks for the quick reply. I will try to provide as much info as possible:
1. Currently we have Jira Agile and Confluence. I was hoping that these two products would be able to handle our current project management needs. Also although we already have both products, only a portion of the company is a actually using them. The rest of our team uses various tools and methods for project management and since each team has a dedicated PM, we are able to source high level data reliably - but not necessarily easily.
2. Since many teams track and manage their projects in a way that works best for them, I was hoping that when they interact with Jira there wouldn't be an immediate feeling of another team's style existing within their own project management tool or a feeling of strict usage expectations.
3. Another concern is that in order to adopt portfolio, it seems like our account with have to adopt portfolio, which requires approval from our admin. Right now I am just doing the preliminary work of identifying potential structures and use cases for our upcoming project.
4. The main needs that we have are: a unified source for documentation, the ability for vertical teams to just focus on their own items but also see the status of potential dependencies down the line, the ability to easily see an overall project roadmap and whether we are on track, and the ability to present a restricted view of a subset of all of this info for relevant external parties with either a dashboard a file export.
Based on Steve's answer below, it seems like some of this may be accomplished by:
1.Backlog : Having a master backlog for the project but using filters based on boards to hide irrelevant info.
2. Sprints: Since they are tied to boards, having boards represent teams would hide other teams sprints. Is this right, I may be confusing myself here?
3. Internal Dashboard: The seems pretty straightforward.
4. External Dashboard: Would this be a separate project?
Please let me know if this helps. I really appreciate your time.
Sure, you can do all of this in JIRA. The big deal is just setting it up so it's flexible for your teams AND keeps your data 'clean.'
Hey Christopher, would you mind sharing a bit more on why you don't think you'll get Portfolio? It seems like a prime usecase for it - do you see functional blockers, or rather a financial decision to buy an extra add-on? Particularly with the new integration with JIRA Software we are currently building out (see my talk from Summit for some more details on what we're working on http://summit.atlassian.com/videos/featured/portfolio-for-jira) this should be easy to set up across different teams' boards. Any input that helps us learn and improve would be greatly appreciated!
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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