Abstract: You’re Agile. You talk the talk and walk the walk. For example, you have retrospectives. just like the 12th principle of the Agile Manifesto says: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Why is it then does your Agile implementation look remarkably similar to everyone else’s? Many of the practices associated with Scrum or SAFe or even XP tend to be taken as doctrinal necessities of agile practice and are sacred. What would your process and culture be like if you applied another of the Agile principles to your organization. You know, this one that seems all too forgotten: “Simplicity -- Maximizing the amount of work not done is essential.” One organization did just that and Tim and Brandon will show you the real benefits that can be gained from radical and surprising simplifications of the process. Far from promoting defiance or forcing compliance we learned to reach better degrees of cooperation, flow, and (yes, the P word) productivity through radical simplification.
Could the same happen for you?
Learning Outcomes: - Consider adaptations beyond "conformance" to XP and Scrum
- Reconsider your best practices
- Evaluate changes according to your needs
- Appreciate more profound questions than "how to implement X"
