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
  • Applying the Information Management Principles
  • Benefits
  • Types of information
  • Formal Content
  • Group Content
  • Individual Content

Was this helpful?

  1. Topics
  2. Data

Information Management

The following AFAIRS principles guide information management activities:

Information and data is an ASSET, which should:

  • be proactively managed throughout its lifecycle due to its inherent strategic value

  • be utilised in a legal and ethical manner

  • have clearly defined stewards assigned to manage it throughout its lifecycle

  • follow the principle of born-digital: stay digital

To be FINDABLE, information and data should be:

  • registered or indexed in a searchable resource

  • described with rich metadata and contain basic machine actionable metadata

  • assigned a unique identifier, where possible, so that it is findable at any point in time

To be ACCESSIBLE, information and data may be obtainable by machines and humans:

  • upon appropriate authorisation

  • through a well-defined protocol

To be INTEROPERABLE, data should be structured and:

  • be machine-actionable

  • utilise shared vocabularies and/or ontologies

  • be both constructed in a way understood by machines and from which meaning is then able to be derived

To be REUSABLE, information and data should be:

  • well described so that it can be easily linked or integrated with other data sources

  • of quality, with its source and context well understood

To be SECURE, information and data should be:

  • classified appropriately

  • labelled appropriately

  • managed appropriately

Applying the Information Management Principles

  • the Principles are inter-related and ideally need to be applied as a set

  • the Principles will sometimes compete. For example, the principles of "accessibility" and "security" often conflict

  • each principle is meant to be considered in the context of "all other things being equal"

  • at times a decision will be required as to which principle will take precedence on a particular issue

Benefits

The Framework aims to deliver or enable the following information management benefits:

Increased impact of work outputs

Managing the outputs from our work to increase its impact.

Improved discovery and access

Providing easy and transparent access to accurate and timely data and information.

Improved integration and accuracy

Collecting data once and ensuring its integrity and quality.

Improved decision-making

Understanding the business and providing better information to support analysis, decision-making, and risk identification.

Improved compliance and decreased costs

Through efficient processes and systems, achieving record-keeping and regulatory compliance and reducing costs.

Types of information

Formal Content

GOAL: Increase our spread of formal content across the business but not its depth of penetration, reserving it for that content that needs that structure and control.

Well defined and controlled in both its structure and composition and has a recognised and active set of owners and stakeholders.

It should include regular review cycles and a known place where it is published and consumed from.

EXAMPLES: Defined reports, compliance pieces, RFPs, and contracts.

Group Content

GOAL: Significantly increase both the spread and depth of group content across the business with the aim of better managing knowledge, improving team efficiency and better demonstrating process compliance and maturity.

Owned and governed by a development team. While requiring some control and structure primarily to encourage consistency, searchability and reusability, the overhead of Formal Content is unwarranted.

EXAMPLES: Team templates, regular internal reporting, meeting agendas and minutes and internal documentation templates.

Individual Content

GOAL: Provide team members with the ability to quickly develop and maintain knowledge for their own purposes / day-to-day duties

Largely unstructured and ungoverned content produced by individual team members as part of performing their day-to-day duties.

Represents the individual body of knowledge that (hopefully) has been documented by team members or is the product of their work activities.

It could be turned into group content with little effort (i.e. introducing a collective rather than individual ownership, standardising the format and storing appropriately).

EXAMPLES: personal notes used during brainstorming

Last updated 2 years ago

Was this helpful?