Product Development Events
@ OpenHAD
Product Development Events
@ OpenHAD
Iterations are the core development cycle in OpenHAD. Teams choose an iteration length between 2 and 6 weeks based on business needs, complexity, and delivery context. Each iteration aims to deliver measurable outcomes, validated learning, product improvements, or deployable capabilities while maintaining a sustainable pace.
Iteration Planning is the event where the team plans the upcoming iteration by setting goals, identifying priorities, estimating effort, assessing capacity, and agreeing on the work most likely to create value. Planning considers the contributions of humans, AI assistants, and autonomous AI agents, determining how work will be distributed, coordinated, and governed across human-AI teams. The outcome is a shared plan that aligns people, AI capabilities, and resources toward achieving the iteration objectives.
Iteration Review is an outcome-focused event where the team inspects and evaluates what was learned, validated, built, automated, or delivered during the iteration by both humans and AI. The team reviews outcomes against goals, explores insights gained from experiments and execution, and demonstrates contributions produced through human-AI collaboration, including work performed by AI agents and automation. Stakeholders provide feedback, assess value, review assumptions and results, and help identify opportunities, risks, and future priorities.
The Short Daily Sync is a brief coordination event focused on progress toward iteration goals, key decisions, risks, dependencies, and blockers. The objective is to maintain flow, enable collaboration, and identify blockers and remove obstacles. After the Short Daily Sync, few team members may engage in focused follow-up discussions to address specific tasks, dependencies, technical challenges that do not require the participation of the entire team.
Weekly Adaptive Planning & Backlog Refinement ensures that both the iteration plan and backlog remain aligned with evolving business needs and priorities. Since OpenHAD iterations can span between 2 and 6 weeks, teams may need to make minor adjustments to the iteration plan during execution. During this event, the team analyze iteration progress and performs any minor changes required for the current iteration, such as adding, removing, reprioritizing, or refining tasks based on changing priorities or learnings. Once the necessary plan adjustments are completed, the team proceeds with backlog refinement by reviewing upcoming work items, clarifying requirements, updating priorities, identifying dependencies and risks, and preparing future work for implementation. This continuous planning and refinement approach enables teams to remain adaptive while maintaining focus on iteration objectives and maximizing value delivery. Within this approach, minor scope changes are welcomed during the iteration, provided the team has sufficient capacity to accommodate.
Flexi Retro is a lightweight, flexible improvement event that can be initiated at any time when the team identifies a meaningful insight, opportunity, challenge, success, failure, or emerging concern. Rather than waiting for a scheduled retrospective, teams reflect on their ways of working dynamically, enabling faster learning and adaptation. Discussions may examine human collaboration, AI-assisted work, AI agent performance, processes, tools, experiments, and outcomes to identify improvements.