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

Was this helpful?

  1. Agile Transformation (Idea Model)
  2. Develop Basics

Assessment

The assessment for Phase 2 aims to evaluate participants' understanding and application of the foundational Agile concepts introduced in this phase. This assessment will measure their grasp of decomposition, work types, feedback loops, task assignment strategies, and communication in Agile teams. It will consist of multiple components to evaluate their knowledge and skills comprehensively.

Multiple-choice questions (MCQs)

Purpose: Test participants' understanding of key concepts such as Work Breakdown Structure (WBS), Definition of Done (DoD), user stories, tasks, and service requests.

Format: Each question has several options, with one correct answer.

Total Questions: 10

Example Questions:

Which of the following best describes a Work Breakdown Structure (WBS)?

a) A list of project tasks and activities arranged in chronological order. b) A hierarchical decomposition of the total scope of work to accomplish project objectives. c) A flowchart depicting the workflow of project tasks. d) A schedule of project milestones and deadlines.

What is the primary purpose of defining the 'Definition of Done' (DoD)?

a) To outline the project scope. b) To ensure a shared understanding of what it means for work to be complete. c) To prioritise tasks in the backlog. d)To assign roles and responsibilities within the team.

Which of the following is NOT a characteristic of a good user story?

a) Independent b) Negotiable c) Testable d) Prescriptive

Short-Answer Questions

Purpose: Assess participants' ability to:

  • explain how identifying work increases quality.

  • describe different levels of DoD and how they apply to various work types.

  • relate the importance of traceability from strategy to execution.

Format: Participants provide brief written responses.

Total Questions: 5

Examples:

Explain the importance of having a clear 'Definition of Done' (DoD) in an Agile project. Describe how feedback loops contribute to the continuous improvement process in Agile methodologies. Discuss the role of governance in developing a good 'Definition of Done' and how it impacts project quality. How does realigning priorities help manage the work effectively in an Agile project?

Peer Review

Purpose: The peer review component of the Agile Training Plan serves multiple important purposes:

  1. Knowledge Reinforcement: By reviewing peers’ work, participants reinforce their understanding of Agile concepts and practices.

  2. Collaboration and Communication: It encourages open communication and collaboration among team members, fostering a culture of constructive feedback and continuous improvement.

  3. Diverse Perspectives: Participants gain insights from their peers' approaches and perspectives, which can lead to more innovative solutions and enhanced problem-solving skills.

  4. Skill Development: The process helps participants develop critical skills in analysis, evaluation, and constructive feedback, essential for effective teamwork in Agile environments.

  5. Quality Assurance: Peer review acts as a quality check, ensuring that the work meets the defined standards and criteria and identifying areas for improvement.

Format: Participants are paired or grouped to ensure a diverse mix of perspectives and attend all of the common agile ceremonies of a selected team over a month. Participants observe and record their thoughts on the ceremonies, including accuracy, completeness, clarity, adherence to Agile principles, and creativity. Participants present their work to their peer review group and the observed team. This could include their decomposition of work, user stories, tasks, DoDs, or feedback loop implementations. Finally, an open floor for discussion is held, allowing participants to ask questions, seek clarifications, and discuss potential improvements.

Last updated 7 months ago

Was this helpful?