Agility as a process is well understood today in feedback generating iterations or as a flow. Agility as a structure is becoming better understood through cross-functional teams working collaboratively. However, Agility as a culture has very little exposure - yet culture impacts every attempt at agility.
This session provides a language for organizational culture, its impact on agility, and examples where exposing culture has aided adoption. We explore cultures within single organizations, sub-cultures across boundaries within larger organizations, and cultures bridging a corporate merger.
Agenda\nIntroduction\nOverview\nUpdate on Adoption\nBrainstorm\nNext Steps\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Scrum is a tool that we use for lean software development\nWhole Team-based approach in defining and developing solutions in short, fast cycles\nSimple Product Backlog which is estimated and prioritized by value, cost, risk and learning\nShort time-boxes to fully develop and test items in the backlog to generate feedback from customers and stakeholders\n