Agile Dev West 2016 - Process & Metrics
Monday, June 6
Configuration Management: Robust Practices for Fast Delivery
Robust configuration management (CM) practices are critical for creating continuous application build, package and deployment to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling changes, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change...
Leading Change—Even If You’re Not in Charge
Has this happened to you? You try to implement a change in your organization and it doesn’t get the support that you thought it would. And, to make matters worse, you can't figure out why. Or, you have a great idea but can’t get the resources required for successful implementation. Jennifer Bonine shares a toolkit of techniques to help you determine which ideas will—and will not—work within your organization. This toolkit includes five rules for change management, a checklist to help you determine the type of change process needed in your organization, techniques for communicating your...
Planning to Learn and Learning from Delivery: Scrum, Kanban and Beyond
If you are new to agile methods—or trying to improve your estimation and planning skills—this session is for you. David Hussman brings years of experience coaching teams on how to employ XP, lean, Scrum, and kanban. He advises teams to obtain the estimating skills they need from these approaches rather than following a prescribed process. From start to finish, David focuses on learning from estimates as you learn to estimate. He covers skills and techniques from story point estimating delivered within iterations to planning without estimates by delivering a continuous...
Tuesday, June 7
Continuous Delivery: Rapid and Reliable Releases with DevOps
DevOps is an emerging set of principles, methods, and practices that enables the rapid deployment of software systems. DevOps focuses on lowering barriers between development, testing, security, and operations in support of rapid iterative development and deployment. Many organizations struggle when implementing DevOps because of its inherent technical, process, and cultural challenges. Bob Aiello shares DevOps best practices, starting with its role early in the application lifecycle and bridging the gap with testing, security, and operations. Bob explains how to implement DevOps using...
Measurement and Metrics for Test Managers
To be most effective, test managers must develop and use metrics to help direct the testing effort and make informed recommendations about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the software, test managers must measure the results of both the development and testing processes. Collecting, analyzing, and using metrics are complicated because many developers and testers are concerned that the metrics will be used against them. Join Mike Sowers as he addresses common metrics—measures of product quality,...
Agile Project Failures: Root Causes and Corrective Actions
Agile initiatives always begin with high expectations—accelerate delivery, meet customer needs, and improve software quality. The truth is that many agile projects do not deliver on some or all of these expectations. If you want help to ensure the success of your agile project or to get an agile project back on track, this tutorial is for you. Jeffery Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects. Poor project management, ineffective requirements development, failed communications, software development...
Wednesday, June 8
Three Things You MUST Know to Transform into an Agile Enterprise
The farther we go down the path of scaled agile transformation, the more we learn that adding process and complexity can only take us so far. At some point, size and complexity are going limit our ability to be truly agile, and we must move toward greater organizational simplicity. The challenge is that large organizations are often complex and usually anything but simple. Most agile transformations start by either ignoring the complexity inherent in the system or by wrapping complexity in planning constructs that may help in the short run but ultimately doom your business agility. Mike...
Slay the Dragons of Agile Measurement
Some consider measurement in agile development destructive—or at the very least useless. Larry Maccherone disagrees and offers eight tools to slay the dragons of agile measurement. The #1 Dragon slayer—Use measurement for feedback rather than as a lever. What's the difference? Feedback is used to improve your own behavior; a lever is employed to change someone else's behavior. The distinction is subtle but critical. If you think what gets measured gets done, you are already venturing into “thar be dragons” territory. But it's not too late. Larry shows how to create a culture where...
End-to-End Quality Approach: 14 Levels of Testing
In 2015, the Standard & Poor’s Ratings IT team set out an ambitious objective—to tighten the process and controls around the quality of code deployed to production. Based on internal cost of quality assessments, and supporting agile and waterfall internal engineering processes, distinct testing levels were identified to help push quality left and root out the underlying causes of defects as early as possible. The ‘14 Levels of Testing’ were defined to collaboratively span organizational functions, establish quality expectations, and help track towards the goal of eliminating defects....
Agile Metrics: Measuring Outcomes and Results
When organizations move to agile approaches, two very common metric anti-patterns surface: (1) The organization doesn’t change its metrics at all and simply continues to measure as they always have; or (2) The organization throws out every metric and just focuses on velocity and trying to increase it. Both of these anti-patterns lead to metrics dysfunction and disastrous results. Bob Galen explains that agile organizations should be developing their measurement strategies early. He explores unhealthy metrics (for example, velocity) and the drives behind measuring them. Then he describes...
Why Agile Works—and How to Screw It Up!
Agile practices can be the easy part of agile. It’s getting people into the agile mindset that can be a real challenge. Do you have a team member who doesn’t quite support agile or someone who’s playing along but not really committed? One step toward obtaining real commitment is a better understanding of why agile works, why it is different, and when it is the right approach. In this fast moving session, Perry Reinert provides a fun look at some of the theory that gets to the core of why agile works. Yes, we really can use the words fun and theory in the same sentence. Combining parts of...
Project Estimation: Myths, Taboos, and Inconvenient Truths
Too many of us continue to suffer through schedule-driven crunch mode and cost overruns. We all know the usual suspects, including bad estimates and changing requirements. But what if we set aside myths and embraced reality? Estimates are uncertain, but that doesn’t make them bad—only inconvenient. We can’t manage away the uncertainty, but we can choose where it lands. Robert Merrill believes that our longing for stable requirements tells us where the uncertainty wants to be—in the scope. What if we stopped fighting it? What if we broke the taboo and said we’re done with crunch mode, with...
Thursday, June 9
How to Do Kick-Ass Software Development
Software development is hard― keeping developers, testers, designers, product managers and other stakeholders in sync and working on the right things at the right time. Building the systems that customers care about and delivering high-quality code fast are challenges every development team faces. Just being agile isn’t enough; we need to actively think about how we can improve software development processes and techniques. Sven details Atlassian’s coding practices and team dynamics, which include: collaborating fast to develop ideas, helping QA with testing, avoiding meetings to get...
Zorro Circles: Retrospectives for Excellence
Have you wondered how to progressively harness your agile team’s energy, focus on important goals, and improve outcomes? Woody Zuill said, “If you could adopt only one agile practice, then let it be retrospectives. Everything else will follow.” Retrospectives help individuals and teams adjust to today’s constant change and establish a sustainable pace to deliver complex products. Zorro Circles is a framework for designing retrospectives that employs proven techniques to gather and analyze information required to collectively solve problems. Aakash Srinivasan and Vivek Angiras introduce the...
Continuous Discovery: The Path to Learning and Growing
Software development is a process of continuous discovery. When writing software, we create ideas, we try them in code, we learn what works and what doesn’t—and that steers us to a better solution. And sometimes we do this all day long! Woody Zuill says that this same process of continuous discovery works for making improvements for our teams, and in our workplaces and organizations. With continuous discovery we do numerous micro experiments that guide us along the path to a better future. If we follow the values and principles expressed in the Agile Manifesto, which provides us a powerful...
A Case Study in Metrics-Driven DevOps
It seems impossible for a DevOps team to even attempt planning its work. The team deals with customers’ never-ending requests and constantly-changing priorities. And don’t forget those unfriendly infrastructure errors that always seem to show up at the worst possible time. Best to live day-by-day and try to keep our heads above water, right? Maybe not. Through a case study of a department that helps make great Electronic Arts games, Ben Vining illustrates how a metrics-driven DevOps team can become reliable, responsive, and predictable—with happy staff and delighted customers. Ben details...
Don’t Make These Scrum Mistakes
Scrum is a project management framework and does not specify a set of how-tos or checklists that some other development processes define. Since Scrum can be implemented in various ways, it is easy—and often common—to misinterpret Scrum’s guidelines and make mistakes while implementing it. A new team, in their eagerness to “go agile” and adopt Scrum, often succumb to common pitfalls. Being aware of these mistakes is the first step toward avoiding or resolving them. Sumedha Ganjoo discusses and shares examples of some common mistakes that she notices new teams making. Examples include shared...
Facilitation Techniques for Agile Meetings and Ceremonies
Facilitation is the art of leading people through processes toward agreed-upon outcomes in a manner that encourages participation, ownership, and creativity from all involved. So how do you take this definition and turn it into facilitating powerful meetings? Most agile practitioners can read about facilitation and the “right” way to do it. However, it can be challenging to take that book knowledge and feel comfortable facilitating agile meetings and ceremonies. Whether you are looking to coach a single team/product or scale agile to the program/enterprise, Darrin London says that...
What Everyone on the Team Needs to Know about Test Automation
Test automation should be an activity that involves the entire project team—not just the testing group. Test automation is a technical testing task, and the test team benefits from the assistance of others in the organization. Jim Trentadue outlines the various testing activities with the corresponding contributions and benefits of each team member. Project managers can coordinate the effort and schedule. Business analysts can manage technical test requirements. User acceptance testers can provide proper steps and screenshots for IT personnel. Developers can write code with testability in...
Scaling Scrum with Scrum™ (SSwS): A Universal Framework
Scrum is a simple framework allowing a single team, working from a single backlog, to maximize the value it delivers to its stakeholders. Unfortunately, your organization probably has more than one team and more than one backlog—but you still need to maximize the value to your stakeholders. You need Scrum, but how do you scale it for your organization? Dan Rawsthorne proposes Scale Scrum with Scrum™; tie your organization’s development scrum teams together with Leadership Teams and Coordination Teams. These are scrum teams that assure that each development team has a backlog, that the...