Category: Videos

Unfucking Feedback in Project Teams

Feedback sucks. It is horrible to give inside a project team, it can be painful to receive – even when it is praise, we are still uncomfortable. It is a problem, because if members of a software development team can’t give effective feedback to each other, and if we can’t...

Self-Governing Teams With Sociocracy for All

Are you interested in learning more about self-managing teams and how to share authority within an organization? This talk discusses the basic patterns and processes of Sociocracy for All, a system of self-governance that can be used in combination with Agile practices to scale self-organization across all decisions made in...

Five Reflections for Modern Leadership

Why are we as leaders drawn to the simple and quick solutions? Answers over questions? This presentation is a little journey of reflection and discovery for modern leaders. You already know this: The world is constantly changing.

Minimum Viable Process

Eric Ries defines a Minimum Viable Product as the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. Using the Minimum Viable Product concept is valuable, but its effectiveness is often hampered by excessive process.

Four Project Feature Prioritization Systems in Four Minutes

Small software development projects are easy to manage. GitHub issues or Basecamp todos are more than enough to keep things going. Adding a feature or refactoring a small software development project is also easy, because there aren’t too many moving parts to consider.

Scaling Agile: The Small-is-Beautiful of Hubs

Scaling agile is all the rage these days, and especially popular with laggard adopters who want to broaden their management span of control. Most scaling frameworks are just classical military hierarchies suitable to command-and-control: in a suitably arranged organization of 625 people, the average number of communication hops between any...

Limiting Work-in-Progress (WIP) for Software Developers

The idea of limited work-in-progress (WIP) is coming from Lean methodologies. At its core, it means that software developers should start new tasks only when the current piece of work is done and delivered. Finding the right work-in-progress limit can increase overall system (organization) throughput.