The Executive’s Guide to Disciplined Agile: Business Agility for Established Enterprises
An agile enterprise increases value through effective execution and delivery in a timely and reactive manner. Such organizations do this by streamlining the flow of information, ideas, decision making, and work throughout the overall business process all the while improving the quality of the process and business outcomes. This talk describes, step-by-step, how to evolve from today’s vision of agile software development to a truly disciplined agile enterprise. It briefly examines the state of mainstream agile software development and argues for the need for a more disciplined approach to agile delivery that provides a solid foundation from which to scale. We then explore what it means to scale disciplined agile strategies tactically at the project/product level. We then work through what it means to strategically scale across your IT organization as a whole and discover what a Disciplined DevOps strategy looks like in practice. Your Disciplined Agile IT strategy, along with a lean business strategy, are key enablers of a full-fledged disciplined agile enterprise. The talk ends with advice for how to make this challenging organizational transition.
Outline/structure of the Session
In this talk we will work through the following topics:
- The race car metaphor for enterprise agile
- The current state of enterprise agile
- Why Disciplined Agile?
- Disciplined Agile Delivery (DAD)
- Disciplined DevOps
- The Disciplined Agile IT (DAIT) Department
- The Disciplined Agile Enterprise (DAE)
- From Transformation to Continuous Improvement
- Learn how agile delivery works beginning to end with enterprise-class organizations
- Understand what it means to tactically scale agile delivery
- Understand what it means to strategically scale agile techniques across your IT department
IT and business executives want to learn about business agility in the enterprise; Experienced agile coaches wanting to take it to the next level
Fundamentals of agile
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Joey Spooner - Using the Kanban Method to "grow up" our businessJoey SpoonerTeam LeadTriTech Enterprise Systems
schedule 1 year agoSold Out!
Running a small business is no small task. Financial management, sales, hiring, managing people, and supporting existing clients are just a handful of activities a small business might address in a single day. So what happens when you use the Kanban Method to manage your business?
I’ll share my experiences while training, coaching, and evolving a small business using the Kanban Method. You’ll see how the Method quickly surfaced issues, revealed hidden opportunities for innovation, and how the business is using the Method to mature the services they offer.
Patrick Steyaert - Business agility – A new way of thinking and a new way of teaching and coaching agilityPatrick SteyaertFounderOkaloa
schedule 11 months agoSold Out!
Business agility is more than the sum of different organizational units that each implement their own chosen agile method on their own little island, constrained by 20th century management. Nor is it a one-size-fits all model that is imposed from the top down. Business agility requires the engagement of the entire organization in a fundamentally new type of thinking. Especially when the (deep) divide between organizational silos risks being reinforced by the islands of agility formed by the, sometimes dogmatic, implementation of different agile methods in different parts of the organization. It also requires creativity and insight to overcome the relics of a 20th century management system. Especially when the thinking that underlies division of labour, capacity utilization, and predictive control still runs very deep. Finally, it requires a new type of change that is resilient to setback.
This presentation reports on our experience with teaching and coaching business agility to a wide range of audiences without digressing into specific agile methods. On a tactical level, we discuss how we developed and use business simulations that engage and mobilize all levels of the organization (including higher level management) across all functions (not just IT, but also HR, Marketing and communications, Finance, Legal, Product management, …). We discuss simulations that allow participants to experience the basic concepts of flow, self-organization and active learning; not just simulations at the team level but also at a cross-team level and across the entire value stream (upstream and downstream). Simulations that are generic enough in order to speak to different parts of the organization, but specific enough as to realistically represent real-life work situations.
On a more strategic level, we discuss how to challenge the traditional linear, reductionist, local optimization thinking (“either-or” thinking) about agile and how to teach integrative, applied systems thinking (“and” thinking) as a new foundation for agile business. Using integrative thinking we will explain how the foundational concepts of flow, self-organization and active learning can be shown to build on each other in order to create a whole that is bigger than the sum of the parts. By setting aside any dogmatic discussions, it builds a common, deeper, understanding between practitioners of the different strands of agility. By using simulation, it allows to overcome the habitual 20th century thinking and prepare for 21st century business agility.
Paul Boos - Full Life-Cycle ContractingPaul BoosIT Executive CoachExcella
schedule 1 year agoSold Out!
Have you wondered what helps make contracts deliver better results? It's not specifying Agile approaches, but thinking of the development life-cycle, its impacts, and asking for demonstrable understanding of Agile approaches.
This short talk will discuss how a contract vehicle was established at the Environmental Protection Agency to improve contractor accountability and more importantly improve system reliability. It will include a short discussion of what next steps for following contracts should be included.