Skip to content
Tagged articles

acceptance criteria

15 articles · Page 1 of 1
Data Bricklaying Diary
Data Bricklaying Diary
Nov 16, 2026 · Fundamentals

From 'Just Query' to Verified Delivery: Goal-Constrained Ontology Construction in 5 Steps

This article outlines a five-step methodology for goal-constrained ontology construction, using an equipment management example to demonstrate how to align stakeholder expectations, define competency questions, reuse existing definitions, build minimal models with provenance, validate with normal and edge-case samples, and deliver version-aligned artifacts with explicit limitations and responsibilities.

acceptance criteriacompetency questionsdata integration
0 likes · 21 min read
From 'Just Query' to Verified Delivery: Goal-Constrained Ontology Construction in 5 Steps
Chengwu Tech Stack
Chengwu Tech Stack
Nov 10, 2026 · Industry Insights

Full AI vs AI-Assisted Development: Speed, Risk, and Acceptance Compared

The article compares full AI development and AI-assisted development using a bricklaying metaphor and a notification retry case study, analyzing how human intervention points affect speed, risk, and acceptance across investigation, design, implementation, review, testing, deployment, operations, and handover.

AI-assisted developmentIdempotencyacceptance criteria
0 likes · 30 min read
Full AI vs AI-Assisted Development: Speed, Risk, and Acceptance Compared
Linyb Geek Road
Linyb Geek Road
Oct 26, 2026 · Artificial Intelligence

Which Tasks Suit AI Agents? 5 Questions to Decide

This article presents a framework for deciding which tasks to delegate to AI agents, emphasizing verifiable acceptance criteria and risk control over task difficulty, and outlines four collaboration modes based on verifiability and risk.

AI agentsAnthropicOpenAI
0 likes · 11 min read
Which Tasks Suit AI Agents? 5 Questions to Decide
Random Bulletin
Random Bulletin
Oct 24, 2026 · R&D Management

Why Post-Mortem Action Items Fail at 10M QPS: Building a Closed-Loop Improvement System

This article details a systematic framework for turning post-mortem action items into verified risk reductions, covering eight required fields, single-owner accountability, a five-state tracking machine, risk-based prioritization, layered governance rhythms, three-evidence acceptance criteria, and cross-team dependency management for 10M QPS systems.

acceptance criteriaaction itemsclosed-loop improvement
0 likes · 32 min read
Why Post-Mortem Action Items Fail at 10M QPS: Building a Closed-Loop Improvement System
PMTalk Product Manager Community
PMTalk Product Manager Community
Sep 27, 2026 · Product Management

Beyond the Demo: Five-Layer Architecture for Production-Ready AI Products

This article argues that moving AI products from demos to reliable B2B production requires a five-layer architecture — model, knowledge, rules, system, and process — rather than just a stronger model, detailing each layer's responsibilities, three collaboration scenarios, a task definition card for requirements, cross-functional team alignment, layered acceptance criteria, and common architectural imbalances to avoid.

AI product architectureB2B AIacceptance criteria
0 likes · 17 min read
Beyond the Demo: Five-Layer Architecture for Production-Ready AI Products
ITPUB
ITPUB
Sep 20, 2026 · Industry Insights

Digital Transformation Isn't Gone—It's Awaiting Its Acceptance Slip

The article argues that the term 'digital transformation' is fading not because the work stopped, but because organizations now demand concrete, verifiable results—acceptance slips—rather than vague slogans, highlighting the gap between project completion and business value, and proposing accountability mechanisms to avoid repeating the cycle with AI.

AI readinessOrganizational AccountabilityPing An case study
0 likes · 28 min read
Digital Transformation Isn't Gone—It's Awaiting Its Acceptance Slip
PMTalk Product Manager Community
PMTalk Product Manager Community
Sep 12, 2026 · Product Management

The One Flaw Shared by Inefficient Product Managers: Requirement Docs as Feature Lists

This article explains why treating requirement documents as mere feature lists leads to endless revisions, and introduces a three-dimensional framework — user value, business logic, system implementation — plus AI-assisted analysis and a rigorous definition of done to produce executable, high-quality specs.

AI-assisted analysisBusiness Logicacceptance criteria
0 likes · 5 min read
The One Flaw Shared by Inefficient Product Managers: Requirement Docs as Feature Lists
Data Bricklaying Diary
Data Bricklaying Diary
Sep 10, 2026 · R&D Management

Agent Runs Tests ≠ Trustworthy Results: Building Independent Verification in AI-Native Development

