11:30 - 12:30 - 60 min Session

Advanced Discussion of StoryPoints for Project Management
Dan Rawsthorne
Acacia A
See The Future

We know that StoryPoints are "a relative measure of size that can be applied to Stories and Epics." Beyond this simple statement there is not much about StoryPoints that we can all agree on - teams and organizations are free to estimate and use StoryPoints as they see fit. Well, I want to use them to aid in Project (not Sprint) Management, and in this talk I present a way to define StoryPoints for this purpose. Come and hear words like "Ideal Effort", "Intrinsic Difficulty", "Function Points", and "Earned Value", and how StoryPoints become the basic currency for Release budgeting and metrics.

Breaking Analysts: A Real-World Tale of Converting a Traditional Business Analyst into a Lover of Scrum
Leslie J. Morse
Acacia B
Build The Future

Pictures convey ideas more clearly and have a greater impact than a simple conversation. The ability to communicate, and perhaps sell, your ideas at a whiteboard is an essential skill for anyone on an Scrum team. In this hands-on session based on Dan Roam’s book, “The Back of the Napkin”, we will learn the six types of diagrams used in business and how to select the right picture for your problem. All you need for this session is an issue, your imagination and the ability to draw a circle, square, arrow and a stick figure. Come on - give this a try. It will be fun.

Technical Practices: What Product Owners, ScrumMasters, and Managers Need To Know
Chet Hendrickson, Ron Jeffries
Acacia D
Build The Future

Successful iterative software development requires some well-known technical practices. Scrum traditionally leaves the discovery and implementation of the practices to the Development Team. However, we continue to see projects struggle due to the lack of good technical practices. In this session, we will give ScrumMasters, Product Owners, and other project Stakeholders the tools they need to understand whether their Development Teams are using the right technical practices, and how - and why - to influence them to improve.

Fixes that fail
Dhaval Panchal, Valerie Morris
Paloverde A
Build The Future

Does your management use velocity as a weapon? Are you concerned about your product’s quality? How have you approached these systemic problems? This session is for those who recognize that symptomatic fixes will not address their core issues. For those interested in learning how to change the conversation with their management, this session will introduce basic systems thinking tools and walk through a case study of an agile organization that is beginning to appreciate the interconnectedness of velocity, quality, morale, revenue etc., in their ecosystem.

Helping Dispersed Teams Bridge Time, Distance, and Culture
Michael Tardiff
Paloverde B
Build The Future

"Our teams are distributed--that's just the way it is today." That's the refrain heard across widely dispersed organizations that seek to gain the benefits that Scrum offers. And sure enough, there are myriad situations where people who want to and need to work together have trouble *being* together physically. This talk is an interactive exploration of the real-world ways teams that are separated can and do work together, with an emphasis on practical ways to bring teams and individuals closer, physically or virtually. Attendees will leave with real xamples and specific recommendations.

Agile Metrics: Velocity is NOT the Goal
Michael Norton
Mesquite 1-3
Build The Future

Velocity is one of the most commonly misused metrics on agile projects. We often focus on improving velocity without proper consideration for root causes. Learn about The Hawthorne Effect, Goodhart’s Law, and why setting goals for velocity can actually hurt a project’s chances of success. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project’s overall health.

Mob Programming: A Whole Team Approach
Woody Zuill
Mesquite 4/5
See The Future

Mob Programming is a Whole Team Approach to developing and coding software: The whole team works on the same thing, at the same time, in the same space, and at the same computer. We've expanded on the idea of Pair Programming by including all team members, including QA and Product Owner, working together at the same time on all the work we do. We have developed practices that allow all team members to contribute (or receive) value througout the day. This has been very productive for us, and has resulted in higher quality and more useful software.