What's your experience coaching teams toward being Agile?
I've been involved in XP projects since 1997. I started coaching the process in 2000. Recently I have become involved in a Scrum-like project. My role has historically been geared towards mentoring technical practices, but in the last few years I have also moved into process coaching from a project management role.
What do you plan to learn /explore at this conference?
I have 2 areas that I'm really interested in exploring.
1) Teaching how to create evolvable designs. This is a purely technical pursuit. There are many schools of thought on "better" designs, but there are subtle things we do when we design and code that makes one design far more flexible than someone else's even though they use the same development practices. But explaining the rationale for some of these subtle hints to the "non-enlightened" ;-) usually falls on deaf ears.
2) Long-term (> 2 year) agile projects. Having been in projects ranging from 6 months to 6 years, there are some very interesting things that happen to teams when "the honeymoon is over." Agile is no longer novel and exciting, but just another thing a team does. I'm interested in ways to keep things fresh and energized when this happens.
How do you plan to contribute?
I'd like to participate in both technical and management sessions where the focus is on direct development team interactions (IOW, not those dealing with meta-roles like PMO and Project Owner). I'm particularly interested in how others succeed (or fail) in encouraging change in team members.
Looking forward to it.
I've been involved in XP projects since 1997. I started coaching the process in 2000. Recently I have become involved in a Scrum-like project. My role has historically been geared towards mentoring technical practices, but in the last few years I have also moved into process coaching from a project management role.
What do you plan to learn /explore at this conference?
I have 2 areas that I'm really interested in exploring.
1) Teaching how to create evolvable designs. This is a purely technical pursuit. There are many schools of thought on "better" designs, but there are subtle things we do when we design and code that makes one design far more flexible than someone else's even though they use the same development practices. But explaining the rationale for some of these subtle hints to the "non-enlightened" ;-) usually falls on deaf ears.
2) Long-term (> 2 year) agile projects. Having been in projects ranging from 6 months to 6 years, there are some very interesting things that happen to teams when "the honeymoon is over." Agile is no longer novel and exciting, but just another thing a team does. I'm interested in ways to keep things fresh and energized when this happens.
How do you plan to contribute?
I'd like to participate in both technical and management sessions where the focus is on direct development team interactions (IOW, not those dealing with meta-roles like PMO and Project Owner). I'm particularly interested in how others succeed (or fail) in encouraging change in team members.
Looking forward to it.