vault backup: 2025-01-15 12:18:05
This commit is contained in:
@@ -35,4 +35,9 @@ The product owner is responsible for the requirements definition. The right requ
|
||||
## 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..."
|
||||
- Not following it a 100% --> do "Scrum, but..."
|
||||
|
||||
## What are characteristics of the Software that we need to implement at OneSec?
|
||||
- we have changing hardware
|
||||
- safety
|
||||
- What exactly is the business plan, who are the customers, what is the product?
|
||||
@@ -8,4 +8,6 @@ tags:
|
||||
# Startup Culture List
|
||||
- Decriminalize Mistakes: Decriminalize mistakes so that teams surface them without hesitation and you can learn from them. A mistake you don't learn from penalizes your organization twice. (Page 227 in [[More Effective Agile by Steve McConnell]])
|
||||
- Have a KPI dashboard for everyone to see
|
||||
- Have a mission statement who is signed by everyone and also influenced by everyone
|
||||
- Have a mission statement who is signed by everyone and also influenced by everyone
|
||||
- problem characterization guideline / checklist: write short 1 pagers whenever a problem appears that we might want to solve. Use the [[More Effective Agile by Steve McConnell#Responding to the Challenges of Complexity and Uncertainty|Cynefin and OODA]] approach to characterize them.
|
||||
-
|
||||
Reference in New Issue
Block a user