Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By, Ernie Miller Agile. Scrum. Kanban. Waterfall. TDD. BDD. OOP. FP. AOP. WTH? As a software developer, I can adopt methodologies so that I feel there's a sense of order in the world. There's a problem with this story: We are humans, developing software with humans, to benefit humans. And humans are messy. We wrap ourselves in process, trying to trade people for personas, points, planning poker, and the promise of predictability. Only people aren't objects to be abstracted away. Let's take some time to think through the tradeoffs we're making together. Help us caption & translate this video! http://amara.org/v/GTxn/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the talk "Humane Development" at Ruby on Ales 2015, Ernie Miller discusses the importance of recognizing the human element in software development amidst prevalent methodologies like Agile, Scrum, and Kanban. He emphasizes that while processes and frameworks provide structure, they often reduce individuals to mere objects or resources, which can harm organizational culture and employee satisfaction. Key Points Discussed are: - **Human-Centric Development**: Miller introduces the concept of "humane development," advocating for a focus on the human aspects of software development rather than treating employees as mere resources. This approach prioritizes compassion and empathy in workplace relationships. - **Challenges with Traditional Methodologies**: He shares his experience in a previous role where the implementation of a Kanban board led to overwhelming stress among employees, as they were treated like components in a production system rather than valued individuals. - **Value of Individual Experience**: Miller reflects on how he previously could leave jobs without feeling responsible if things weren't working, contrasting this with his current position where he feels a direct responsibility for creating a healthy work environment. - **The Misuse of Agile Concepts**: He critiques how Agile methodologies have been misinterpreted in organizations, often prioritizing speed and control over human-centered values. This is reflected in the shift from Agile principles towards a focus on certifications and rigid processes. - **The Importance of Asking Why**: Miller stresses the significance of questioning tasks and deadlines—"Why do we need to complete this?"—to avoid unnecessary work on problems that may not exist, thus encouraging more thoughtful and effective development practices. - **Sustainable Work Practices**: He argues against the glorification of "hustle culture" and emphasizes the need for sustainable work rhythms, comparing effective workflow to a marathon rather than a sprint. In conclusion, Miller urges attendees to consciously integrate humane values into their development practices, advocating for a balance between process and the unpredictable yet beautiful nature of human beings. The main takeaway is that to foster a successful and thriving development culture, one must prioritize human connections and question the underlying motives of work demands.
Suggest modifications
Cancel
