Know What Matters.
Cut What Doesn't.
Everything you need to score your backlog with MoSCoW, map value vs effort on the strategic quadrant, manage epics and features, and visualise your roadmap — all in the browser, no install required.
PortfolioInSite Web is a fully browser-based backlog prioritisation and portfolio visibility platform. There is nothing to install — paste a Jira URL or upload a CSV, score your backlog with MoSCoW in minutes, and export results back to your team. All data stays in your browser.
What you get out of the box
- MoSCoW scoring with five weighted criteria across every item in your backlog — Must Have, Should Have, Could Have, Won't Have
- Strategic Map (value vs effort quadrant) with bubble clustering and zoom — instantly see where your portfolio should focus
- Epic and Feature hierarchy view — roll up scores and understand delivery risk across parent work items
- Backlog Health scoring — age, stagnation, type mix, and assignee distribution at a glance
- Roadmap timeline with MoSCoW colour bands — visualise sequencing across teams and quarters
- CSV import from Jira, ServiceNow, Azure DevOps, Advanced Roadmaps, or any standard export
- Full CSV and Advanced Roadmaps export so scored items flow back into your delivery pipeline
Getting Started walkthrough
Video coming soon
⏱ ~2 minutes · Import, score, export
How to get your first backlog scored
Export your backlog from Jira
In Jira, run a board or backlog view filtered to your project. Use the Export → CSV (all fields) option. PortfolioInSite reads Jira's standard column names automatically.
Import into PortfolioInSite
Click the Import button in the tool header. Drag-drop your CSV or paste a URL. The tool auto-detects ID, Summary, Type, Status, Assignee, Story Points, Epic, and Component columns.
Score with MoSCoW
Each item starts Unscored. In the Backlog Triage tab, use the inline score selectors to rate Business Value, User Impact, Strategic Alignment, Time Sensitivity, and Effort Complexity. The weighted algorithm assigns a MoSCoW band automatically.
Validate on the Strategic Map
Switch to Strategic Map to see your portfolio plotted value (Y) vs effort (X). High-value, low-effort items (top-left) are your quick wins — consider re-prioritising if they sit in Won't Have.
Export and share
Use Export CSV (Standard) to get a scored file you can share with the team or re-import. Use Export for Advanced Roadmaps to generate the PI-ready format Jira expects.
💡 Set your Jira URL
Paste your Atlassian site URL in the site bar (e.g. https://your-org.atlassian.net) to make issue IDs clickable — it dramatically speeds up review.
💡 Use the filter bar first
Before scoring, filter to a single component, epic, or assignee. Scoring in focused batches takes 30 minutes vs 2 hours for a full unfiltered backlog.
Full step-by-step guide is in the licensed playbook
Unlock the complete setup guide, scoring calibration tips, Jira export settings, and field mapping reference with a PortfolioInSite Web licence.
Unlock Full Playbook Module overview →PortfolioInSite Web is designed for three distinct roles. Each brings different intent to the same dataset — understanding which lens you're working from helps you focus on the right modules and avoid drowning in data not relevant to your decisions.
Product Owner / BA
Your primary home is Backlog Triage. Score items, manage MoSCoW bands, and maintain the Strategic Map. Focus: getting the right things to the top of the backlog for the next sprint.
Portfolio / Programme Manager
Use Epics & Features and the Roadmap for cross-team visibility. Your goal is ensuring the portfolio is aligned to strategy, and the right epics are being prioritised for PI planning.
Delivery / Scrum Master
Backlog Health is your primary signal. Monitor stagnation, age, and assignee load. Use the Dashboard to track sprint-over-sprint velocity and MoSCoW distribution trends.
Shared capabilities across all roles
- CSV import from any source — Jira, ServiceNow, Azure DevOps, Advanced Roadmaps, or manual entry
- Real-time filter bar — filter by type, status, assignee, epic, component, or MoSCoW band instantly
- Inline editing — update scores, titles, assignees, and status without leaving the triage table
- Dark and light theme that persists across sessions
Backlog Triage is the primary workspace in PortfolioInSite Web. Every imported item lands here, and scoring happens inline — no separate form, no context switching. The table supports full filtering, sorting, bulk operations, and inline editing for all key fields.
What you can do in Backlog Triage
- Score any item with the five MoSCoW criteria — Business Value, User Impact, Strategic Alignment, Time Sensitivity, and Effort Complexity
- Filter the full list by MoSCoW band, type, status, assignee, epic, component, or project using the filter bar
- Click any Jira ID to jump directly to the issue in Jira (requires your site URL to be set)
- Add items manually if they don't exist in your Jira export — useful for risk items, spike work, or ad-hoc requests
- Sort by score, age, effort, type, or any column header — multi-level sorting supported
- Row-level actions: edit inline, delete, or duplicate any item
Backlog Triage screenshot — coming soon
🎯 Score in context
Run a triage session with the PO and a BA together — live scoring in the tool surfaces instant disagreement and drives better backlog conversations than any spreadsheet.
⚠️ Unscored ≠ Won't Have
New imports land as Unscored. Use the Unscored chip filter to work through them systematically — don't let them pile up or they'll distort your MoSCoW distribution charts.
PortfolioInSite Web implements a weighted MoSCoW algorithm across five criteria, each scored 1–4. The combined weighted score determines the MoSCoW band automatically — removing the subjectivity of manual band assignment and making prioritisation auditable and defensible to stakeholders.
Non-negotiable. Must be delivered in the current PI/sprint. Failure to deliver = project failure. Regulatory, safety, or core-function items.
High value and expected, but the project can proceed without it short-term. Will be delivered if capacity allows — strong candidate for next PI.
Nice to have. Positive impact if included but won't be missed if dropped. First items cut when capacity is tight. Used to fill sprint buffers.
Explicitly out of scope for this PI. Not rejected permanently — it signals clear expectation management. Revisit in future PI planning.
| Criterion | What to consider | Score 1 | Score 4 |
|---|---|---|---|
| Business Value | Revenue, cost saving, compliance, or strategic gain | Negligible impact | Critical business outcome |
| User Impact | How much does this improve the user's experience or unblock their workflow? | Minor convenience | Removes a major blocker |
| Strategic Alignment | Does this align to the current PI objective or OKR? | No alignment | Core to the current strategy |
| Time Sensitivity | Is there a deadline, regulatory date, or dependency forcing delivery now? | Flexible timing | Hard deadline or external commitment |
| Effort Complexity | Inverse score — lower effort = higher score (quick wins rank up) | High complexity | Simple, well-understood work |
📐 Calibrate first
Before scoring a full backlog, score 5 representative items as a team. Lock in your 1 and 4 anchors for each criterion — this ensures consistency across hundreds of items.
🔄 Re-score each PI
MoSCoW scores should be refreshed each PI planning cycle. Strategic alignment shifts; what was a Could Have in Q1 may be a Must Have in Q3 after market feedback.
The Epics & Features tab groups your backlog by Epic, rolling up MoSCoW scores across all child items to give you a portfolio-level view of prioritisation. It surfaces delivery risk — epics with a high proportion of Must Have children but low completion rates are your first warning signal.
Key capabilities
- Epic roll-up view — see the MoSCoW distribution (Must/Should/Could/Won't) for every epic's children
- Aggregate score and completion rate per epic — instantly identify which epics are most strategically loaded
- Filter child items by MoSCoW band within an epic — drill into what's blocking or at risk
- Inline epic editing — update epic titles, assignees, and components without leaving the view
- Orphaned items detection — items with no parent epic are flagged for housekeeping
🔍 Look for Must-heavy epics
An epic where 80%+ of children score Must Have is a red flag — either the scoring is uncalibrated or the epic is genuinely critical. Escalate to leadership before PI planning.
🧹 Housekeep orphans
Orphaned items (no epic) accumulate quickly. Run a monthly housekeeping pass to assign them — orphans skew your Backlog Health scores and Strategic Map clustering.
The Strategic Map plots every item on a value (Y axis) vs effort (X axis) quadrant. Items bubble-cluster when they share the same coordinates — hover any bubble to see the cluster contents. The quadrant gives you an immediate visual answer to the question "where should we focus next?"
Reading the quadrant
- Top-left (high value, low effort) — Quick Wins. If these are scored Won't Have, question why — they're your easiest strategic gains
- Top-right (high value, high effort) — Strategic Investments. Must Haves typically live here — they need capacity planning and dependency mapping
- Bottom-left (low value, low effort) — Fill Work. Could Haves and backlog padding. Useful for filling sprint buffers but shouldn't be in Must Have
- Bottom-right (low value, high effort) — Avoid. Any Must Have item in this quadrant warrants an urgent review — you may be building the wrong thing
Strategic Map quadrant screenshot — coming soon
🔍 Zoom to investigate clusters
Large clusters in the bottom-right quadrant are a warning sign. Use the mouse wheel or pinch to zoom in, then hover individual bubbles to identify which items are piling up in low-value, high-effort territory.
🎯 Click to cross-navigate
Click any bubble on the Strategic Map to jump directly to that item in the Backlog Triage tab with the row highlighted — great for live stakeholder sessions.
The Dashboard provides an executive-level summary of your backlog prioritisation state — MoSCoW distribution, score trends, type mix, and assignee workload in a single view. Designed for stakeholder reporting and PI review preparation.
What's in the Dashboard
MoSCoW distribution chart
Stacked bar showing the split of Must/Should/Could/Won't across your entire backlog — and how it changes over time.
Scoring completion rate
What percentage of your backlog has been scored. Target 100% before PI planning — unscored items are invisible to prioritisation.
Type and assignee breakdown
Donut charts showing the distribution of types (Epic, Feature, Story, Bug) and assignees across your MoSCoW bands.
Score distribution histogram
Frequency distribution of raw scores (0–20) to identify scoring cliff effects — a healthy backlog has a bell-curve distribution, not a spike at the extremes.
Dashboard guide is in the licensed playbook
Unlock the full Dashboard guide, chart interpretation tips, and stakeholder reporting templates with a PortfolioInSite Web licence.
Unlock Full PlaybookThe Roadmap renders a Gantt-style timeline of your backlog items coloured by MoSCoW band, grouped by assignee or team. Visualise sequencing, identify scheduling conflicts, and communicate delivery intent to stakeholders — all driven by the scores you've already assigned.
How to use the Roadmap
Set start and due dates
Roadmap bars are driven by start and end dates on each item. Edit these inline in the Backlog Triage tab or import them from Jira's due date field.
Group by assignee or team
Use the group-by selector to switch between assignee lanes (individual workload view) and team lanes (portfolio delivery view).
Filter to MoSCoW bands
Use the band filter to isolate Must Have items only — the cleanest way to present a committed roadmap to leadership without noise from Could and Won't items.
Roadmap guide is in the licensed playbook
Unlock Roadmap configuration, date import tips, and stakeholder communication templates.
Unlock Full PlaybookThe Product Owner view gives POs a personal workspace — a prioritised list of their own items ranked by MoSCoW score, with sprint assignment controls and a capacity bar showing how much of their PI commitment is Must Have vs Could Have.
Product Owner capabilities
Personal backlog view
Filtered automatically to items assigned to the current PO — reducing noise from cross-team items while keeping the full portfolio context available.
Sprint assignment
Drag items into sprint buckets directly from this view — changes reflect immediately in the Backlog Triage table.
PI capacity bar
Visual bar showing Must/Should/Could/Won't item counts and story points against the PI capacity ceiling — immediate visual confirmation of over-commitment.
Product Owner guide is in the licensed playbook
Unlock sprint assignment workflows, capacity planning tips, and PI review preparation guides.
Unlock Full PlaybookBacklog Health analyses your backlog for stagnation, age, orphaned items, type imbalance, and assignee overload — producing a health score that surfaces debt before it becomes a delivery risk. Run a health check before every PI planning session.
Health metrics explained
Age and stagnation
Items that have sat untouched in a To Do or In Progress state for more than N days (configurable) are flagged as stagnant. High stagnation = backlog decay.
Type mix health
A healthy backlog has a balanced mix of Stories, Features, and Bugs. An 80%+ bug backlog is a quality signal; an 80%+ Epic backlog lacks decomposition.
Scoring completeness
Percentage of items with a MoSCoW score assigned. Unscored items are blind spots in your prioritisation — target 100% before PI planning.
Assignee concentration
Items unassigned or heavily concentrated on a single person indicate single points of failure. Health flags when any one assignee holds >40% of Must Have items.
Backlog Health guide is in the licensed playbook
Unlock health score interpretation, remediation playbooks, and pre-PI planning health checklist templates.
Unlock Full PlaybookPortfolioInSite Web accepts CSV exports from Jira, ServiceNow, Azure DevOps, Jira Advanced Roadmaps, and any standard spreadsheet export. The import engine auto-detects common column names and maps them — but knowing the expected format prevents surprises.
Recognised CSV column names
- Issue Key / ID —
Issue key,ID,Key,Ticket,Number - Summary / Title —
Summary,Title,Name,Subject - Issue Type —
Issue Type,Type,Work Item Type,Category - Status —
Status,State,Resolution - Assignee —
Assignee,Owner,Assigned To - Story Points / Effort —
Story Points,Story point estimate,Points,Effort,Size - Epic / Parent —
Epic Link,Epic,Parent,Epic Name - Component —
Component/s,Component,Team
🔑 Story Points required for Effort axis
The Strategic Map's X axis (effort) is driven by Story Points. Items without story points plot at X=0 — score them before using the quadrant for portfolio decisions.
⚠️ Large exports (1000+ items)
For boards with 1000+ items, pre-filter in Jira before exporting (e.g. to a single component or Epic Link). The tool handles large files but triage sessions are faster when scoped.
📋 ServiceNow exports
ServiceNow uses Number for the ticket ID and Short description for the summary. These are auto-mapped. Ensure you export State and Assignment group for full field coverage.
🔵 Azure DevOps exports
Use the Query → Export to CSV feature in Azure DevOps. Include Work Item Type, Title, State, Assigned To, Story Points, and Area Path (mapped to Component) for best results.
🟠 Jira export — recommended JQL filter
To export issues across all sprint states for a given project, use the following JQL in Jira's Issue Navigator (Issues → Search for Issues), then export via Export → CSV (all fields):
project = <project name> AND sprint in (futureSprints(), openSprints(), closedSprints()) AND updated >= -16w ORDER BY created DESCReplace <project name> with your Jira project key (e.g. PROJ). The -16w filter limits results to items updated in the last 16 weeks — adjust as needed to control export size.
Configuration controls scoring weights, MoSCoW thresholds, Jira site URL, column visibility, and data persistence settings. Default weights work well for most teams — but calibration for your organisation's context significantly improves scoring accuracy.
Key configuration options
Scoring criterion weights
Adjust the relative weight of each of the five scoring criteria to match your organisation's priorities. A compliance-heavy team may weight Time Sensitivity at 2× the default.
MoSCoW band thresholds
The score ranges that map to each MoSCoW band can be adjusted. Default: Must Have ≥15, Should Have ≥10, Could Have ≥5, Won't Have <5.
Jira site URL
Set your Atlassian site URL (e.g. https://your-org.atlassian.net) to make issue IDs in the triage table clickable links back to Jira.
Configuration guide is in the licensed playbook
Unlock weight calibration guides, threshold recommendations by team type, and export configuration templates.
Unlock Full Playbook