DevOps East 2017 - Agile & Lean Development, Principles, & Practices
Sunday, November 5
Leading SAFe–SAFe Agilist Certification Training
Certified ScrumMaster Training
Fundamentals of Agile Certification—ICAgile
Agile Test Automation—ICAgile
Monday, November 6
Lean Software Development: Principles and Practices
PreviewLean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development—concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by developing in small batches; emphasizing high quality which decreases delays due to defect repair; making policies, process and progress transparent; optimizing the whole rather than individual steps; and becoming more efficient by decreasing waste. Ken describes lean’s emphasis on cycle time rather...
Leading Successful Organizational Change Efforts
Has this happened to you? You try to implement a change in your organization, and it doesn’t get the support 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 organizational change management, a checklist to help you determine the type of change process needed in your organization, techniques for...
Get Started with Acceptance Test-Driven Development
PreviewDefining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, developers, and quality assurance experts alike. The origin of many items living in our defect tracking systems can be traced to our difficulty performing these initial activities. Ken Pugh introduces acceptance test-driven development (ATDD), explains why it works, and outlines the different roles team members play in the process. ATDD improves communication among customers, developers, and testers. By decreasing re-work, ATDD has proven to dramatically...
Tuesday, November 7
Stop Talking about DevOps: Start Applying Continuous Delivery Practices
DevOps. You think you need it because the market is telling you so, but the market is confused (and self-perpetuating). Agile, continuous delivery, and DevOps all promise the same dream—improved time to market through incremental delivery of quality software. So where should you focus? Max Griffiths begins by distinguishing DevOps from the other approaches and, rather than wrangling new words for old problems, helps refocus how to measure success. How long does it take you to commit and deliver code? Max shows how you can measure this through Value Stream Mapping, a crucial tool used to...
What DevOps Means for Testers
DevOps is more than a buzzword or a passing fad. It's a radically new approach to rapidly deliver high-quality software applications. However, many organizations don’t fully grasp the magnitude of this change or what it means for everyone involved in the software development lifecycle. Jeffery Payne says that DevOps—when done right—drives higher quality and efficiency into software development, software testing, and application management activities. It empowers teams to remove impediments to quality and productivity throughout the entire software lifecycle. However, when DevOps is done...
Plan, Architect, and Implement Test Automation within the Lifecycle
In test automation, we often must use several tools that have been developed or acquired over time—with little consideration of an overall plan or architecture and without considering the need for integration. As a result, productivity suffers and frustrations increase. Join Mike Sowers as he shares experiences from multiple organizations in creating an integrated test automation plan and developing a test automation architecture. Mike discusses both the good (engaging the technical architecture team) and the bad (too much isolation between test automators and test designers) on his test...
Wednesday, November 8
Measure Anything: The Quality, Productivity, Predictability, and Engagement Model
Measuring software development is difficult. Measuring the return on investment (ROI) of complex initiatives (such as adopting agile) is even more difficult. One department at IBM struggled to reduce a list of 150 metrics down to a top twenty to use in consulting engagements. Through the years, nearly every one of Anthony Crain’s clients has asked him for help in proving that their teams were “getting better” at development. Nearly all of their measures were “adoption” measures showing how teams were doing agile. However, none of the metrics was focused on whether the development was...
Why Won’t They Pair?
Do your developers and testers pair—and do it in the best ways? If you can answer yes, then you are among the fortunate ones who have a trusting environment where people have confidence in their work. Unfortunately, a large number of development shops don’t practice pairing in any form. Pair programing was documented in Kent Beck’s book eXtreme Programming Explained, published in 1999. So why is it that eighteen years later many developers and testers do not practice this simple yet effective programming technique? Linda Cook addresses many reasons that people don’t pair. Drawing on...
Balance Discovery and Delivery with Dual-Track Agile
PreviewDo your product teams frequently struggle to have groomed and well-defined stories ready for the developers? Do you find yourselves frequently in “feed the beast” mode to keep your development teams busy? Do your product teams have problems gaining shared understanding across product management, interaction designers, developers, and QA? If so, your product teams manifest the symptoms of single-track agile—and this session is for you. Sean McKeever explains the key steps in establishing dual-track agile methodologies at your organization, presents his experiences, and provides...
The Top Five Agile Concepts That Most Companies Completely Miss
PreviewOrganizations claim to be going agile. Many agile leaders promise twice the results in half the time. Unfortunately, most organizations and leaders fail before they even start. In five basic concepts Lee Henson shares the reasons for their failures. First, focusing on the outcome instead of the output is critical for agile project success. Second, organizations that succeed are those that take time to eliminate technical debt and focus on test automation. Third, as organizations strive to be precise in their estimates, they are learning that time-based estimation was never intended...
They Said, We Said: Bridge the Communication Gap with Behavior-Driven Development
PreviewHave you heard that only 36 percent of business features built into software are actually used by end users? And why do we get functionality that fails to work as expected? One of the age-old problems between IT and our clients is that we don’t speak the same language. Sheetal Patel shares her experience of how behavior-driven development (BDD) introduces the bridge of common language that both IT and non-technical, business clients can speak to build the right product. Sheetal explains how collaborating on agile teams with BDD gains a common understanding among developers, testers...
A Lean Tour of Lean Software Development
Lean software development has been described as “better, faster, cheaper” and focused on “eliminating waste,” but those are misnomers. Going after speed improvement and waste elimination can actually reduce the benefits you might otherwise get from lean. Ken Pugh describes what lean software development really is and why you should be incorporating it into your development efforts—whether you use Scrum, kanban, or SAFe. Ken explains the mindset, principles, and practices of lean. Its foundations are systems thinking, a relentless focus on time, and an understanding that complex systems...
Thursday, November 9
We Are Doing Agile But, But, But …
“We are doing agile, but the only tests we do in a sprint are unit tests” or “We are doing agile, but we have a hardening phase at the end, which is really more of a system integration test” or “We are doing agile, but testing is done by a separate test team.” Sound familiar? Gitte Ottosen says that these agile transition failures prevent teams from getting the maximum value out of the agile context. Failing to create a mindset and environment where quality is built-in continuously and testing is an integrated part of the development lifecycle are risks not only to quality in classical...
Awesome Agile and How We Did It: Halogen’s Journey
Many organizations struggle to achieve predictable, high quality software delivery. However, agile software processes are not prescriptive, and we recognize that processes are continuously evolving to improve delivery, consistency, and quality. Karen Holliday describes the challenges that Halogen Software experienced in the past five years as they moved from waterfall delivery to the agile/scrum development model. Karen shares the strategies implemented at Halogen that have led to a string of five on-time quality releases—including two early releases. Learn how to plan in an agile (ALM)...
Agile Testing Is All about Risk—Not Bugs and Quality
PreviewMany organizations make huge investments in software testing, and unfortunately they often don’t understand or extract full value from these activities. This can lead to testing being viewed as a mere formality or necessary evil within an organization. Fortunately, we can deliver more value with relatively minor adjustments to our approaches. The transition to agile practices provides a natural opportunity for test specialists and others to put these adjustments into practice. Plan-driven approaches can also be adjusted to increase the value delivered from testing activities....
Task-Oriented Unit Testing for Agile and Traditional Projects
Developers are charged with developing software at lightning speed, often using new and unreliable technologies. Rob Sabourin shares a task-oriented method for organizing unit testing to help programmers and other team members get to consistently done working code, testing beyond the code. Rob approaches unit testing from the viewpoint of completing all the technical work required to fulfill a requirement, exercising the entire vertical technology stack and going beyond raw code. Programmers learn when and how unit test design can be implemented blending white box and black box techniques...
Sustaining Agility—After the Consultants Leave
PreviewOrganizations transitioning to agile often hire external consultants to help them become more agile. However, what tends to happen six months after the consultants leave is that the organization is often left with more—and different—problems than they had before. Susan Lin says this happens because the organization was not set-up to deal with the new challenges. Susan shares the Help Agility Stay framework and shows how you can help your organization grow and sustain agility by applying the three main principles of the framework—create a shared vision of agility, co-create a...
Put Agile to the Test: A Case Study for Test Agility on a Large IT Project
PreviewAgile practices, although applicable to a variety of situations, are most commonly applied to IT projects, generally for software development. Can you apply agile methods to just part of a software implementation project? Todd Jones presents this case study where agile techniques were applied to the testing phase of a multiyear, multimillion-dollar IT program that included replacing a legacy system, new software development, creation of a new enterprise data model and document management solution, and complex financial balancing. After briefly describing the challenges faced by the...
Use Mind Maps to Increase Team Velocity and Communication
Ever sit in a strategy review session and get little or no participation from others? Or feel like you left a planning session with a different understanding of what was agreed to? If you feel there must be a more effective way to communicate important information around your strategy and plans and you want a better way to document it so your stakeholders will both understand and engage in providing useful feedback, Jennifer Bonine has a solution for you. Join Jennifer as she describes mind mapping tools and techniques and explore how mind maps can help increase team velocity and...
Scale: The Most Hyped Term in Agile Development Today
Scrum is everywhere. More than 90 percent of agile teams use it. But for many organizations wanting to scale agile, one team using Scrum is not enough. Dave West says the Nexus Framework, created by Ken Schwaber, the co-creator of Scrum, provides an exoskeleton for Scrum. Nexus allows multiple teams to work together to produce an integrated increment regularly. It addresses the key challenges of scaling agile development by adding new yet minimal events, artifacts, and roles to the Scrum framework. Dave discusses Nexus, addresses its boundaries, and explains what else is needed for agile...
Help! The Scrum Master *is* the Impediment
The change in mindset necessary to become a servant leader is incredibly hard for a scrum master who comes from a command and control background. As a newly minted Professional Scrum Master (PSM I), Ryan returned to his team excited and ready to get underway with a scrum adoption, but he had not fully grasped the concept of servant leadership. Instead of being a change agent, he was an impediment. Ryan’s cautionary tale is a common one. Attendees will learn about the difficulties of becoming a scrum master, how scrum team members need to embrace the scrum values to promote healthy team...
Design by Discovery to Stop Building Bad Software
Two common situations lead to bad software—the project team isn’t aligned on the problem or the customer isn’t involved in the design process. Either way, you end up with a product that the business didn’t ask for, the tech team struggles to deliver, and customers don’t want. So, how do you increase confidence in the direction of your product and work together to build innovative solutions that bring the business, technology, and customers together? Garren DiPasquale and Matt Wallens introduce, a process to understand business goals and customer needs. It isn’t about designing screens or...
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
PreviewA hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton...
Resolve the Contradiction of Specialists within Agile Teams
PreviewAs teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these...
Individuals, Interactions, and Improvisation
As agile practitioners, we constantly strive to better ourselves, our team, and our delivery. A great way to achieve this is simply being open to learning new ideas from other disciplines—including improvisation. Jessie Shternshus shares her story of realizing the uncanny similarities between agile team principles and the pillars of improvisation. Effective improvisers give their teammates unconditional support, practice active listening and accept (and build on) each other’s ideas, see and use mistakes as opportunities, learn to embrace the unknown, and always consider who their audience...
Friday, November 10
Building an Agile Organization at Light Speed
Everyone loves the idea of explosive growth. Unfortunately, explosive growth often lives up to its name. Everywhere you look, things are blowing up. Josh Anderson shows you how to corral the chaos and provide your company with the growth it desperately needs.
The two key challenges of explosive growth are diametrically opposed: protect and support your existing teams and processes, while simultaneously growing an organization around them. To make that happen, you must walk the tightrope of process evolution as you grow your team. Josh shares real-world strategies you can use to...
Transform a Product Team to Agile—and Live to Tell About It
The idea of transformation can be both exciting and frightening. How do we shake off old ways of thinking? What will emerge when the transformation is complete? How will I know the transformation is finished? These are questions and challenges that many product teams face as they make the transformation to agile.
Kevin Stilwell shares his experience and techniques for shaking off old paradigms and practices to break the organizational “muscle memory” that exists in many companies. What emerges will be a high performing product team—and the reward will be well worth the effort.
The Yin & Yang of Agile Success at Dude Solutions
In this mini-panel discussion Kevin Stilwell and Josh Anderson share their from-the-ground-up experiences building an agile organization and field participants’ questions. From their unique perspective Kevin and Josh share tactics and practices they used to build a high-performance agile organization. They are essentially sharing the “secret sauce” that made Dude Solutions a great example of “agile done well.”
Leverage Big Wall Planning for Truly Aligned Organizational Execution
Love it or hate it, the Scaled Agile Framework (SAFe) was found to be the most used framework for enterprise-level agility in Version One’s annual survey. That said, many aspects of SAFe—including effective portfolio management—are difficult for organizations to implement.
Laura Burke Olson shares Big Wall Planning, a technique that Ipreo uses to “seed” their release trains with high-priority, high-value, and balanced portfolio-level epics. Big Wall Planning engages all aspects of company leadership in deciding the product roadmaps. This is a huge challenge in organizations that...
Aligning Toward Business Agility–360° of Freedom
What happens when the product vision is unclear? Simply put, your teams struggle to build valuable features and your customers are not happy. This lack of alignment eats away not only at the value you’re trying to deliver but also at your customers’ good will—and it can demoralize your teams.
Ryan Ripley examines the why behind your current practices and shows you how the agile values, principles, and ceremonies of an agile organization are designed to create and maintain alignment all the way from customers to individual team members. Drawing from real-world examples, Ryan explains...