Update nexus: fix conflicts and sync local changes
This commit is contained in:
@@ -1,34 +1,34 @@
|
||||
---
|
||||
title: "Agile Practices"
|
||||
type: concept
|
||||
tags: [agile, scrum, kanban, devops]
|
||||
sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]
|
||||
last_updated: 2026-04-22
|
||||
---
|
||||
|
||||
## Summary
|
||||
Agile Practices are iterative development methodologies (Scrum, Kanban) that emphasize continuous delivery, customer collaboration, and adaptability. In the DevOps context, Agile and DevOps are symbiotic — Agile focuses on iterative development while DevOps extends agility to operations, together enabling end-to-end speed and quality. Agile frameworks provide the delivery cadence while DevOps provides the operational excellence to sustain it.
|
||||
|
||||
## Key Frameworks
|
||||
|
||||
### Scrum
|
||||
- Structured sprints with defined timeboxes
|
||||
- Roles: Product Owner, Scrum Master, Development Team
|
||||
- Ceremonies: Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective
|
||||
|
||||
### Kanban
|
||||
- Continuous flow model (no fixed sprints)
|
||||
- Visual board with WIP limits
|
||||
- Focus on throughput and cycle time
|
||||
|
||||
## Agile + DevOps Integration
|
||||
- **CI/CD as Agile Accelerators**: Automating testing and deployment shrinks feedback cycles from weeks to minutes
|
||||
- **Value Stream Mapping**: Lean technique to identify and eliminate waste in Agile/DevOps workflows
|
||||
- **Shift-Left**: Moving operations concerns (security, performance) into Agile sprints
|
||||
|
||||
## Connections
|
||||
- [[DevOps Culture]] — Agile and DevOps are symbiotic; DevOps extends Agile to operations
|
||||
- [[CI/CD Pipeline]] — CI/CD accelerates Agile feedback cycles
|
||||
- [[Value Stream Mapping]] — Lean technique for Agile/DevOps workflow optimization
|
||||
- [[Shift-Left Testing]] — Agile practice of moving testing earlier in the lifecycle
|
||||
- [[Project State Management]] — [[Event Sourcing]] as an alternative to Kanban-style collaboration (see Conflict Area in overview.md)
|
||||
---
|
||||
title: "Agile Practices"
|
||||
type: concept
|
||||
tags: [agile, scrum, kanban, devops]
|
||||
sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin]
|
||||
last_updated: 2026-04-22
|
||||
---
|
||||
|
||||
## Summary
|
||||
Agile Practices are iterative development methodologies (Scrum, Kanban) that emphasize continuous delivery, customer collaboration, and adaptability. In the DevOps context, Agile and DevOps are symbiotic — Agile focuses on iterative development while DevOps extends agility to operations, together enabling end-to-end speed and quality. Agile frameworks provide the delivery cadence while DevOps provides the operational excellence to sustain it.
|
||||
|
||||
## Key Frameworks
|
||||
|
||||
### Scrum
|
||||
- Structured sprints with defined timeboxes
|
||||
- Roles: Product Owner, Scrum Master, Development Team
|
||||
- Ceremonies: Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective
|
||||
|
||||
### Kanban
|
||||
- Continuous flow model (no fixed sprints)
|
||||
- Visual board with WIP limits
|
||||
- Focus on throughput and cycle time
|
||||
|
||||
## Agile + DevOps Integration
|
||||
- **CI/CD as Agile Accelerators**: Automating testing and deployment shrinks feedback cycles from weeks to minutes
|
||||
- **Value Stream Mapping**: Lean technique to identify and eliminate waste in Agile/DevOps workflows
|
||||
- **Shift-Left**: Moving operations concerns (security, performance) into Agile sprints
|
||||
|
||||
## Connections
|
||||
- [[DevOps Culture]] — Agile and DevOps are symbiotic; DevOps extends Agile to operations
|
||||
- [[CI/CD Pipeline]] — CI/CD accelerates Agile feedback cycles
|
||||
- [[Value Stream Mapping]] — Lean technique for Agile/DevOps workflow optimization
|
||||
- [[Shift-Left Testing]] — Agile practice of moving testing earlier in the lifecycle
|
||||
- [[Project State Management]] — [[Event Sourcing]] as an alternative to Kanban-style collaboration (see Conflict Area in overview.md)
|
||||
|
||||
Reference in New Issue
Block a user