---
esco_uri: http://data.europa.eu/esco/skill/72a74f69-5cf1-43c5-99b9-62a444578919
esco_label: "engineering processes"
relation: essential
onet_soc: 15-1252.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# engineering processes — Software Engineer

For a Software Engineer, 'Engineering Processes' isn’t about building bridges; it's about *how* we build software reliably and predictably. Daily, this manifests as participating in – and often driving – the selection and implementation of methodologies like Agile (Scrum, Kanban), Waterfall (less common now but still relevant for some projects), or hybrid approaches. It means understanding when to use specific practices within those frameworks: writing user stories with clear acceptance criteria, conducting code reviews, defining sprint goals, estimating effort, and tracking progress using tools like Jira, Azure DevOps, or Trello.  It's about making informed decisions *about* the development process itself, not just coding.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
