Conference Presentations

Sustaining an Agile Culture

In Scrum, the product owner manages the product backlog-seems simple enough. But what principles are required to make seemingly straightforward agile practices really work? Mitch Lacey suggests courage, trust, commitment, and simplicity are those principles. Courage: Do I have the courage to say no to this stakeholder for the overall benefit of the product? Trust: Can I trust the team to sustain their velocity? Commitment: Are all team members working everyday to improve? Simplicity: Are we doing only the things that bring value to the product? These are real-life questions that agile team members face daily. It's not enough to just say you're agile because you work in iterations. Truly being agile weaves these principles into the fabric of our projects. Join Mitch to learn how he has applied these principles in his projects and the failures that have occurred when the principles were misaligned or absent all together.

Janet Gregory, DragonFire Inc.
Agile: Resetting and Restarting

The Agile Manifesto-ten years in the making-was published in 2001. Now, with more than eight years of practice, the manifesto has greatly influenced the process of software development. It has influenced the IEEE's software contracting models, the Project Management Institute's view of software project management, the Software Engineering Institute's CMMI™ assessment model, and helped change the development process for thousands of organizations around the world. During these years, agile practices have moved forward and continued to mature, adopting ideas from lean manufacturing and the theory of constraints to add more rigor to our work. Still, many agile projects today tend to fail because they are overly tactical and do not take the long-term view.

Alistair Cockburn, Humans and Technology
Beyond Scope, Schedule, and Cost: Rethinking Performance Measures for Agile Development

A recent Business Week article proclaimed, "There is no more Normal." With businesses in the throes of pervasive change, the traditional emphasis on "following the plan with minimal changes" must be supplanted by "adapting the plan to inevitable changes." If agile development practices are about focusing on and delivering customer value, then how can adherence to traditional scope, schedule, and cost be a good way to measure performance? It can't. Jim Highsmith explains the need to move beyond the classic Iron Triangle measures to instead focus agile software development success on value, quality, and constraints. Even today, many agile teams are asked to be flexible and adaptive and then are told to conform to planned scope, schedule, and cost goals. They are asked to adapt-inside a very small box. If we are to truly bring agile values to our organizations, then we must change our performance measures.

Jim Highsmith, Information Architects, Inc.
Understanding and Managing Change

Has this happened to you? You try to implement a new software quality improvement program and it ends up failing. And, to make matters worse, you can't figure out why. It may be that your great idea didn't mesh well with your organization’s current culture. Jennifer Bonine shares a toolkit to help you determine which ideas will-and will not-work within your organization. The toolkit includes five rules for change management, a checklist to help you analyze the type of change process needed in your organization, a set of questions you can ask to better understand your company's goals, techniques for overcoming resistance to change, and the formal roles necessary to enable successful change. This toolkit-together with an awareness of your organization's core culture-allows you to identify the changes you can successfully implement and those that should be left for the future.

Jennifer Bonine, Oracle Corporation
STARWEST 2009: Test Process Improvement on a Shoestring

In these times of economic crisis, cost reduction is usually the number one motive for test process improvement. Although improvement models such as TMMi® and TPI® are very popular, they require formal assessments, process change working groups, extensive implementation programs, and new organizational structures. Instead, you can quickly implement measures that improve your testing process incrementally within your day-to-day activities. Martin Pol presents a low-budget way to select and implement a set of measures that can rapidly improve testing’s contribution to your project’s success-simple risk analysis, proactive test design, coverage targeting, and novel ways to reuse tools, environments, expertise, and existing testware. Learn how low-budget test process improvement can become a natural behavior for your testing staff.

Martin Pol, POLTEQ IT Services BV
Toward 21st Century Automation for Agile Testing

As more companies move to agile software delivery approaches, new challenges and dynamics are impacting their testing practices. Organizations face many issues when implementing automation, including selecting tools that are usable and flexible, encouraging non-technical and non-testing staff to contribute tests, enabling open-source integration, and promoting test-driven development. Dietmar Strasser shares his experiences tackling these challenges as many organizations shift from traditional test automation to agile. Learn about the increased importance of testing in the agile development environment; the role that process and tools play in supporting the agile team; the differences between traditional and agile test automation; how to develop fast, automated test scripts; the use of agile and traditional testing methods side-by-side; and how to deal with test automation in a distributed development environment.

Dietmar Strasser, Micro Focus
Seven Factors for Agile Testing Success

What do testers need to do differently to be successful on an agile project? How can agile development teams employ testers’ skills and experience for maximum value to the project? Janet Gregory describes the seven key factors she has discovered for testers to succeed on agile teams. She explains the whole-team approach of agile development that enables testers to do their job more effectively. Then, Janet explores the “agile testing mindset” that contributes to a tester’s success. She describes the different kind of information that testers on an agile team need to obtain, create, and provide for the team and product owner. Learn the role that test automation plays in the fast-paced development within agile projects, including regression and acceptance tests. By adhering to core agile practices while keeping the bigger picture in mind, testers add significant value to and help ensure the success of agile projects.

Janet Gregory, DragonFire Inc.
A Solid Foundation for Quality Improvement

Many managers look to formal techniques-requirements reviews, code inspection, and testing-to improve the quality of their software. While these techniques are valuable, they only evaluate the state of quality rather than improve it. The key is to create quality software in the first place. This can only be achieved by a change in management style. Jason Bryant proposes a set of simple and effective principles you can employ to produce high quality software. First, you must foster a culture where people are given the freedom, time, and resources to do the job correctly the first time. By embracing user centered and incremental development practices, you will go a long way toward ensuring accurate and timely software delivery. Focus on training your staff to become masters of their craft and invest equally in architecture, new features, and maintenance.

Jason Bryant, Schlumberger Information Solutions
Agile, Lean, and the Project Management Office

PMOs usually think they are out of business when agile rolls into town. But the reality is that the PMO can play a pivotal role in successful agile adoption in large organizations. Jean Tabaka shares her knowledge about how to engage your PMO for agile adoption by using three primary Lean Principles: "Eliminate Waste," "See the Whole," and "Amplify Learning." Jean gives examples of how PMO members can act as the "systems thinkers" for their organizations, pulling successes from the engineering group and instilling them into the entire enterprise. Learn the role of the PMO within agile-how the PMO pulls standards versus pushing them; how the PMO provides product backlog prioritization guidance regarding architecture and governance; how the PMO serves its agile community by facilitating release planning across teams; and how the PMO creates and maintains product councils.

Jean Tabaka, Rally Software Development
Becoming a Lean-Agile Enterprise

Many companies have adopted agile by using Scrum on one or more of their projects. Unfortunately, they may be missing the point that agility should be aimed at the enterprise, not merely at the team. Agile enterprises can respond quickly to changing market conditions, competitive pressures, and changing technical environments, thus bringing their innovations to market faster. However, creating an agile enterprise is much more than simply getting teams to adopt Scrum. Alan Shalloway discusses how to use lean thinking to determine where to start using agile methods as well as how to adopt agile throughout the entire enterprise.

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.