The Agile principle of “trusting work to the self-organizing, self-managing teams” is radically different to the military doctrine of “strict top-down hierarchy, command & control”. Yet almost a 100 years ago this idea was tried out on many battlefields and the consequences are still felt today.
Have you ever wondered why, when you’ve finally got Agile/Lean working nicely in your software engineering team, managers or ‘outsiders’ can come in and create politics ‘un-necessarily’, despite your best efforts? Have you ever sat there in meetings frustrated and exasperated at the seemingly unnecessary dramatics some participants go through?
We are incessantly, almost compulsively drawn to gatherings of intelligent, creative people. While we are looking to learn ways to change our professional and personal lives for the better with Agile approaches, on a deeper level, we’re compelled because we crave profound change and the inspiration to instigate a revolution.
Similarly to design patterns, present pedagogical patterns solutions to recurring problems in a given context. The wider context for the pedagogical patterns is teaching and learning, especially of technical subjects.
What is a responsible programmer? What habits does a responsible programmer have? I started asking myself and others that question and this presentation is the result of this. I will look into good habits for coding, using tools, managing environments and working in projects.
Learn how, when and why to break the rules. This presentation takes you on a full tour of what creativity is, what it isn’t, the 8 different types of creative contributions, and which environments are best-suited (and worst-suited) for those types of creativity. I will also discuss recent research on …