HVE main page

[shiranr]

Pull Request Template

What are you trying to address

This PR introduces a new section to the Engineering Fundamentals Checklist focused on Hypervelocity Engineering (HVE) principles. HVE is a modern delivery approach that enables small, expert teams to ship high-quality software at speed by embedding compliance, security, and governance from the start.

More content is coming in the near future.

Checklist

READY TO PR? Use the check-list below to ensure your branch is ready for PR.

• Changes follow the repo structure and land in the appropriate folder and section
• No confidential information
• No duplicated content
• Labeled appropriately
• This PR was reviewed by at least one subject matter expert
• No lint check errors related to your changes

Note: You may see link check errors on pages you have not touched. This is normal, and due to either broken links or sites that reject link checker bots. The reviewer will help you get to a green state on these.

[github-actions]

🦙 MegaLinter status: ⚠️ WARNING

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ MARKDOWN	markdownlint	1		0	0.29s
✅ MARKDOWN	markdown-table-formatter	1		0	0.22s
⚠️ SPELL	cspell	2		2	1.78s
✅ SPELL	lychee	1		0	0.17s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[TessFerrandez]

Looks great, I'm approving but have some suggestions

[balteravishay]

A general comment from me: HVE is a very "ISE" term that is not commonly known. do we want to push a new term on the industry or should we adjust to more common names for what this actually means?

[balteravishay]

another general comment: is HVE a "section" of its own? or is it an extension of everything that the playbook already has?

[chadradams]

See notes attached.

[chadradams]

A glossary for HVE terms like “policy-as-code” or “CRISP-DM” could be helpful.

[shiranr]

I added it as another user story.

[balteravishay]

CRISP is an internal tool. not sure that we should refer to it externally while it is not released publicly.

[nyouens]

I agree with the comment around HVE being an internal label and we may want to consider in future iterations if this is the best construct for customer teams who hear other popular terminology.