Conference Presentations

Successful Process Improvement - The Agile Way

Using agile techniques to develop and implement new processes-whether for use in agile environments or not-will increase stakeholder involvement and buy-in, lower cultural resistance, reduce process development cycle time, and encourage continuous process improvement. Join Nelson Perez as he explains how to translate the core principles of the Agile Manifesto into a context that you can apply to any process development and improvement program. Use the Agile Manifesto values and principles to speed up your process improvement initiatives and ensure its success. Based on his experience in a company with a highly resistive culture, Nelson realized that process improvement approaches must be tailored to each situation-what works consistently in one organizational culture may not be useful in another culture down the street, across town, or in another country.

Nelson Perez, Sierra's Edge, Inc.
Better Software Conference 2008: Agile Software Testing Strategies

Test automation is like exercise. We know both are great ideas, but most of us don’t do enough of either. Although we know that creating a solid automated test suite is critical to any agile testing strategy, we are often just told to "Do it" without much support-money or people. Jared Richardson examines the infrastructure and tools needed for your automated testing to succeed and prosper. Jared examines three strategies-test-driven development, defect-driven testing, and blitzkrieg testing-you can use to ensure great test coverage on your projects. You'll gain an understanding of how to leverage your testing investments by employing continuous integration practices in your development projects. With real-life scenarios as a backdrop, Jared discusses appropriate testing strategies for your current project or the next one down the road.

Jared Richardson, 6th Sense Analytics
Agile Leadership: Coaching Great Teams

When adopting agile methods, many project managers find it difficult to move from a traditional, control-based model to a servant-leader based model. This paradigm challenges managers to their core because agility demands a coaching-driven mindset rather than the classic "I'm-in-charge" view. Explore the core aspects of agile leadership and team coaching with Bob Galen as you look at leadership from an agile perspective. Bob discusses "coaching up" the team as part of an agile adoption strategy and offers a conversation framework you can immediately use at work-and at home. Learn the fundamental coaching patterns and anti-patterns as you find out when to step in to help and when to be patient. You'll have the opportunity to practice a conversation or two and hone your new coaching skills.

Robert Galen, RGCG, LLC
You Just Don't Understand Me: Interdisciplinary Awareness to the Rescue

Different disciplines and departments in an organization often have the same goals, but often misunderstand one another. We have all heard someone say about another group, "Those people are clueless." The irony is that "those people" are saying the same thing back under their breath. Within the software disciplines, poor understanding, lack of communication, and unfortunate stereotyping are often commonplace. Presenting a new concept and team exercise called Interdisciplinary Awareness, Mike Tholfsen helps us focus on the importance of team dynamics in building good software. With case studies from both Microsoft Office and Windows teams, Mike shows how they built stronger trust within and between teams. Incorporate this exercise in your group and discover how interdisciplinary awareness can lead to greater understanding and appreciation, a stronger sense of team, and a higher degree of trust.

Michael Tholfsen, Microsoft Corporation
A Kanban System for Software Engineering

Ideas from Lean Thinking have been growing in popularity with the Agile software development community. Over the past year, the use of kanban (literally signal cards) popular in manufacturing has been seen as the significant innovation in managing agile work and is growing in adoption at firms such as Yahoo! David Anderson introduced the first electronic kanban system at Microsoft in 2004 and has since extended the technique through his work at Corbis. Kanban acts to limit work-in-progress and focus the team on achieving a continuous flow of value to the customer. Kanban innovates on accepted agile management practice by providing an iteration-less process with a regular release cadence. It helps achieve a balance of demand against capacity on the team and eliminate multi-tasking. David will present a brief history of the technique through case study reports from teams at Microsoft and Corbis.

David Anderson, Modus Cooperandi
Better Software Conference & EXPO 2008: Pragmatic Agility - Principles, Not Dogma

You've got questions. Andy Hunt has answers. What is agile software development all about? Why the sudden popularity of agile? Why is it fundamentally different from other approaches? Will it work for my organization and me? Join Andy, one of the seventeen original signatories of the Agile Manifesto and a founder of the Agile Alliance, for his pragmatic take on the answers to these and your other questions. Look at the foundations of agile software development and see what problems agility seeks to address. Don’t be distracted by dogma as you take some time to explore the core aspects of agile development. Andy presents a brief overview of the major agile methodologies and walks you through a typical day in the life of an agile developer. Find out what's really important about the agile approach and take back new ideas to help you transition to agile while avoiding common stumbling blocks.

Andrew Hunt, Pragmatic Programmers
More than the Process Police: CMMI® Process and Product Quality Assurance

For organizations to succeed in process improvement efforts, they must determine whether newly introduced processes are, in fact, being adopted by managers and practitioners. The Capability Maturity Model Integrated (CMMI®) identifies this verification activity as Process and Product Quality Assurance (PPQA). If you think PPQA is simply "process police," you're not getting all that you should out of your CMMI® practices. Done right, PPQA can be a driving agent for change in your organization. Unfortunately, all too often PPQA ends up little more than a post-mortem review of what was done wrong. That approach, which offers little opportunity to change behavior, not only lowers the value of the process, but also hampers change management efforts. Will McKnight demonstrates the potential of an efficient PPQA process.

Will McKnight, Next Level Consultants
Agile in the Non-Agile Enterprise: Hurdling Obstacles

Agile is entering the mainstream as a software development practice and leading wider organizational change in many companies. However, in large organizations, it's not practical just to "flip a switch" and have your entire software department "go agile" all at once. In that situation, agile and non-agile teams must work together during the transition. Agile teams must continue to interface with their company's business processes, while management must streamline traditional processes and activities. Agile teams face many obstacles in their quest for cooperative development--resistance to change; differing culture and value systems; changes to measurement, evaluation, and reward systems; and new contracting terms. Join Michele Sliger as she explains how to clear these and other common hurdles facing agile teams working in a traditional organization.

Michele Sliger, Sliger Consulting, Inc.
Flow, Pull, Innovate: The Secrets to Agile Adoption

Jean Tabaka provides straightforward guidance on how teams can begin their agile journey and learn to mature and scale into more and more discipline. The five-step approach emphasizes a path based on the principles of Lean Thinking-Flow, Pull, and Innovate. Each of the five steps outlines specific practices for growth as well as pitfalls and roadblocks to navigate and avoid. Step 1: The team learns to work in a continuous flow. Step 2: The team matures by pulling ready items from the backlog. Step 3: A group of teams adopts and scales up the individual team practices. Step 4: The scaling continues to cover multiple projects. Step 5: The practices are adopted throughout the entire organization. You can apply the disciplines discussed in this class to a single co-located team, a team of teams, or an entire organization eager to take advantage of both agile and lean approaches.

Jean Tabaka, Rally Software Development
The Good, the Better, and the Rather Puzzling: The Agile Experience at Five Companies

Strategic software development is happening every day-and failures continue to plague us. Unquestionably, a major paradigm shift is underway with the movement to agile methods. But are they really working? With results drawn from industry statistics, Michael Mah answers vital questions about the effectiveness of agile methodologies-XP, Scrum, TDD, pair programming, etc. One discovery underway is that agile methods could be turning the "law of software physics" upside down. For decades, there have been predictable relationships among schedule pressure, staff ramp-up, and bug rates; now, industry data tells us that all this could be changing with agile. Join Michael Mah for a revealing discussion of productivity findings at five-all ostensibly agile-companies, and how they produced a range of results for time-to-market, productivity, and quality.

Michael Mah, QSM Associates, Inc.

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.