Optimize Your Human/Robot Mix for Ferocity with Confidence
Experienced agilists know that if you want to be fierce and move fast, you need confidence that you can charge ahead without leaving a mess behind. Strategically, this means defining the things you already understand so tightly that you can hand them off to robots. With automation guarding your back, you can focus your human energy on conquering new challenges. That’s the theory anyway. In the mess we call real life, most of us struggle to draw the line between human work and robot work, so we frequently end up with frustrated humans chasing ineffective robots.
In the context of real life on the shop floor, how can we optimize our robot/human mix in a way that frees the most human energy to perform the most human work? In this session, we will approach the question from two perspectives: DevOps and software testing. Both have the same general problem but they bring different needs and difficulties.
Outline/Structure of the Talk
The session will be driven by a single question: what is the appropriate mix of human and robotic effort in my functional area?
- The kind of work that humans do well
- The kind of work that robots do well
- Example mix from real life: software testing at CyberGRX
- Example mix from real life: DevOps at CyberGRX
- Discussion: let's talk about your mix
Participants will be equipped to think strategically and pro-actively about what they should and should not automate, rather than reacting to each proposed solution in isolation.
Spoiler: DevOps and test represent opposite extremes. Charles will argue (quite strongly) that humans belong in the Dev part and the entire Ops part should be automated. Mike will argue (equally strongly) that testing is a learning activity and therefore very human. The role for robots in the test function is to aid the humans in their learning and to detect unexpected changes. The lesson we hope to share from this contrast is that the question about appropriate mix does not have a single "right" answer.
managers, team leads, students
schedule Submitted 11 months ago
People who liked this proposal, also liked:
Steve Ropa - Career growth, recognition and continuous learning for software craftspeopleSteve RopaMaster CraftsmanRocky Mountain Programmers Guild
schedule 9 months agoSold Out!
Over the years, we've talked quite a bit about how to become a craftsman, exploring deeply how to progress from Apprentice to Master. What is often missing is any detail beyond the general thoughts that this is a Good Idea. Steve will share an approach, based on his experience of many years and many development organizations, to learning and career development for your team. This approach goes beyond the general ideas around Craftsmanship, but provides actual concrete areas of development. Unlike a formalized "skills checklist" we will apply a pattern language to help identify a continuum of growth for anyone's long term development.
We will discuss building understanding and building skills in the following areas:
Process and Technical Ecosystems
Joel Tosi - Product Framing Workshop - OKRs, Personas, Storymapping, Oh MyJoel TosiDojo & Co
schedule 10 months agoSold Out!
In this hands on workshop, teams (4-5) will use Product Chartering, Personas, Storymapping, and User Journeys along with Experience Tests to explore a product of their choice.
Along the way we will touch on how you blend architecture needs into this as well as chaos engineering - especially if the audience is more technical
The takeaways are hands on approaches to product discovery and how it blends into delivery
Steve Ropa - Craftsmanship is NOT ExpensiveSteve RopaMaster CraftsmanRocky Mountain Programmers Guild
schedule 10 months agoSold Out!
Whenever someone wants me to buy something expensive, they tell me to think of it as an investment. Over the years, when a business person heard about Craftsmanship or certain Technical Practices, they immediately heard the same argument about it being an investment. Lets look at it differently. Craftsmanship is not more expensive than "Just Get It Done" even if you ignore the long term investment aspects. By exploring where the technical practices come from, and how best to apply them, we can see that being the best isn't more expensive after all.