This is the presentation of the software developer that suffers from Type II BiPolar and ADHD. It’s not something we talk about, but BiPolar, depression, and ADHD runs rampant in the software development community – they tend to correlate with higher intelligence.

One of the best ways to move yourself forward as a developer is to have mentors who can forward your skills, or to be a mentor for a newer developer. Mentoring isn’t limited to just “hard” or technical skills, and a mentoring relationship can help in all aspects of any career – be it open source, a day job, or something else entirely.

This session walk you through charts from real Kanban teams asking “what should be happening”?

Agile software development was born ten years ago, with a gathering of industry luminaries in Snowbird, Utah. They were frustrated that so much ceremony and effort was going into so little success, in failed project after failed project, across the software industry.

This presentation reviews the top 10 myths and misconceptions, along with a few neglected and important principles of Lean thinking that many in software development, including Kanban practitioners, neglect. I first learned about a Kanban approach to development from an apologetic agile practitioner concerned that they’d broken “the rules.” Although it’s common practice, fixed time-boxes aren’t a required strategy for agile development. Since Kanban’s broad adoption, I’ve continued to encounter a number of myths and misconceptions both for and against Kanban.

The most well-known developers have something in common: they’re productive. Usually, it isn’t just dumb luck. More often than not, they’ve focused on becoming more productive.

As a full-service online-agency e-netconsulting KG ist specialized in technically sophisticated web- and mobile-solutions. Aiming for improvement of internal processes Kanban soon appeared as a suitable method. Kanban enables us to model the entire value-added-chain . Focusing on software-development led to high response time regarding inquiries and often did we not go the whole distance, i.e. documentation and similar tasks remained incomplete.

Learn how Kanban, as an alternative to top-down approaches, can be used to support introduction of best software development and organizational practices using a few real-life examples.

How do I make my managers more Agile?, How can I convince developers to educate themselves?, How can I make customers more cooperative? When transforming organizations and other social systems people usually encounter obstacles. And these obstacles very often involve changing other people’s behaviors. Of course, we cannot really _make_ people behave in a different way. We also cannot really make people laugh, and we cannot really make people happy. But… we can certainly try!

Based on a real project experience, this presentation covers all dimensions that make great teams: hiring, communications, methodology, environment, culture, and community.

Producer : Lone Star Ruby Conference