People & Teams

Conference Presentations

Mistakes Agile Teams Make

The road to hell is paved with good intentions-with a special section reserved for those who have tried to "go agile". Agile adoption can fail because a number of common, large-scale, organizational issues. A lack of executive-level support can squash promising improvements among the day-to-day producers. Sometimes the organization is in such disarray that delivering perfect features perfectly wouldn't keep customers satisfied. While these are real and important, J. B. Rainsberger suggests you'll find it more productive to focus on issues over which you have real influence. J. B. describes a few relatively simple mistakes, the warning signs to look for, and how to solve the problems. Hear useful stories from an experienced agile coach that include, "If I'd only known then what I know now ..." You'll laugh, you'll cry, and with luck, you'll catch a problem or two before it blows up on you.

JB Rainsberger, Diaspar Software Services
"With Great Power Comes Great Responsibility" - Empowering the Agile Team

Managers at many levels are often afraid to let go of the reins for fear of losing control of the project (and their position of power). V. Lee Henson explains the benefits of letting go and outlines the expectations of a responsible, empowered agile team. Through presentation of multiple real-world scenarios and years of project management experience, Lee will show that often our own human nature is the greatest impediment to being a better manager. Lee focuses on the attributes of an effective agile manager/leader, the expectations and attributes of an empowered agile team, the pitfalls and warning signs of a "damaged" team, and the rewards an organization can expect from adhering to basic agile principles. You will leave with the tools to help any agile team become more empowered.

V. Lee Henson, VersionOne, Inc.
Beware of Your Brain

Cognitive scientists tell us that we are more productive and happier when our behavior matches our brain's hardwiring-when what we do and why we do it matches the way we have evolved to survive over tens of thousands of years. One problematic behavior humans have is that we are hardwired to instantly decide who we trust. And we generally aren't aware of these decisions-it just happens. Linda Rising explains that this hardwired "trust evaluation" can get in the way of working well with others. Pairing, the daily stand up, and close communication with the customer and others outside the team go a long way to overcome our instant evaluation of others. As Linda helps you gain a better understanding of this mechanism in your behavior and what agile processes can do to help, you are more likely to build better interpersonal relationships.

Linda Rising, Independent Consultant
Collaborative Leadership: A Secret to Agile Success

When members of a development project are asked to become a self-directed agile team, some claim that leadership and leaders are obsolete. Or, is a different type of leadership exactly what agile teams need to truly flourish? Pollyanna Pixton describes a new, collaborative leadership style that does not attempt to control or micro-manage. It's one that asks the right questions at the right time to generate new ideas and develop creative products that customers need and want. Pollyanna explains the four areas of collaborative leadership-creating an open environment where the best people can work, learning from stakeholders throughout the enterprise, prioritizing innovative solutions based on business value, and standing back to allow the team to succeed.

Pollyanna Pixton, Accelinnova
Are We There Yet? Defining "Done"

"Are you done yet?" The answer to this question may sink your career, your team, and your project. If you respond with a "yes," you may be forced to take on additional work you can't handle. If you say "no," you may be branded as someone who can't get things done. Mitch Lacey notes that this innocent question is asked countless times on almost every software project. Establishing an upfront, common understanding of "done" can save teams and businesses countless hours of rework, process-thrash, unclear communication, and hidden work. Mitch describes what a "done list" is, how it adds value, and the value it communicates to stakeholders. Mitch takes you through an exercise on how to establish a common understanding of done and provides an exercise that you can use with your project teams.

Mitch Lacey, Mitch Lacey & Associates, Inc.
Overcoming the Pitfalls of Transitioning to Agile

If you've been trying to change your organization so that your projects are more agile, you may have encountered several problems-one is that it's difficult to have product management, senior management, and functional managers work together to lead in a way that makes sense for your agile project. You're also probably working with other parts of a large program that isn't agile; you have a geographically distributed team; your management wants to know at the beginning when the project will end; or you might have a project team that does not share a common vision of what "done" means. Johanna Rothman explores common organization, management, team, and individual team member issues. She offers suggestions for making the changes more acceptable and helping people work with you in a way that enables your projects to succeed.

Johanna Rothman, Rothman Consulting Group, Inc.
Top Ten Non-Technical Skills of the Better Testing

In the era of SOA and Web 2.0, as it becomes more and more difficult to accomplish comprehensive testing, Krishna Iyer and Mukesh Mulchandani describe ten non-technical skills that will make you a better tester. The first five are qualities we often look for in testers yet seldom practice scientifically and diligently--collaboration, creativity, experimentation, passion, and alertness. The second five are abilities that are seldom mentioned, yet equally important for testers--connect the dots, challenge the orthodox, picture and predict, prioritize, and leave work at work. Drawing from their experiences of building a testing team for their organization and consulting with global firms in building "testing capability," Krishna and Mukesh show how you and your test team can improve each of these ten non-technical skills. Practice these skills during the session and take back techniques you can use to hone your skills at work.

Krishna Iyer, ZenTEST Labs
STARWEST 2008: What Price Truth? When a Tester is Asked to Lie

As testers and test managers, our job is to tell the truth about the current state of the software on our projects. Unfortunately, in the high-stakes business of software development, often there is pressure--subtle or overt-to distort our messages. When projects are late or product reliability is poor, managers' and developers' reputations-and perhaps even their jobs-may be on the line. Fiona Charles discusses the importance to testers of refusing to compromise the truth, recognizing a potential cover-up before it occurs, knowing the legal position around securing project information, and developing a strategy to maintain integrity and still get out alive.

Fiona Charles, Quality Intelligence Inc.
STARWEST 2008: Five Things Every Tester Must Do

Are you a frustrated tester or test manager? Are you questioning whether or not a career in testing is for you? Do you wonder why others in your organization seem unenthusiastic about quality? If the answer is yes to any of these questions, this session is for you. Julie Gardiner explores five directives to help testers make a positive impact within their organization and increase professionalism in testing. Remember quality-it's not just time, it's time and quality; it's date and quality; it's functionality and quality. Learn to enjoy testing and have fun-the closest job to yours is blowing up things for the movies. Relish the testing challenge-it's you against the software and sometimes, it seems, the world. Choose your battles-take a stand on issues that are vital and let the small things go. And most importantly, remember that the only real power we have springs from our integrity-don't sell that at any price.

Julie Gardiner, Grove Consultants
Has the Time for the Adversarial Organization Passed?

The concept of an independent test organization is considered a "best practice" by many experts in the industry. Is this degree of autonomy actually a good thing in the real world today? In such a structure, some testers can only play "Battleship" with the delivered software, shouting gleefully when they find a defect. On their first tours of Toyota's factories, American automakers were astonished to find no "rework area." Toyota engineers didn't subscribe to the approach of inserting defects on the production line only to remove them later in the quality control and rework area. Yet this is exactly what the independent test group excels at! Is it time to discard this organizational model and focus on working together with developers to prevent defects in the first place? Gerard Meszaros examines the sacred concept of independent test teams based on experiences from the agile software movement and Lean production systems.

Gerard Meszaros, Independent Consultant

Pages

AgileConnection is a TechWell community.

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