Transformation to Greater Business Agility
To achieve the true promise of agile it isn’t enough to pilot a few Scrum teams or buy a tool. You must start by sharing enterprise strategy across all of your agile teams. Visibility into the strategy empowers teams as they prioritize the work they want to deliver, and connects the teams enabling greater collaboration
Agile development practices typically break down as you scale across teams and across the broader organization.
- Teams have too much Work in Process
- Teams don’t coordinate their work
- Teams work on the wrong priorities
- Strategy and execution are misaligned
At CA, we’ve learned that delivering high value software to customers requires multiple, coordinated, strategically aligned development teams working together to plan and execute a release. Scaling across teams and the organization is where Agile development practices typically break down, making it challenging to develop a realistic, actionable delivery plan.
Outline/structure of the Session
- What we think we know
- Business obstacles to agility
- Architecting a new system for agility
- Business outcomes and impacts
- 5 steps to build business agility
- Case study
- Add automation when it's needed
- Creating a shared purpose
- Bias for action
- Why team level agile alone is insufficient for significant improvements to business outcomes
- What are the 5 steps to build business agility
- Why process before tooling/automation, but, you need both in the end
- Disruptive agility is not just for software development
Executives, Program Managers, Product Owners, Business Owners or anyone interested in why team level Agile alone is insufficient for significant business impacts
- Have a basic understanding of team level Agile (Scrum and/or Kanban) and the ceremonies associated with it.
- Have a desire to seamlessly connect business strategy with team level execution.