matthewmccullough
commented
10 years ago :+1:
Open tlberglund opened 10 years ago
matthewmccullough
commented
10 years ago :+1:
danhillenbrand
commented
10 years ago :+1: Both sound good to me
I'm very interested in hearing you thoughts on abandoning Product Owners. My take is that they should be leaders that facilitate the collaboration of all stakeholders of a product, not be what appears to be dictators from the development side. I look forward to your talk!
tlberglund
commented
10 years ago @danhillenbrand All will become clear. :)
Might you update dat Meetup site? These talks are hereby declared to be :ship:ed.
I would like to volunteer to speak at the September meeting. Two talks! What do you guys think?
Discrete Math You Need to Know
What do you need to know about prime numbers, combinatorics, and the underpinnings of public key cryptography? Well, maybe more than you think!
In this talk, we'll explore the branch of mathematics that deals with individual, countable things. Most of the math we learn in school deals with real-valued quantities like mass, length, and time. However, much of the work of the software developer deals with counting, combinations, numbers, graphs, and logical statements: the purview of discrete mathematics. Join us for this brief exploration of an often-overlooked but eminently practical area of mathematics.
First, Kill All the Product Owners
By now, we are all comfortable with the orthodoxy: the product owner discerns the needs of the customer and feeds them to developers in the form a prioritized backlog. Developers pull work from that backlog, always confident that they're working on the highest-priority feature at the moment, and never having to worry about how those priorities are allocated. This system is simple, efficient, and has helped many teams function better than they used to. It's also time for the system to die.
A few revolutionary companies are experimenting with the idea that developers should be in charge not only of when they build new features, but what features to build. Rather than mere code technicians following the will of a product and marketplace expert, developers themselves become experts in their product domain, building the tools users need—by conceiving of those tools themselves. Dispensing with the product owner creates an entirely new organizational tenor: one in which everyone is encouraged to master the business's domain, to organize their work in autonomous ways, and to take ownership of the purpose for which the organization exists.