38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
---
|
|
title: Agile Implementation Plan
|
|
created_date: 2025-01-14
|
|
updated_date: 2025-01-14
|
|
aliases:
|
|
tags:
|
|
---
|
|
# Agile Implementation Plan
|
|
|
|
## Scrum
|
|
### Roles
|
|
#### Product Owner
|
|
The product owner is responsible for the requirements definition. The right requirements and their appropriate prioritization is crucial for the success of a project. Therefore it is very important to hire excellent personnell for this role, since it has a high leverage. See [[More Effective Agile by Steve McConnell#Most common Challenges|Most common Challenges with product owners]] for more details.
|
|
|
|
### Meetings
|
|
#### Sprint Planning
|
|
#### Daily Standup
|
|
|
|
#### Retrospectives
|
|
### Work Units
|
|
- Stories should be completable within a single sprint:
|
|
- The team should decompose its stories so that no single story consumes more than half the team for half the sprint; most stories should be smaller.
|
|
- The team should aim to complete 6-12 stories per sprint (assuming recommended team size (3-9))
|
|
|
|
|
|
---
|
|
## Current faults discovered
|
|
- Excessive schedule pressure --> focus on appearance of progress above actual progress (see [[More Effective Agile by Steve McConnell|More Effective Agile]], page 51)
|
|
|
|
|
|
## Core Culture Values
|
|
- Open mistake and learning mentality: includes retrospection after sprints: could I have done more, should I have done less? Is the quality release quality?
|
|
- Commitment mentality: every team member is included in the planning and commits personally to what they can reasonably do in the next sprint.
|
|
|
|
## Risks associated with Scrum at OneSec
|
|
- We don't understand scrum well enough to properly implement it. Or to properly coach the entire team how to stick to the rules
|
|
- [[Floris]] cannot give away responsibility to the team.
|
|
- Not following it a 100% --> do "Scrum, but..." |