Arty Starr
Central Iowa Software Symposium
Des Moines · August 5 - 7, 2016
Author of Idea Flow, Founder, FlowInsight
Arty Starr is a recognized Flow Experience expert, researcher, speaker and thought leader, and author of Idea Flow, how to measure the friction in software development. Arty's PhD research is developing a theory of momentum in software development, and she is creator of the FLOWS platform designed to help developers thrive and find joy through more time in the flow state. The company she founded, FlowInsight, is on a mission to bring back joy to our everyday work.
Arty is also a 2D/3D animator and artist, and has spent the last couple years building 3D apps in AR. She loves to share about her experiences with these technologies.
Presentations
Keynote: Let's Make the PAIN Visible!
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the effects of learning curves, collaboration pain, and problems building up in the code?
With visibility we can:
- Identify the biggest causes of pain
- Make the case to management for improvement
- Optimize productivity with a data-driven feedback loop
Stop Getting Crushed By Business Pressure
This is my story of lessons learned on how to stop the crushing effects of business pressure… I was team lead with full control of our green-field project. After a year, we had continuous delivery, a beautiful clean code base, and worked directly with our customers to design the features. Then our company split in two, we were moved under different management, and I watched my project get crushed.
As a consultant, I saw the same pattern of relentless business pressure everywhere, driving one project after another into the ground. I made it my mission to help the development teams solve this problem. This is my story of lessons learned on how to transform an organization from the bottom up. I'll show you how to lead the way.
Learn Your Way to AWESOME.
How do we know if our improvements are actually making things better? If we refactor the code, did we make it better? If we skip the tests, are we making things worse? What does better really mean, anyway?
Once we start tracking metrics on the pain we experience during development, we've got a data-driven feedback loop to learn what actually works! Objective data enables us to do something we've never been able to do before in our industry: science.
The “Continuous Acceleration Toolkit” includes new metrics, new tools, and new science-based learning processes, designed to accelerate you and your team to a whole new level of productivity.
Top 5 Reasons Why Improvement Efforts Fail
This is my story of lessons learned on why improvement efforts fail… I had a great team. We were disciplined about best practices and spent tons of time on improvements. Then I watched my team slam into a brick wall. We brought down production three times in a row, then couldn’t ship again for a year.
Despite our best efforts with CI, unit testing, design reviews, and code reviews, we lost our ability to understand the system. We thought our problems were caused by technical debt building up in the code base, but we were wrong. We failed to improve, because we didn’t solve the right problems. Eventually, we turned our project around, but with a lot of tough lessons along the way.
Flow Theory & AI Architecture
I.flow() AI is an emotional intelligence AI that learns to respond in real-time to the pain of humans, for example, developers that are having a hard time. The I.flow() AI Platform is still in the early stages of mapping theory to concrete implementation, so in this talk we'll breakdown architecture strategy, pain metrics, pair programming buddy, supply chain flows, and the underpinning of Flow theory.