I think Pair Programming is vital to the success of a programming team, but every time I join a new team I seem to find I’m in a minority of people who feel that way, let alone have any experience of actually doing it.
Find out why we give personal feedback, how to provide effective feedback, what makes feedback ineffective and how to deal with poorly phrased feedback. Learning what makes feedback effective helps you to seek your own feedback and improve, whilst being able to support the people around you.
This is suitable for anyone who’s nervous about giving or getting feedback. Coaches and other Agile Transformers may find this simple workshop helpful for their own teams.
Agile coaches often need to distinguish when people “do” an agile practice versus “really understand” that practice. This workshop will help coaches develop a tool, mapping agile practices, or more specifically, behaviours people exhibit when using an agile practice, to a learning model. The learning model of choice for this workshop is the Dreyfus Model of Skill Acquisition. We will also discuss how to apply this tool to better communicate and set goals with teams “going agile”.
Increasing gender intelligence strengthens our ability to maximize the contributions of all members of the team while maintaining both equity and uniqueness. New research from neurobiology sheds light on the real differences in male and female brain structure, chemistry, and blood flow. This data underlies the emerging science of gender intelligence, providing a new vision of gender relationships. Gender-intelligent supervision, employee coaching/mentoring and negotiation and conflict management leads to a competitive edge in the toolkit of forward-looking companies.
Our ability to identify patterns of behavior and the likely reasons behind them helps when addressing team dynamics issues. The popular Scrum characters chicken and the pig turn out to be just two of many behaviors that comprise the Scrum Bestiary. Other examples include the seagull - who derails the team and leaves - and the fox - who is intent on stealing vital resources. This humorous workshop presents a taxonomy of some common behaviors on teams and looks at the drivers behind them and strategies for addressing them.
This report describes how scrum was adopted by more than half of the software developers at Amazon.com (and counting). The adoption was due largely to the efforts, both accidental and purposeful, of an internal employee. Amazon’s corporate and development cultures played important roles, both positive and negative. With no executive sponsorship, adoption occurred primarily a team at a time. The wide range of success across teams and organizations leads to a number of important lessons learned with regard to enterprise scrum adoption. The lesson: you can cause this to happen.