Idea Flow
Models
Idea Flow
  • Welcome!
    • Why Models?
    • Why Principles?
  • Agility & Transformations
    • Intro to Agile
      • What Does Agile Mean?
      • What Is An Agile Mindset?
    • Intro to Transformation
      • Why Transform?
      • How Is The Transformation Done?
      • Who Transforms?
      • Which Areas or Functions Transform?
      • How Long Does A Transformation Take?
  • Agile Transformation (Idea Model)
    • Intro to IDEA
      • Leadership-Strip (Tanzaku)
      • Managing The Change
      • Metrics
      • Coaching Plan
        • Coaching Assessment
    • Initial Exposure
      • Training & Coaching
      • Assessment
    • Develop Basics
      • Training & Coaching
      • Assessment
    • Evolve & Reflect
      • Training & Coaching
      • Assessment
    • Accelerate & Kaizen
      • Training & Coaching
      • Assessment
  • Delivery Approach (Flow Model)
    • Intro to Flow
      • Flow of Work
      • Dev Sec Ops
    • Conceptualise
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Commence
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Construct
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Confirm
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Complete
      • Process
      • Outputs
    • Check
      • Process
  • Scrum, Kanban & Other Agile Frameworks
    • Double-Loop Scrum
    • Kanban
  • 3D Work-Breakdown
    • Intro to Work Breakdown
    • Direction
    • Discovery
    • Delivery
    • Flow & 3D Work-Breakdown
  • Roles & Responsibilities
    • Overview
      • Trust Circles
      • Enterprise View
    • Core Team Roles
      • Scrum Master / Iteration Manager
      • Product Owner
      • Developer
      • Tester
      • Business Analyst
      • Infrastructure
    • Extended Team Roles
      • Product Manager
      • Test Lead
      • Tech Lead
      • Subject Matter Expert (SME)
      • UX/UI Designer
      • Infrastructure Lead
      • Project Manager
      • Solution Architect
      • Delivery Manager
      • Change Analyst
    • Trusted Advisor Roles
      • Project Sponsor
      • Stakeholders
  • Topics
    • Prioritisation
    • Estimation
      • Estimation Overview
      • Epic Estimation
      • Initiative Estimation
    • Planning
      • Sprint / Iteration Planning
      • Release Planning
      • Quarterly Planning
      • Problem Statement
    • Ceremonies
      • Showcase
      • Scrum of Scrums
      • Stand-up
      • Retrospective
      • Elicitation
      • Elaboration
      • Acceptance Criteria (AC)
    • Artefacts
      • Tech Spike
      • Definition of Done
      • Social Contract
      • Personas
      • Lean Canvas
      • User Stories
    • Toolkit
      • Success Sliders
      • ICaRuS Scoring
      • Accountability Cards
    • Quality
      • Test Strategy
      • Test Plan
      • Quality Attribute Definitions
      • Test Type Definitions
      • Regression Test Suite Definitions
      • Defect Definitions
      • Defect Severity
      • Defect Priority
      • Agile Testing Quadrants
      • Risk-Based Testing
    • Templates
      • 3rd Party Handover Template
      • Audit Logs
    • Data
      • Information Management
    • Kanban
  • Agile Testing (4Aces Model)
    • Intro to Agile Testing
      • Test Principles
        • Test Automation Principles
      • Test Artefacts
      • Test Triangle
      • Agile Testing Quadrant
    • Arrange
    • Act
    • Assert
    • Annihilate
  • INCIDENT MANAGEMENT (TRACeR MODEL)
    • Intro to TRACeR
      • What is Incident Management
      • Incident Management Workflow
    • Triage
    • Review
    • Action
    • Check
    • Resolve
  • Change Management (3C Change Model)
    • Intro to 3C Change
      • What is Change?
      • What is Change Management?
      • 7Rs of Change Management
      • Model States
      • Implementation
    • Capture
      • Priority
      • Experience
      • Impact
      • Change Types
    • Consider
      • Risk
    • Conduct
      • Plan
        • Change Activities Matrix
      • Perform
        • Rollback or Roll-forward
      • Prove
        • Change Result/Status
  • Faciliation
    • Intro to Faciliation
      • Agile Facilitation
      • Planning and Running a Workshop
    • Meetings
      • Meeting Prep
    • Workshops
      • Quarterly Planning Workshop
      • Integrated Culture Workshop
    • Games
      • Dice Game
      • Battleships
      • Kanban Pizza Game
    • Icebreakers
      • Check Your Personal Thinking Style
  • Agile Coaching (A6 Model)
    • Intro to Coaching
    • Agree
    • Address
    • Assess
    • Align
    • Assign
    • Account
  • Agile Leadership
    • Intro to Agile Leadership
  • Strategy
    • What is Strategy?
    • What is Vision?
    • What is a Mission?
    • What are Values and Drivers?
    • Intent-based Outcomes
    • MunroMaps
  • OKRA
    • OKRS + ACTIONS = OKRA
      • Implementation
      • Cycle Cadence
    • Objectives
      • OKRs
    • Key Results
    • Actions
  • Agile Software Architecture (C4 Model)
    • Intro to Architecture
      • Role of the Architect
      • SOLID Principles
      • DRY Principle
      • Single Source of Truth (SSOT)
    • Context
      • Examples
    • Container
      • Examples
    • Component
      • Examples
    • Code
      • Examples
    • Patterns
      • Back-end for Front-end (BFF)
      • Event-Driven Microservices
  • Portfolio Management (PMO Practice Model)
    • Intro to Portfolio Management
      • Practices & Flow
      • Objectives
      • Types
      • Maturity Assessment
      • Setting Up
        • Charter
    • Demand Practice
    • Risk Practice
    • Performance Practice
      • Cost of Delay (CoD)
      • Metrics
    • Report Practice
    • Delivery Practice
    • Asset Practice
    • Change Practice
  • RAFT
    • RAFT Framework
  • Tools
    • Jira
      • Best Practice
      • Printing Physical Cards
    • Confluence
      • Best Practice
      • Example Confluence Layout
    • Power BI
      • Power Query M
    • Miro
      • Best Practice
  • FAQs
    • Frequently Asked Questions
    • Glossary of Terms
  • Thanks & Contributors
    • Thanks
    • License
