People & Teams

Conference Presentations

Testing Lessons Learned from Extreme Programmers

One of the things testers often notice about Extreme Programming (XP) is that there is no defined role for testers on the team. Yet XP teams describe themselves as "test infected." They practice Test-Driven Development (TDD), writing executable unit tests before writing the code to be tested. Many teams practice Acceptance Test-Driven Development (ATDD), writing executable acceptance tests before implementing a feature. They use continuous integration to give them rapid feedback about the effects of changes. They practice pair programming, a technique that results in all code being peer reviewed before it's checked in. In short, XP teams test continuously from the very first moment of any given project. You could even call them "test obsessed." That obsession helps explain why Elisabeth Hendrickson, author of Test Obsessed, likes XP teams so much.

Elisabeth Hendrickson, Quality Tree Software, Inc.
Scrum: Roadmap for Implementation (Part 2)

With quite a few successful agile implementations under his belt, Hubert Smits guides you through the steps for implementing Scrum in an organization. Scrum implementation grows from a single team working on a pilot project, to multiple development programs running in parallel-all with Scrum as the underlying methodology. Hubert explains how to train and motivate your pilot teams and replace your project requirements documents with a backlog. He outlines the roles of architect, business analyst, and tester in a Scrum-led project. Learn what happens when multiple teams have to work together and how dependencies between teams are discovered and managed. Find out how change management becomes an integral part of the project and discover new management tools that you can use in an agile project.

Hubert Smits, Rally Software Development
Climbing the Decision Tree: Reaching High Quality Team Decisions

When teams "go agile," members of the whole team take on greater responsibility for thinking and deciding as a unit. Though individual team members may know how to make great individual decisions, few people bring the skills or perspective needed to make high quality decisions as a group. Teams need to plan for all elements of high quality team decisions, balancing technical quality, commitment to implementation, efficiency, and opportunities for team development. Rather than relying solely on a consensus model, an effective team will have a repertoire of decision-making methods and select the best approach for their decisions before they face each choice point. Diana Larsen introduces a decision tree model for teams and covers the what, who, when, where, why, and how of team decision-making.

Diana Larsen, FutureWorks Consulting
Scrum: An Introduction (Part 1)

Scrum is the most popular agile project management method today. Hubert Smits illustrates the basics of this method based on his experiences in implementing Scrum in many organizations. He explains the concepts of Scrum to software developers, development managers, and CIOs who are adopting-or thinking about adopting-Scrum in their organizations. After discussing the position of Scrum within the agile world and comparing it to methods like Extreme Programming and Lean Software Development, Hubert takes you through the full Scrum methodology and explains the meanings and practical implementations of Product Backlog, Sprint Planning, Product Increments, and Retrospectives. Join Hubert for a highly interactive discussion of this important project

Hubert Smits, Rally Software Development
Using the Theory of Constraints to Coach Agile Teams

Even as a large number of teams are adopting agile methods, some teams are finding this transition to be a big leap. Because each team is unique, they are not able to follow all of the practices "by the book." Each team must customize certain practices to best suit its needs and abilities. Naresh Jain shares his experiences guiding agile teams through this transition. He introduces a technique of coaching teams that employs Goldratt's Theory of Constraints to identify the bottlenecks and issues faced by the team during the agile adoption process. Naresh shows how more experienced agile teams can use the Theory of Constraints technique as a just-in-time practice to eliminate bottlenecks and deliver new knowledge and experience to the team.

Naresh Jain, ThoughtWorks Technologies (India) Pvt. Ltd.
Flow, Pull, Innovate: How Agile Teams Mature and Scale

Jean Tabaka offers straightforward advice on how agile teams can mature and learn to scale up to larger and larger projects. The three steps of her approach emphasize a path based on principles of Lean Thinking--Flow, Pull, and Innovate. Flow is about creating smooth delivery of value. Pull is the way teams pull ready items for delivery, and the business pulls ready, tested, and valuable features into productive use. Innovate is about how the organization drives improvements rather than merely responding to issues. For each of the three steps, Jean outlines practices for growth and identifies pitfalls to avoid and roadblocks to navigate around. 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. Join Jean and learn to achieve the greatest innovations with a much lower risk of failure.

Jean Tabaka, Rally Software Development
Pragmatic Learning: Improve Your Learning Skills (Part 2)

Your approach to learning a new technology or acquiring a new skill is key to your personal success. So, how do you learn how to learn? What tricks can you use to learn faster and retain more of what you learn? Andy Hunt presents a brief recap of The Dreyfus Model for learning and explains how you can learn more deliberately by managing your “knowledge portfolio.” Andy explores practical learning techniques including mind maps, reading techniques, and situational feedback. During this class, he shows how these techniques fit in to the cognitive model discussed in “Refactoring Your Wetware (Part 1).” Andy describes methods ranging from the tried-and-true to the truly exotic that he uses to cope with the veritable torrent of new information that assaults each of us. Andy’s promise? "You'll learn one proven technique that can improve your daily productivity by 20%-30%."

Andy Hunt, The Pragmatic Programmers
Building Agile Workspaces

An agile team needs a workspace that supports highly collaborative ways of working together. The team needs to be able to sit together and have visible "information radiators" of the latest status on planned work and code quality. Some teams also boost their spaces with "eXtreme Feedback Devices" such as lava lamps and audio signals linked to automated processes. It is vital to ensure that feedback mechanisms within the agile workspace are easy to interpret and low maintenance. Join Rachel Davies to explore different ways to set up your agile workspace for maximum fun and productivity. Discover different ways to present information to the team and some snags to watch out for. If you or your team is new to agile development, this class is for you.

Rachel Davies, Rachel Davies
Management Mindsets: What's So Different About Agile

You've probably heard of Theory X, Theory Y, and Theory Z management styles. Even though we've run out of letters at the end of the alphabet, it's time for a new management theory for self-organizing agile teams. Esther Derby examines what parts of a manager's job stay the same and what parts diminish as the team manages its own work. She discusses the new roles for managers in agile organizations: team coach-creating an environment for success and helping the team improve their teamwork; team champion-helping the team interface with the rest of the organization; boundary manager-keeping distractions at bay and making sure the team has what it needs; risk manager-anticipating and mitigating risks; and organizational influencer-looking across the organization and removing impediments. Although your role as manager changes as you embrace agile practice, there's plenty to do. Plus, it's even more fun!

Esther Derby, Esther Derby Associates Inc
Introduction to User Stories

Agility is often described in terms of iterative development. In fact, it's more of an iterative analysis process with the code being written and tested immediately after the requirements are discovered. The heart of this process is the user Story, a collection of requirement descriptions, value statements, cost estimates, architecture designs, and test cases-all rolled into one. While at first glance user Stories seem simple, they play a key role in all agile methods. What makes a good one? How do you write it? How do you make them the right size? Alan Shalloway answers all of these questions and more in this thought-provoking class. Unfortunately, it is not enough just to create a collection of stories. We need a way to organize them and to plan for their release. Alan concludes by discussing these important organizational issues.

Alan Shalloway, Net Objectives

Pages

AgileConnection is a TechWell community.

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