As the Managing Director of Excelon Development, Matt Heusser, consults, trains, and does software delivery while helping others do it. Probably best known for his writing, Matt is the lead editor of "How to Reduce The Cost of Software Testing" (Taylor and Francis, 2011), editor for Stickyminds.com, and recipient of the 2015 Most Popular Online Contributor to Agile at the Agile Awards. A 2014 recipient of the Most Influential Agile Test Professional Person Award (MAITPP) in Potsdam, Germany, Matt also served as the lead organizer of theSoftware Testing World Cup. He is a former of the board of directors of the Association for Software Testing and creator ofLean Software Testing family of methods.
A technologist with 15 years of experience executing strategy and delivering high quality products. Career has included product management; program/project execution; people leadership; agile coaching; and enterprise agile transformations. Also a proud participant and contributor to the technology community; including organizing meet-ups and conferences; speaking at local and regional conferences; and guest blogging.
Kevin Seidl is a Product Owner at John Deere in Des Moines, Iowa. He has worked at Deere for over 7 years.
Kevin focuses on a customer first approach to problem solving, preferring to get his boots dirty in the field understanding needs over white boarding in a conference room. Farming and big data are rarely in the same sentence but Kevin brings those together in the products he delivers.
When he's not working you may find him on the side of the road cursing the British engineers responsible for his car’s(MGB) most recent demise. He has also perfected the "agile oil change": add oil in faster than it can leak out, but never all at once.
Llewellyn Falco is an independent agile coach. He is a PluralSight author, international speaker and the creator of the open source testing tool ApprovalTests( www.approvaltests.com ). He spends most of his time programming in Java and C# specializing in improving legacy code. He also volunteers creating courseware and teaching kids to program ( www.teachingkidsprogramming.org ).
Jason has over 20 years experience working in the technology industry, and specializes in helping companies continuously deliver value quickly by using Lean|Agile techniques. Currently an Enterprise Agile Coach and Trainer at SolutionsIQ, Jason splits his time between instructing classes, coaching Scrum and Kanban teams, and helping organizations transform. Prior to SolutionsIQ, Jason held engineering and Agile transformational leadership roles at Salesforce, Good Technology, and Nokia.
Melissa Perri is a product consultant and speaker based in New York City. As the CEO of ProdUX Labs, Melissa does strategy and training for product management teams globally. As a practitioner and a coach, Melissa enjoys finding the best processes for her clients while tackling their toughest product problems with the team. She is currently writing a book called “The Build Trap” and launching a product management school online.
Julie has over 30 years in Enterprise Software and is an experienced leader of high tech development teams, a former Director of Engineering, and a joint inventor on 5 patents. She is knowledgeable in all aspects of development and delivery, agile methodologies, coaching, and collaborative leadership. She is committed to diversity with a focus on supporting Women in Technology and encouraging girls to embrace STEM. Currently at Veritas in role of Agile Transformation Coach, Scrum Master, and practitioner in the Agile Practice Group.
Julie Chickering, Agile Advisor & Strategic Solutions Consultant, Agile Coach, Certified Scrum Trainer (CST), Certified Scaled Agile Program Consultant (SAFe® SPC), PMP, PMI-ACP, Accredited Kanban Trainer (AKT)
Julie believes that Agile practices are packed with potential — to enable business agility, and breakthrough results. A passion to empower customers to realize that potential is what brought her to Rally in 2008. She’s amassed a strong track record of helping organizations of all sizes in various industries successfully execute Agile transformations. Julie brings real-world experience working with people at all levels — executive, program, and team — to adopt and roll out realistic Agile strategies organization-wide.
Jeffrey Davidson has been exploring the boundaries of building world-class IT teams through leadership, training, and coaching teams and executives for over 20 years. A recognized expert in building agile software development teams, he has taught thousands and consulted with multiple Fortune 100 corporations. Jeffrey’s ability to blend strategic thinking, powerful questions, and experience makes him a desired coach when companies want to turn theoretical knowledge into real-world application.
Jeffrey’s goal is simple, he wants to help you and your team achieve greatness. Does that sound so hard?
Zach VanMeter is a software engineering consultant for Pillar Technology in Des Moines, Iowa. Industry experience includes the great DSM trifecta of insurance, banking, and agriculture. His normal work day is heavily influenced by both Scrum and Extreme Programming (XP) practices. Zach's career started in business analysis and his desire to be closer to the nuts and bolts of value delivery led to his career in software development.
Kevin is a software engineering consultant for Pillar Technology in Des Moines, IA. He has enjoyed how much Pairing, TDD, CI and other Extreme Programming practices has made developing software enjoyable and exciting. Continuing to learn different, new, old, crazy, simple ways to enable quality software development and deliver business value quickly is a major passion of his.
A self-proclaimed nerd, Brandon Carlson works for Lean TECHniques, Inc., an IT consultancy that helps teams deliver high-value, high-quality products to market. Since starting his career in 1995, Brandon has been blessed with nearly 20 years of experience to remind him how much more there is to learn. Passionate about elevating the performance of the IT industry, he has helped numerous organizations from startups to Fortune 100 companies improve their product development and delivery systems. Brandon’s current interests include behavioral psychology and professionalism in the world of software development. He can be reached on Twitter and pretty much everywhere else on the web as “bcarlso”.
Jodi Jones is an agile software delivery consultant and coach for Source Allies. She enjoys working with software development teams, and focuses on improving delivery using agile techniques.
She is a change enthusiast with a passion to make organizations and the community a great place to work for technology professionals. Jodi co-founded both the Des Moines Charity Hackathon and the Des Moines Agile conference, as well as organized internal company hackathons.
When not collaborating with her team, you will probably find her running on local trails or racing in her next marathon.
Kent J. McDonald uncovers better ways of delivering value by doing it and helping others do it. His 20 years of experience include work in business analysis, strategic planning, project management, and product development in a variety of industries including financial services, health insurance, performance marketing, human services, nonprofit, and automotive. He is active in the business analysis and agile software development communities helping people share stories about what does and does not work. He shares those stories at beyondrequirements.com in addition to presenting at and helping organize several local and international conferences.
Kent is author of Beyond Requirements: Analysis with an Agile Mindset, and co-author of Stand Back and Deliver: Accelerating Business Agility.
Keith Dahlby is a father, web developer, Git enthusiast, language geek and seven-time C# MVP from Cedar Rapids, Iowa. By day he is CTO of HuBoard and Architect for the New Bohemian Innovation Collaborative; by night he once blogged with Los Techies, but now mostly argues on Twitter. His open source efforts include posh-git, a Git environment for PowerShell; and up-for-grabs.net, a site featuring open source projects looking to mentor new contributors. He's also a core contributor to LibGit2Sharp, used by GitHub for Windows and Git for Visual Studio. Keith studied Computer Engineering and Human-Computer Interaction at Iowa State University, and has spoken at developer events around the world. His talks have been described as "terrific!", "very interactive!", and "the best I've seen all hour!”.
Joshua Carson is the API Evangelist for John Deere. He has worked with software teams for eight years. He focuses on how to learn as quickly as possible, getting different teams required to make software communicate with each other, as well as finding the root causes to whatever happens to be going on.
Joshua has been practicing various forms of Agile development for the past six years. As either a developer, tester, customer support, project manager, or any of the other roles required to make a working product, he has seen a variety of software projects from a variety of different views. He has seen how just getting the right people in the right place can make all the difference. His focus is on getting the people on the ground what they need to get the job done with as little overhead as possible.
Tim is a long-time programmer (since 1979), reviewer, speaker, writer. He has been active in many of the big changes in software over the past 36 years (including Design Patterns, Object-Oriented Design, and Agile software development).
In addition to his contributions in "Clean Code" and "Agile In A Flash", Tim's articles appeared in the C++ Journal, Pragmatic Bookshelf, InfoQ, CIO, and SmartBear.
Tim is one of the crew of experts at Industrial Logic, a premier agile consultancy, eLearning vendor, and thought leader. Here he joins with other industry experts to help people develop the skills that will make them awesome.
Tim muses about of his experiences and ideas on the Agile Otter blog and the Industrial Logic company blog.
Tim Gifford is a software delivery consultant specializing in Extreme Programming, Lean, Agile and DevOps. He has been producing software with teams for over 20 years. He’s been involved in projects ranging from small websites to scaled Agile adoptions at Fortune 100 companies. In 2001, he created one of the first social networking sites without realizing it.
As a Software Delivery Coach, Tim Gifford works with companies to transform their software from a liability and cost center to an asset and competitive advantage.
After years of consulting and conferring with teams from Activate to Zappos, Matt Heusser has seen more that how teams test - he has seen how test strategy changes over time to support more ambitious development approaches.
That vantage point gave Matt the opportunity to put together a playbook - a guide to the recurring patterns of success, and failure, that he has for teams on the page of continuous improvement. Teams that moved from heavily documented process to light, to executable examples and exploration, and, for some, one-piece flow and continuous delivery tend to experiment with technique — some techniques seem to work, and others, not so much.
Come benefit from the experience of others as we discuss a move to a fluency model for Agile-Testing, with real examples. Take home ways your team might evolve … and perhaps a few things to avoid.
Behind every awesome product is a team who trusts one another and works well together. This is the positive case of Conway’s Law, in which a system is a reflection of the organization that built it. At the other extreme is a system built by a team whose members are distrustful, do not collaborate, and are ultimately dysfunctional. The resulting product will inevitably fail its customers. Adding and revamping features to such a product would be dressing up a rotten egg.
Rather, we must form a healthy team in order to have a healthy product. How do we do that? How do we find the “right” people; bring them together and ensure the outcome is a great product?
In this talk, we’ll explore 5 (not so easy) tips about doing just that. We’ll inject thinking from past and present leaders; and leverage Lean & Agile principles, to build and sustain a healthy team.
Have you also been binge watching Narcos on Netflix? From this portrayal we see that much of Pablo Escobar's success can be attributed to the relationships that he built and his ruthless nature. These are qualities also key to the success of the modern Product Owner. This session attempts a humorous comparison as well as offers an in depth discussion about the key relationships of a Product Owner and how to build them.
You don’t need to be a mechanic to know something is wrong with your car. And you don’t need to be a programmer to know if something is wrong with the code.
This session will focus on training you to have a ‘sense of smell’ for bad code. So you can increase the serendipity in your explorations by having insights into which sections of code are particularly error prone.
Let’s take a look at how quickly we can instill some design sense into fresh minds using Sparrow Decks. Sparrow decks are a rapid succession of 50-100 examples in a 3 minute burst. They allow the pattern recognition portion of the brain to spring in gear and do what it does best.
No one sets out to fail when they embark upon an Agile transformational journey. Far too often however, the same failure patterns are visible, especially to practitioners who work with many organizations. In this interactive session, we will discuss the top ten most common anti-patterns that threaten the success of enterprise Agility. We will also generate insights about the root causes - why these patterns emerge over and over again. Following our session, you'll have the knowledge you'll need to diagnose these patterns, and some strategies for avoiding these ten mistakes you shouldn’t make.
Over the past few years there’s been a push in the product development world to “make products that people love”. While many companies focus on having the best design and the greatest experience, they are still missing the most important step in product development – learning about their customers.
The popularity of Agile and Lean has sparked discussions about getting software out faster to users. At the core of this has been the Minimum Viable Product. Unfortunately, many people still do not understand the MVP. Some see it as a way to release a product faster. Others are scared of it, viewing it as a way to put broken code on your site and ruin products.
The sole purpose of Minimum Viable Product is to learn about your customers. This step that has been so overlooked and yet it is the most essential part to creating a product your customers will love. The more information you can uncover through experimentation, the more certainty there is about building the right thing. In this talk, Melissa will go over how to design the most effective product experimentations to learn about your customer, their problems, and how to solve them. She’ll explain how to get the rest of the organization on board with this method of testing, and how to incorporate it into overall Product Strategy.
What are the misconceptions of an MVP
What the goal of an MVP really is
How to do effective product experimentation
How product leaders need to change their styles to coach experimental teams
One of the major success factors in an agile transformation is helping teams take ownership: the teams own the solution. This requires Leaders learning how and when to step back (and when to step up.)
The Veritas NetBackup organization has tried agile transformations three times in the last seven years with the first two not succeeding and the third one going much better. The key difference has been the transformation of the Leaders to help teams take ownership as opposed to focusing only on the scrum artifacts and ceremonies. Moving from managers to Leaders is not an easy task. How did these Leaders learn? What did they learn? Join us to hear about NetBackup’s transformation story and some of the concepts and techniques that made the difference such as learning to be an enabler, how to ask questions and not give answers, and other tools.
We are not practicing the same Agile we did 15 years ago. Agile at scale is mainstream. Thousands of companies are actively seeking information on how to scale agile effectively. There are many frameworks and techniques but they all boil down to a set of common principles. Agile done well involves teams, programs and portfolios in a way that aligns strategy and execution. It's important to apply a proper team foundation to build things right but without agile applied at the program and portfolio level all we may end up with is the wrong things built faster. In this talk Julie will discuss how to effectively apply Agile to your portfolios and programs to ensure you are also building the right things. Learn to create value, not just process.
Are you hungry? Eat this pre-processed, fast food hamburger!
Still hungry? Add a large order of French Fries!
New to iterative software? Use Scrum!
Tired of Scrum? Use Kanban!
Got lots of teams? Use SAFe!
We know a healthy diet values natural foods over the simplicity and ease of fast food. Similarly, many agile techniques are much more valuable than the simple, fast food version of software development everyone is teaching.
Over the last 15 years we started relying on other people's best practices instead of developing better ways of delivering software. We are using solutions developed for a different team, in a different decade, in a different company, in a different industry. There is such a rich tapestry of ways to build software and we are stuck eating software's version of fast food.
This interactive session discusses a bunch of different Agile techniques and when they are useful. Then we will look at just how different agile might be if we picked only the most appropriate items. Lastly, you will work with a few peers to determine if you need to swap a few techniques, or even build a personalized version of Agile, specially designed to help with your situation.
Pair programming often recommended as a fix to software projects, but why send two people to do the job of one? We'll talk about why pair programming is not a scam to double the cost of a project and deliver half the value.
Zach and Kevin work daily in an agile environment that embraces the practice of pairing. We'll share the value that pairing brings to the business, the team, and the individual. We'll discuss the right and wrong ways to implement pairing and provide pragmatic ways you can make it work for your organization. We'll share our lessons learned from real life projects and experiences and what can be done to overcome common issues that affect the success of pairing. You will be able to walk away with answers to common questions and solutions to ensure pairing is successful in your organization.
You've probably heard that You can't improve what you can't measure sible visible. From value stream mapping to burndown charts, making things visible is a core component of the continuous improvement process. Brandon Carlson says that even with all this visibility, much of the data surrounding how your teams work is either not captured or not visible, and thus represents a great opportunity for improvement. Imagine your management team tells you that your velocity is too low. Why is it too low, and what can you do about it? Brandon shares one team’s surprising answer to that question when they analyzed previously invisible data. How do you know what the highest risk areas of the system are for enabling the most cost effective regression test strategy? You'll get that answer, too. It's all there, tucked away where no one can see.
The Scrum Master role is a foundational concept of Scrum, yet like everything else, the role and it’s value should not be fixed. As with everything else related to agile, the nature of the Scrum Master role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions:
We hear it all the time: face-to-face communication is best. Co-located teams are more collaborative, more productive, more manageable. Pair programming is more efficient than code review. Mob programming—literally the whole team around one screen—may be even more efficient. This session won't try to argue that these statements aren't true in the moment, but rather that these optimizations achieve a local maximum. We will explore the limitations of co-location, and discuss distributed communication patterns that can help even mostly co-located teams achieve their global maximum.
Are you dreading your demo days? Have you seen more slides about 'working' software than you thought possible? Is everyone just checking their emails?
Demos can and should be a valuable part of your projects feedback loop. They can let you know when you've discovered something great. They can let you know when you went too far into a bad idea. They can let you know just how far away you might be from something your customers need.
How often are demos something that add all that value? What about even adding any value? This session will give you the tools you need to make demos that don't suck. Learn how to spot bad demos, what key things you need in your demos, and even a bit about how to make demos that can wow your stakeholders.
We have at the seen teams evolve in line with original agile principles and modern technologies to be more exciting, more capable, more helpful, and ever more lean.
At the same time, other organizations have evolved their agile practice away from the original values and principles through a series of compromises, until it has become a lifeless set of formalities.
We realized that the most deeply, impressively agile teams we know seem to have connected on four values.
They make people awesome, deliver value continuously, and experiment and learn rapidly. These challenging changes are only possible because of the safety that permeates their practices and culture.
Come for a re-think of agility and a challenge that may transform your experience of software development.
DevOps lore tell legendary tales of “Unicorn” companies. We’re told these mythical companies continuously deliver software to production with nary a blemished aura or mussed mane. Can it be so? Is this but a fairytale?
In this talk, we will dispel the fantasy and show you how to get similar results. Spawning the first unicorn is the most difficult, so I will show you the specific steps, tools, techniques and architectural patterns of Operations First Delivery to create your first “Unicorn” project.
|Schedule||Room 302/303||Room 304/305||Room 306/307||Room 308/309|
|8:00 - 9:00||Check-in and Registration - Ballroom B|
|9:00 - 9:30||Opening - Announcements, Speaker Introductions - Ballroom B|
|9:30 - 9:45||Break|
|9:45 - 10:45|
|10:45 - 11:00||Break|
|11:00 - 12:00|
|12:00 - 1:00||Lunch (Provided) - Ballroom B|
|1:00 - 2:00|
|2:00 - 2:15||Break|
|2:15 - 3:15|
|3:15 - 5:00||Open Space - Ballroom B
Networking, Drinks and Tapas - BallRoom B