The portfolio team has transitioned from the old portfolio tool, Accolade, to Jira to streamline the number of tools in use. Jira for portfolio consists of three main components:
General Portfolio Initiatives Follow-Up: This portfolio layer provides a comprehensive overview of all initiatives, including descriptions, costs, decision notes, accountabilities, dependencies, and more.
Plan View: This component displays the timeline and planned activities for various initiatives, indicating when and what will be accomplished.
Detailed Project View: This view supports both waterfall and agile methodologies, allowing for detailed tracking and management of one or multiple initiatives.
Porfolio Inniatives follow-up
Kanban & Table view
The Jira Kanban board is used to track all initiatives within the Portfolio, providing all necessary information to facilitate informed decision-making. It offers a quick overview of projects that are in the envisioning, strategizing, or blocked stages.
Users can view initiatives by IT Domain, underlying project, responsible parties, GBU, or BSA.
Additionally, it allows for assessment in a format similar to an Excel spreadsheet.
Details on a initiatives
For each initiative, various pieces of information are captured and stored in Jira throughout the portfolio process. This includes:Vision of the Initiative: Details on the target audience and the benefits it will provide.
Goal/Value Statement: The objectives and value the initiative aims to deliver.
Risks: Potential challenges and risks associated with the initiative.
General Information: Includes GBU, objective, strategic theme, business owner, and IT owner.
Due Dates: Scheduled completion dates for the initiatives.
Applicable Notes: Portfolio decision notes involving necessary stakeholders.
Confluence Link: Reference to related Confluence documentation.
Google Drive Link: Access to relevant Google Drive files.
OKRs: Objectives and Key Results associated with the initiative.
Budget and Impact: Financial considerations and effects on future run costs.
Additionally, all subtasks within the actual project are tracked to identify who holds responsibilities for critical topics. This ensures that the objectives for the main strategic themes are achieved.