Agile Dev Practices West
 
Our Promise to You

http://www.sqe.com
 
 
 
Agile Dev Practices West 2012
Wednesday Concurrent Sessions
Wednesday, June 13, 2012 12:45 PM
AW1
Scaling Agile
Agile Architecture Practices for Large Scale Agile Development C Scott Ambler, IBM Rational Although “agile architecture” may sound like an oxymoron to you, the reality is that a simple, elegant architecture is a key enabler of any successful system, particularly large scale ones. Scott Ambler describes agile architecture practices—at both the project and enterprise level—that form a middle ground between the extremes of big architecture up-front and outright hacking. Scott discusses agile modeling practices—initial architecture envisioning, proving an architecture with working code, and just-in-time model storming—that enable agile teams to benefit from architectural modeling without suffering the drawbacks of detailed design documentation. Beyond architecture, Scott introduces agile design techniques—continuous integration (CI), test-driven development (TDD), and refactoring—that build on and provide feedback to an emergent architecture. To illuminate the importance of agile architecture strategies, Scott discusses these topics within the context of the Disciplined Agile Delivery (DAD) methodology, a hybrid agile framework covering the full delivery lifecycle. Learn more about Scott Ambler
Wednesday, June 13, 2012 12:45 PM
AW2
Agile Implementation
Adding Good User Experience Practices into Agile Development C Jeff Patton, Comakers, Inc. Whose job is it to ensure that the user has a good experience with a new application? As agile processes are taught today, the user experience (UX) design practice is usually left out or at best described as an optional team role. However, the companies that build useful, usable, and desirable software know that UX is baked into the whole development process. Jeff Patton describes what user experience design is and isn’t, and how every person on the team has something to contribute. Hear concrete examples of how companies have adapted their UX practice to work well in an agile context and, along the way, discovered innovative UX practices that work better in agile contexts. Jeff explores pragmatic personas, guerrilla user research, design sketching, lightweight prototyping, and concept testing. Leave with valuable tips for adding UX practices and thinking to your agile process to help you get good user experience. Learn more about Jeff Patton
Wednesday, June 13, 2012 12:45 PM
AW3
Kanban
Transitioning Your Team to Kanban: Theory and Practice C Gil Irizarry, Constant Contact You’re familiar with agile and perhaps practicing Scrum. Now, you want to learn about Kanban to see if it is something to add to your development toolkit. Can Kanban help you? How does it differ from Scrum and other agile methodologies? Kanban is quickly being adopted by teams that want to improve their productivity. Kanban focuses on continuous flow and incorporating the theory of constraints which together allow teams to improve and streamline their product delivery. Learn about Kanban—not only the theory, but also practical lessons on transitioning your team to Kanban. Get insight into moving from Scrum to Kanban and pick up techniques that can aid any team. See cumulative flow diagrams, WIP (work-in-progress) limits, classes of services in action, and hear about other ideas from the Kanban toolset. Come and grow your agile repertoire! Learn more about Gil Irizarry
Wednesday, June 13, 2012 12:45 PM
AW4
Agile Testing
Agile Testing: Challenges beyond the Easy Contexts C Bob Galen, iContact Don’t let anyone tell you differently: agile testing is hard! First, we have to get over the misconception that you don’t need testers within agile teams. Then, we have to integrate testers with the developers and engender a holistic quality approach. And those are only the challenges when the going is easy! In more difficult contexts, testing in agile environments is—well, even more difficult. Bob Galen explores how to handle testing in difficult contexts—lack of test automation capabilities, agile in highly regulated environments, testing when your team is spread globally and real-time interactions are nearly impossible, and more. He describes contexts and approaches for blending existing, traditional testing techniques with their agile counterparts. With real-world examples, Bob describes how teams have achieved a good working balance between the two—for example, in test planning and quality metrics reporting. If your agile project is in a difficult testing context, come with your big issues and expect some new options, but no silver bullets. Remember—it’s hard! Learn more about Bob Galen
Wednesday, June 13, 2012 2:30 PM
AW5
Becoming Agile
Designing Agility Practices that Last C David Hussman, DevJam Every day more agile practices and styles emerge, overlap, and compete. This proliferation challenges you to choose from among XP, Scrum, lean, Kanban, or the ways of the emerging Lean Start Up crowd. Rather than stumbling down one path or another, join David Hussman as he shares tools for assessing and designing an agile process with practices that address your specific needs and constraints. David starts by teaching a simple assessment process to help you understand where you are today. Then, he offers ideas for selecting a meaningful set of practices and moves on to teach you how to create a meaningful and measurable coaching plan. David covers the selection of product planning tools, iterative delivery tools, tracking tools, and more. If you want to clear the fog about which agile practice will really help you, come for some answers. Even if you don’t yet know what questions to ask, David can help. Learn more about David Hussman
Wednesday, June 13, 2012 2:30 PM
AW6
Agile Implementation
Agile Metrics: Velocity Is Not the Goal C Michael Doc Norton, LeanDog, Inc. Velocity is one of the most common metrics used—and one of the most commonly misused—on agile projects. Velocity is simply a measurement of speed in a given direction—the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team? Michael “Doc" Norton walks us through the Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project's overall health. Learn more about Michael Doc Norton
Wednesday, June 13, 2012 2:30 PM
AW7
Kanban
Why Continuous Improvement Programs Fail: Can Kaizen and WIP Help? C Michael DePaoli, VersionOne If you have established an agile or lean development approach and aren’t experiencing meaningful innovations or improvements in your process, this session is for you. Michael DePaoli shares an interdisciplinary understanding of why change initiatives so often fail and what to do about it. Join Michael and your peers to explore the neuroscience behind change and review the patterns of cultural, organizational, and behavioral dysfunction that impede improvement efforts. To address these challenges, Michael explores the kaizen philosophy of change and why optimizing from a current situation is often better than attempting revolutionary changes. Through the use of an innovation game, you’ll have an opportunity to share your challenges with continuous improvement and work with Michael and other participants to map out a new approach. Learn how to cultivate a kaizen culture and apply work-in-progress (WIP) limits to achieve a continuous improvement competency within your development approach. Learn more about Michael DePaoli
Wednesday, June 13, 2012 2:30 PM
AW8
Agile Testing
Testing Traps to Avoid on Agile Teams C Janet Gregory, DragonFire, Inc. Why do many agile teams fail at testing? Iterations turn into mini-waterfalls with testing at the end; stories never become “done” and carry into the next iteration with unresolved bugs; testers worry they’re losing control or being set up to fail; customers keep changing their minds after all the tests have passed. However, some teams do succeed with testing on agile projects. What do they do differently? Janet Gregory shares the lessons she’s learned that help teams—and especially testers—get agile right. With examples from her real-world experiences, Janet describes the testing traps and the practice or process to help fix each one. One example is “forgetting the big picture”—so easy when you are testing small, granular stories. A practice to put in place that avoids this trap is implementing feature acceptance tests to supplement story acceptance tests. Janet outlines the basic steps you can take that can make the difference between success and failure. Learn more about Janet Gregory
Wednesday, June 13, 2012 4:00 PM
AW9
Becoming Agile
Signs Your Agile Adoption Is Off Track—And How to Fix It C Thomas Stiehm, Coveros, Inc. Adopting agile is often a difficult proposition with many variables and sometimes uneven results. Recognizing when your adoption isn't working well and taking pro-active actions to put it back on track are essential. So, how do you know if your adoption is proceeding through rough but expected waters or running the risk of failing? Thomas Stiehm describes the signs of serious adoption problems and the steps you can take to fix them. Leveraging ten years of experience helping teams adopt agile, Tom walks through the many successes and failures he’s seen and, more importantly, the mistakes companies and people made that led to those failures. Learn the remediation steps you can take to re-energize and re-center your adoption efforts. Don’t let small missteps cascade into failure. Instead, join in and take back an action plan that’s sure to increase the odds of making your agile adoption a win for you, your teams, and your company. Learn more about Thomas Stiehm
Wednesday, June 13, 2012 4:00 PM
AW10
Agile Implementation
The Science of Lean C Karl Scotland, Rally Software Development Science is the building and organizing of knowledge into testable explanations and predictions about the world; lean is an approach which recognizes and leverages many scientific discoveries to enable faster flow, higher value, and greater capability. When thinking about opportunities for continuous improvement, science and lean should go hand in hand. Karl Scotland explores some of the science behind lean—from mathematics to neuroscience—in order to explain why and predict how various practices can have a positive impact on the way we work. Gain a deeper understanding of both the science of lean and how to take a scientific approach to learning in order to reap the benefits of paying attention to people, process, and economics. Leave with richer insights into why and how lean approaches work, and the ability to apply the science—and a scientific approach—to your own teams and organizations. Learn more about Karl Scotland
Wednesday, June 13, 2012 4:00 PM
AW11
Agile Techniques
Test-driven Development: An On-stage Demonstration C Llewellyn Falco, DevelopMentor Test-driven development (TDD) is a skill that takes patience to master—you can’t learn it reading a book. As with learning any new language, to gain fluency you need to practice TDD with competent coaching and lots of hard work. Many well-intentioned programmers try and finally give up on TDD because they never develop the fluency it requires. On stage, Llewellyn Falco leads a live TDD demonstration, talking through the process and microsteps of: (1) studying a feature, (2) creating an initial test, and (3) iteratively developing the related test code and feature code until the feature is completely programmed. Watch how to iteratively write a test, see it fail, and then write the feature code to make it pass. After explaining the theory behind the particular TDD technique used, Llewellyn leads participants in testing progressively more complex objects and scenarios. Learn more about Llewellyn Falco
Wednesday, June 13, 2012 4:00 PM
AW12
Agile Testing
Acceptance Test-driven Development: Tests with the Future in Mind C Jeff Cheezy Morgan, LeanDog, Inc. Acceptance Test-driven Development (ATDD) is a popular topic these days—everyone’s excited about the idea of writing tests prior to development. Yet many teams run into difficulties as they attempt to implement this practice. It’s all too easy to fall into the trap of writing acceptance tests that mostly specify keystrokes and button clicks. Join Cheezy Morgan as he offers an overview of ATDD while sharing his experiences and insights gained working with numerous teams implementing ATDD. Cheezy will take you on a journey of discovery, demonstrating practical techniques for writing ATDD tests that describe the essence of what they are specifying while hiding unnecessary details that obfuscate their meaning. Because ease of maintenance is a key to ATDD’s long-term ROI, Cheezy shows how to structure and layer test code to reduce brittleness and fragility so your ATDD test suite will retain its usefulness well into the future. Learn more about Jeff Cheezy Morgan


Top of Page
 
Send us Your Feedback