• Coaching skills – peer coaching, user of personas, solution driven coaching. Visual representation of product owner role
• Better taskboards. Expand Continuous Integration
• Stuff about values
• Dots on stories to measure (lean) lead time
• Coding dojo is a great idea. I’m going to give that a shot at my own company
• Not asking (or less) “Why?”
• Dojo
• [Pierluigi] Solution Focused Reasoning. SLIM. [Serge B.] Product Owner Kanban
• Ready Kanban. Try & improve peer coaching
• Coaching
• Help our product owners more. Don’t ask “Why?” too much
• Solution Focused Approach. Systems thinking approach to conflict resolution. Tools to support Product Owner
• Conflict Resolution (a spike with it anyway). Continuous Integration. Thinking about “Toyota thingys”
• Fitnesse. Product Owner dots
• Story striptease
• Read more books (but I promise that to myself every year )
• Code smells
• Some team-coaching techniques
• Conflict Resolution
• Questions! Questions! Questions! It’s all about powerful questions
• A bit of everything
• Continuous Integration for system admin. User stories for non-dev work
• Conflict Resolution without Compromise
• Improve my coding skills
• Conflict Resolution Diagram
• Story Mapping
• Don’t know yet what would be possible…
• Good ideas about asking the right questions as a coach. The werewolf game
• Story mapping
• BoF, TDD, Agile, Scrum
• Automated testing/TDD, hopefully Fitnesse. Technical/Architecture guidance
• Conflict Resolution Diagram. Open questions. Retrospectives
• Have to think about it
• Check about “Nono’s”. Practice Birthday Greeting Kata. Look at Kent Beck’s videos
• Code smells
• Brainstorm. Include testing earlier
• Visualising better Scrum boards
• Story dots
• Deborah Hartmann references
• Fitnesse with SLIM runner. Solving conflicts method. Coding dojo
• Powerful questions, team values, set the good urgency, listen to the team
• Smells as a vocabulary for describing technical debt. Coding dojo
• More retrospectives
• Try coding dojo. Read the Core Protocols again
• Story mapping. Product Owner storyboard
• Storyboard mapping. “Ready” state of user story
• Toyota Way. Win-win (no compromise). Dojo. Continuous integration with OPS => DEVOPS
• Adapt theories to our own area
• Mainly coaching skills, e.g. input from Solution Focused thinking
• Science Scrum! Visual Management
• Solutions Focused, a new kind of question setting
• Retrospectives not only after sprint but also in crisis
• Everything
• Open Space meetings. User Story Mapping and much, much more
• Oh-so-much. VM builds. Continuous Integration with performance and profiling. Conflict Resolution
• Continuous Integration
• A lot!
• Agile methods in Software architecture. Encourage team members and management to pay attention to Agile
• Open Space
• Conflict Resolution. Retrospective should become a safe place
• I’m new to this area, a lot
• Lots
• Team values. Product Owner tools
• Visualisation
• Story mapping, story striptease, interviews, miracles
• Scrum board enhancement
• Conflict Resolution Diagram
• The games
• Using code smells. Play games as a way to teach others
• Pierluigi’s stuff
• Solution Focused approach

Tag clouds made with Wordle