HVE Project Lifecycle

Up: HVE Core · Teaching: HVE Teaching Plan

Microsoft Guidance

The lifecycle overview maps delivery from setup to operations:

Stage	Purpose	Representative tooling
1. Setup	Establish the working environment	hve-core-installer, git-setup
2. Discovery	Investigate the problem and constraints	rpi-research, brd-builder, security-planner
3. Product Definition	Specify requirements and decisions	prd-builder, requirements-author, adr-creation
4. Decomposition	Break scope into work items	functional-planner, backlog-manager
5. Sprint Planning	Select and organize delivery work	backlog-manager, backlog-management
6. Implementation	Execute engineering work	RPI Agent, rpi-plan, rpi-implement
7. Review	Evaluate the result	rpi-review, code-review
8. Delivery	Merge and hand over	git-merge, backlog-management
9. Operations	Maintain and respond	documentation, incident-response

Transitions depend on artifacts and readiness: requirements feed decomposition, planned work feeds implementation, and review can return work for correction. Operations can lead back to implementation. Design Thinking outputs enter Discovery. This is an iterative delivery map.

Frontier Teaching Proposal

Use a fictional client engagement aligned to Whitelabel Training Program. Give learners incomplete requirements, an existing repository, and a delivery constraint. Ask them to identify the current stage, the missing evidence, and the next human decision before choosing tooling.

Teach the distinction between the project lifecycle and HVE RPI Workflow with two examples: a client engagement containing several implementation tasks, and a small defect needing only a bounded change. Assess the quality of the learner’s choice, rather than recall of every tool name.