90 minutes

Pragmatic Personas: Putting the user back into user stories

room: Columbus KL — time: Wednesday 09:00-09:45, Wednesday 09:45-10:30
Level: Introductory

Persona put the user back into your user stories.

While we understand that our users are important we may lack language for talking about them. If you already know about persona you may find your approach for performing research and representing user data as a user persona to be time consuming and, what’s more, the persona you create simply aren’t being used. In this short tutorial you’ll learn to create simple relevant persona for your agile project, how to communicate them to the team, and how to use them generate valuable feature ideas, and design imperatives for your product.

Mylyn: Redefining the "I" of the IDE

room: Grand Ballroom C North — time: Wednesday 09:00-09:45, Wednesday 09:45-10:30
Level: Introductory

Not long ago the notion of a tool that hides more of the system than it shows sounded crazy. To some it still does. But hundreds of thousands of Mylyn users have made next big evolution of the IDE clear. Stories and tasks are more central than source code, focus is more important than features, and integration with the agile workflow is the biggest productivity boost since code completion. This talk will demonstrate the concepts of the task-focused interface and look ahead at how we are redefining the “I” of the IDE by personalizing the user experience around the agile process.

Selenium and JBehave : A surprisingly successful shotgun wedding

room: Grand Ballroom E — time: Monday 14:00-14:45, Monday 14:45-15:30
Level: Practicing

Selenium is the 800lb gorilla of open source web application testing. For four years it has been steadily gaining a following and making a difference for corporations large and small. Such tools have always been a trap for adept Agile teams though. Too often teams rely on functional testing and skimp on the much more effective ‘small’ unit tests. Now with JBehave steering Selenium, we’re seeing test scripts emerge that engage formerly perplexed management and business folks. The time has come for this type of tool pairing to be valued for its role in validating Agile in the enterprise

Where Does Developer Testing End and Tester Testing Begin?

room: Grand Ballroom D North — time: Monday 14:00-14:45, Monday 14:45-15:30
Level: Practicing

This is a trick question, right? In agile, everyone works on the same items together, at the same time. Yet, the reality is we’re not all interchangeable cogs. Developers and testers each bring their own, unique skills to the table. The key to effective agile is not minimizing our differences, but building upon the strengths each person brings to the team. Join us for this hands-on simulation and retrospective as developers and testers explore how agile teams build quality into their process, how each member contributes to that quality, and how we can avoid traditional testing pitfalls.

Deep Democracy: A Radical Approach to Hearing from Every Voice

room: Crystal A — time: Thursday 09:00-09:45, Thursday 09:45-10:30
Level: Practicing

This session is an explanation and demonstration of Deep Democracy, primarily aimed at coaches interested in learning new techniques. Deep Democracy—originated by Arnold Mindell—maintains that a well functioning group is dependent on all the voices, positions and views in the group being heard and valued. We will start with the definition, origins and applications of Deep Democracy, then conduct a Large Group Process in which all can directly experience the power of this approach. In our debrief, we will harvest the wisdom of the group, and explore practical uses in Agile team situations.

Mission Impossible: TDD and JavaScript

keywords:
room: New Orleans — time: Tuesday 11:00-11:45, Tuesday 11:45-12:30
Level: Practicing

JavaScript has earned a special, dark place in most programmer’s hearts as it is a necessary evil for making the web experience dynamic. You are test-driving your JavaScript, aren’t you? If not, why not? If the reason is that you don’t know how, or haven’t taken the time to learn the various testing frameworks, then this session is for you. We will briefly explore the various testing frameworks, build our own lightweight framework, and then test-drive a small bit of functionality using it.

Can you hear me now? Good...

room: Crystal A — time: Tuesday 16:00-16:45, Tuesday 16:45-17:30
Level: Practicing

This tutorial focuses on the detailed specifics that will make distributed agile meetings effective. We will demonstrate several key agile meetings, run in a distributed fashion, so teams can immediately improve their projects. To do so, I will highlight specific tools available in the market place to facilitate each of these different kinds of discussions (retrospectives, planning meetings, stand ups). I’ll demonstrate the processes to enable more effective communication between remote locations and describe the key roles required on a project to encourage the best exchange of information.

Overcoming Agile ADHD

Level: Practicing

Fear of decision making often leads teams to exhibit one or more of the dysfunctional symptoms of Agile ADHD. This tutorial will help agile practitioners overcome the fear of decision making by first embracing that there are no right or wrong decisions. Agile development is ultimately driven by a series of decisions, all of which are made in the face of uncertainty. Tutorial participants will take away principles and practices that enable their team to embrace uncertainty and be proactive in making better decisions at the most responsible moment.

Activity Theory for Manifesting Agile

room: Columbus GH — time: Wednesday 09:00-09:45, Wednesday 09:45-10:30
Level: Introductory

Agile development means self-management, collaboration, and working towards shared goals. Agile practices support much of this, but we can still learn more, both to better understand current practices and to develop new ones. This session is an introduction to cultural-historical activity theory, a psychological framework for understand collaborative behaviour. The framework has shown the role of tools in cognition and collaboration, and understanding structural tension between different activity systems: it can also be used to understand and improve agile software development.

Why Is Testing So Slow?

room: Grand Ballroom D North — time: Thursday 09:00-09:45, Thursday 09:45-10:30
Level: Practicing

Why is testing so slow? Why is testing taking so long? We’ve done lots of things to speed up testing, but we still face this time crunch when we get to the end of the iteration; then we find out from the field that there are problems that we didn’t anticipate. In this workshop, we’ll gather familiar patterns that slow down testing, and discover a few more in the process—and maybe we’ll find that the slowest parts of testing have nothing to do with testing at all. If you have problems that you’d like to solve or solutions that you’d like to offer, come along.

Syndicate content