Agile Scrum - mostpros1/repository GitHub Wiki

Scrum guide

---

Agile scrum engineering culture

Fail-friendly environment

• Fail fast → Learn fast → Improve fast. Failure recovery > Failure avoidance. Fail wall. Who’s fault was it? What did we learn? What will we change?

Trust > Control

• Agile at scale requires trust at scale. That means no politics. It also means No Fear. Fear doesn’t just kill trust, it kills innovation. Because if failure gets punished people won’t dare try new things. Focus on motivation, community and trust. Rather than structure and control.

Autonomous team

• Autonomy basically means that the teams decides what to build, how to build it, and how to work together while doing it.
• Cross functional self organizing teams with around 8 people. End-to-end responsibility. Design, commit, deploy, maintenance, operations. Each team has a long term mission. Example: Make the company the best place to discover the xyz industry.

Alignment and autonomy

• High alignment and high autonomy. Alignment enables autonomy.
• Leader’s job: Communicate what problem needs to be solved and why. Team’s job: Collaborate with each other to find the best solution.

Community > Structure

• How easily can we get our stuff into production?
• Release easy, release often. So small frequent releasing is a routine. Invest heavily in test automation and continuous delivery infrastructure.
• Self-service model. Client app team, feature team and infrastructure team

Chaos > Bureaucracy

• Healthy culture heals broken process.