Description
After completing anything, you can use retrospectives to look back and learn . This is a great way to learn and improve whether looking at software development in an Agile environment or starting a new workout program. In this session we will discover ways to do retrospectives, and how to use them to make improvements going forward. We will conduct at least one retrospective as an example for you to leave with.
Speaker Bio
Susan Smith is an experienced IT professional with 20+ years of experience with software development teams. Susan has held many positions from business analyst, quality analyst, to management positions. She has helped several companies bring Agile development methodologies into their SDLC. Susan’s current focus and expertise is process improvement, on time software delivery with business value, and team building.

Description:  
Have your Agile practices become stale or redundant? Does it feel like your team is just going through the motions? Have team members asked to discontinue “critical Agile practices” and ceremonies?
In Lean product development, the minimum viable product or MVP, is defined as the product with the highest return on investment versus risk. It’s a strategy to avoid building products that customers don’t need or want by maximizing our learning of what is valuable to the customer.
Agile is typically learned through exposure to a series of Agile practices, a recipe of sorts.  But what if that recipe goes beyond minimal? Have we replaced heavy waterfall process with heavy Agile process?
Speaker Bio:
Troy Tuttle is a Lean-Agile coach, software developer mentor, and consultant with almost a decade of experience working in Lean-Agile environments. He currently operates KanFlow, a consulting firm dedicated to helping software professionals, teams, and organizations improve by the study and application of Lean and Agile principles and practices. Most of his work is directed by approaches that support better clarity, understanding, and continuous learning about Lean, Agile, and the nature of knowledge work itself.
Troy has been heavily involved in the community as a facilitator and speaker. He founded the Limited WIP Society of Kansas City in 2009—a user group for Lean, Kanban, and Agile practitioners to help others in the community with the theory and practice of Lean software. He also regularly speaks at local, and regional events and conferences. Recently his interests have focused on systems thinking and complexity theory as alternative means to achieve a better understanding of Lean and Agile software development.

Description:
The #FailFast concept was first coined in the late nineties but has had a resurgence with the DevOps and Agile movements. Unlike Agile and DevOps though, #FailFast has conflicting views on whether the movement is good and bad. Let’s go over the history of #FailFast, look at some case studies, and discuss ways to incorporate the ideas into our lives when it makes sense.
Speaker Bio:
Sarah is a Technical Project Manager in the Program Management Office at Cerner Corporation. She has worked in the automated testing, mobile and interoperability spaces at Cerner in a number of roles and holds certifications as a Certified Software Quality Analyst, ICAgile Certified Professional, and a Project Management Professional. When not working, Sarah is quilting, competing in dog agility, or chasing her 18 month-old twins around.