| Leading Change to Agile |
|
|
Title of Presentation: Leading the Change to Agile in a Six Sigma Organization Short Abstract and Outline: This session will focus on expected frustrations (and strategies for dealing with them) when a process-centric IT organization faces Agile for the first time. This session will describe lessons learned from piloting Agile teams within a process-focused organization. Six Sigma and DMAIC are appropriate for reducing variation in quick cycle-time, repeatable processes, but not software development. DMAIC techniques have slowed down productivity in software development by attempting to decompose a naturally empirical problem into unrepeatable activities. If your IT organization is structured by process area (e.g. Systems Analysts, Systems Testers, UI Designers, Enterprise Data Modelers, etc.), then you will want to attend to learn about: • DMAIC: an Agile Anti-Pattern • Wasted Effort (why waterfall works, but Agile works better) • Must-haves before you start an Agile pilot • Frustrations you should expect • Productivity gains you should expect (and how to measure) • Winning the metrics game • Winning the status game • Productivity will get you noticed • Leveraging your organization's discipline • Intangibles, and how to make them tangible • The Agile-V: The Perfect Daily Status • Get what you measure • Warning Signs • Transform process-driven discipline to test-driven productivity • System Testers can be your best friend • Dependent • Demonstrating Discipline • Exposing dependencies • Intangibles This presentation is a joint evolution from consulting engagements and regular presentations to senior management to track the progress of Agile rollout experiences. |
| < Prev | Next > |
|---|
| Seminars Details |
|
We offer seminars and executive briefings on agile software development. These are content filled seminars and are the pedigrees of the same high quality seminars we deliver at conferences nationwide.
Formats Delivery Mechanisms If this is delivered presented to a large audience (50+) then it would be classic presentation with light Q&A encouraged throughout. Our preference is to break this up into small group discussions (5-7 at a table) and then shift back to larger group summary. This format allows participants to personalize the information presented with a stronger feeling of value. One presenter can orchestrate this well only for groups less than 45. Ideal, would be to add a co-presenter for delivery. Then we would demonstrate agile behaviors through an interactive dialog and we could handle a larger number of people with small group discussion break out and large group summary (60-70 folks with small group discussions and large group sumamry). Groups larger than 70+ would be done via a lively interactive dialog with the two presenters and light Q&A from the audience. |
|
• Scrum Adoption • Intentional Change • Analysis • Facilitation • Retrospectives • Agile Transitions Each coaching enagagement requires a certain amount of hand crafting please Contact Us for more. |