Powered by GitBook
On this page
  • Day 1:
  • Day 2:

Was this helpful?

  1. Topics
  2. Planning

Quarterly Planning

Last updated 2 years ago

Was this helpful?

We use this to define goals for the upcoming quarter for each delivery area and determine whether there are any further considerations that must be made before the planned activity commences so that we can ensure our plan is realistic and will achieve value for the business.

Quarterly planning is when the business defines the goals for the quarter and their metrics for the teams to commit to a feature roadmap.

Dividing the year into quarters makes planning easier and more accurate, decreases risk and complexity, improves dependency mapping and provides an opportunity for a shorter feedback loop in case the prioritized features are not driving to the desired goals.

Benefits of quarterly plannning include:

  • Establishing face-to-face (virtual) communication among all team members and stakeholders

  • Building a social network the teams can depend upon

  • Aligning development to business goals with the business context, vision, and Team and Program objectives

  • Identifying dependencies and fostering cross-team collaboration

  • Matching demand to capacity and eliminating excess Work in Process (WIP)

  • Fast decision-making

The Quarterly Kick-Off session is held for all Major Play and BAU areas to share their goals for the coming quarter and plans to achieve these with our End to End teams and interested stakeholders so that everyone understands what we are seeking to achieve as One Team.

Intended Outcome All delivery teams are aligned with the direction for the coming quarter.

Day 1:

  1. Prepare the metrices on what has been delivered and what value did it drive, if we had objectives already defined then were we able to match the key results we expected to achieve (Did we achieve the Value/impact we expected if not then what happened, if so then how did it help us as an organization)

  2. List the items that might move to next quarter (be prepared to ask the question why to understand how can we have done this better during the day 1 of planning)

  3. Prepare the Collaboration board (Virtual or Physical more focused towards Virtual if we are planning to hold Virtual Day 2)

  4. Bring the risk forward to the risk board to ask what risks had occurred and what did we do about it (Did we mitigate it or resolved it before it could occur or Accepted the consequences)

  5. Did we change priorities if so then why (display the change in priority to ask the reason why in the board)?

  6. Run the workshop to define the cost of delay for each item (Must include relative estimation of Business Value, Risk reduction/Future Opportunities, Time Criticality)

Example Canvas from SAFe can be used before going into Quarterly Planning (this might stay the same of can be changed based on the market response we need to have)

Day 2:

  • Prepare the Business context to be shared with the key results achieved for the Quarter

  • Define what we would like to achieve in the next Quarter with Portfolio/Product/Solution vision

  • List of desired Outcomes for the quarter (Using Objectives and Key Results)

  • Ready Objectives & Key Results for Program level

  • Strategic & Portfolio Roadmap: How does Quarterly OKR's connect to Organizational OKR's

  • Metrics for the quarter - How are we going to measure our Key Results

  • Top priorities for the Quarter - How each AGP's help achieve the Key Results

  • Concept workshops planned and resulting work items estimated

  • Ready Collaboration boards for the areas to plan with RAID & ROAM included at area/program level

  • A refined list of AGP's t-shirt sized and teams already have a good idea about them

  • Define Program Team structure & send out invitations

  • Agenda sent to the relevant stakeholders 1 week prior with Start and Stop times, timeboxes, speaker callouts etc. If multiple time zones involved please take into account of that as well

  • Define the facilitators & the outcomes expected out of each breakout sessions

  • Facilitator understands context and mechanics of the event & has access to Facilitator guide if needed with support from their Supervisor if they are new to this (New to A&G or Facilitating this for the first time)

  • Technology/Infrastructure team involved to support the expected Objectives to be delivered

Multiple teams will be sent to their breakout rooms with one facilitator to start planning their quarter

What happens in the team breakout rooms:

  1. Teams will understand what is there in their backlog according to the priority

  2. Teams will do high level estimation at AGP level with T-shirt sizing if the work has not already been estimated

  3. Teams will define action items for each work item needed post the Day 2 of planning e.g. need concept workshop or detailed risk management planning etc.

  4. Teams will bring the items in the roadmap based on priority.

  5. Teams will updated the dependencies with other teams in the Program and organization wide