Still waiting for answers from Atlassian...can anyone leapfrog? My note, below, after they responded they don't have traditional sales teams:
I reviewed the Portfolio demo videos and have a few questions, in addition to understanding whether I can connect with a Project Director/PMO representative at a current client using Portfolio to better understand the capabilities as a governance tool (explicit vs. implicit capabilities). Would you be able to provide that, or would I just post the request in a forum?
Initial questions, after viewing the demo would appear that data integrity is a critical component for the success of the product feature/functionality, specifically – can we manage projects and the portfolio without MSFT Project? To that point:
1. Is there a limit to the number of teams a team member can be assigned to?
2. Is there a limit to the number of sprints a team can run concurrently and how is that rolled up? Must all sprints be defined and team member time / capacity split among each? Objective: one JIRA project, one organizational team, multiple sprint teams within the organization team
3. What role configurations are included in Portfolio? In other words, who can enter team members and time for capacity planning (can that be restricted, if so, how)?
4. For individual capacity planning, does the tool compare the time available for the team member to the sigma hours estimate and remaining in factoring capacity per individual? Objective: resource optimization
5. For team capacity planning, does the tool roll up 3, to the team(s) level? Objective: resource optimization
6. What type of historical trending reports are available (look back) as well as forecasting reporting at the epic, team, teammate, project level? What data is required to ensure accurate reporting?
7. How are tasks associated with fixed milestones and does the tool notify (or can be configured out of the box) for milestones that appear at risk?
8. Does the tool enable variable work days (e.g. default, I assume, is 8 hours – would like to adjust to 6 hrs – is that possible, if so how?)
9. What is the process for a single team, under one JIRA project, to execute against a scrum and Kanban process simultaneously? In the demo, they were separate options – would like the ability to combine within a sprint.
a. Additionally, if it’s allowed, how are Kanban hour estimates considered in individual team capacity and committed tasks (against sprint, project, epic, portfolio)?
b. What are the “traditional” methods supported, referenced in the demo and where can I find more information on support via Portfolio?
10. How are dependencies across tasks, or predecessors / successors monitored (with JIRA out of the box links)? Is there any alerting (out of the box) or enforcement of those (like MSFT project)?
11. What type of financial reporting is available within Portfolio (e.g. resource costs)? In general, what enhanced reporting does the tool provide to enable impact analysis and decisions at the portfolio level?
12. Does the tool support any DRE, actual to planned reporting (sprint execution, for example – churn is a big issue, as well as completion of committed tasks or fixed date)?
13. Does this tool provide sync capabilities to any non-Atlassian code review/QA systems and, if so, is that integrated (OOTB) into reporting?
Assuming this is designed, in part to support capabilities companies are using in MSFT Project, so do you have a compare contrast data sheet between the two products?
Before I install and embark on a trial, I need to understand the data set up that JIRA must have to support portfolio (e.g. use of epics, projects, jira issue types, issue type schemas, workflows et al. As typical, standards are typically light in JIRA, so what is the minimum viable requirement to ensure Portfolio will function optimally?