The article explains why AI agents running tests doesn't ensure reliable verification, proposing a five-layer system — self-verification, independent verifier, test role, CI toolchain, and business acceptance — with version-linked evidence, protected acceptance criteria, design cross-checks, and clear human judgment boundaries for semantic, risk, and authorization decisions.

AI-native developmentCI/CDVerification
0 likes · 13 min read
Agent Runs Tests ≠ Trustworthy Results: Building Independent Verification in AI-Native Development
Tech Ocean
Tech Ocean
Aug 11, 2026 · Product Management

Beyond PRDs: The Six Product Facts AI‑Ready Product Managers Must Deliver

Product managers must replace lengthy PRDs with a concise, executable product intent that includes problem definition, rules, interactive prototypes, domain models, acceptance criteria, and decision context, enabling both humans and AI agents to understand, implement, and verify requirements consistently across design, development, and testing.

AIacceptance criteriacontext package
0 likes · 19 min read
Beyond PRDs: The Six Product Facts AI‑Ready Product Managers Must Deliver
Chengwu Tech Stack
Chengwu Tech Stack
Aug 11, 2026 · Artificial Intelligence

Pyramid Theory: The Hidden Logic Behind High-Impact AI Prompts

The article demonstrates how the pyramid principle — conclusion-first, categorized grouping, and layered decomposition — turns vague client requests into structured, verifiable AI prompts, using a contract bulk-import example to show a four-level breakdown from delivery conclusion to executable tasks.

AI collaborationAI promptingacceptance criteria
0 likes · 21 min read
Pyramid Theory: The Hidden Logic Behind High-Impact AI Prompts
Engineer Tang's Implementation Study Notes
Engineer Tang's Implementation Study Notes
Mar 17, 2026 · Industry Insights

First Client Meeting Mastery: A Proven Framework for Implementation Consultants

This guide outlines a complete framework for implementation consultants facing their first client meeting, detailing pre-meeting preparation, a five-step communication process, three critical taboos, and closing techniques to project professionalism and avoid common pitfalls.

acceptance criteriaclient meetingcommunication framework
0 likes · 6 min read
First Client Meeting Mastery: A Proven Framework for Implementation Consultants
DevOps
DevOps
Jan 4, 2023 · Fundamentals

Understanding Test‑Driven Development: From TDD Mindset to Contract Testing and Standards

The article explains how Test‑Driven Development is fundamentally a mindset that emphasizes predefined standards and expectations, explores related practices such as contract testing, acceptance criteria, and standard‑driven development, and discusses the challenges of defining, maintaining, and motivating adherence to these standards within agile teams.

AgileContract TestingTDD
0 likes · 6 min read
Understanding Test‑Driven Development: From TDD Mindset to Contract Testing and Standards
DevOps
DevOps
Jun 24, 2020 · Product Management

Essential Knowledge for Scrum Product Owners: From Project‑to‑Product Mindset to Acceptance Criteria

This article explains the fundamental concepts a Scrum Product Owner should master, including the shift from project to product thinking, the PO role and mission, product vision techniques, backlog grooming, persona creation, user story format, and the importance of well‑written acceptance criteria.

Product Owneracceptance criteriaproduct management
0 likes · 11 min read
Essential Knowledge for Scrum Product Owners: From Project‑to‑Product Mindset to Acceptance Criteria
DevOps
DevOps
Oct 24, 2018 · Operations

Improving Delivery Efficiency with Suppliers through Agile Principles and Work‑in‑Progress Limits

The article describes how a financial institution applied agile concepts such as limiting work‑in‑progress, daily progress meetings, clear requirement definition, and acceptance criteria to a supplier‑driven project, resulting in higher delivery speed, better focus on high‑priority items, and continuous improvement of the collaboration process.

Delivery EfficiencyDevOps RecruitmentWork-in-Progress
0 likes · 10 min read
Improving Delivery Efficiency with Suppliers through Agile Principles and Work‑in‑Progress Limits
DevOps
DevOps
Dec 3, 2017 · R&D Management

Understanding Definition of Done (DoD) and Acceptance Criteria (AC) in Scrum

This article explains Scrum's Definition of Done (DoD) and Acceptance Criteria (AC), illustrates common pitfalls through daily stand‑up examples, presents excerpts from the Scrum Guide, compares DoD and AC, and offers practical recommendations for teams to establish clear definitions before the first sprint.

R&D managementacceptance criteriadefinition of done
0 likes · 8 min read
Understanding Definition of Done (DoD) and Acceptance Criteria (AC) in Scrum