Coming OnBoard - 3 months of Making My Team More Agile — Paul Boos
My Experience
For the last 9 years, I have been customizing/implementing methodologies to be used with organizations. I would consider myself mildly successful, but each organization has had unique challenges that have prevented full-scale implementation of these methodologies. I now have a team that is extremely receptive to improvement and we have settled on a SCRUM-based methodology that we are in the process of implementing.
The Discussion
I'm interested in the discussion focusing on my experiences so far and learning about pitfalls that could come about that I haven't reached yet. While I understand SCRUM well from a learned sense, this is my first implementation of an almost pure SCRUM methodology. Additionally, this implementation is within the Federal Government and certain "things" we must do (by law and/or policy) are very non-agile and I am interested in learning more about how to accommodate thes without disrupting the team's agile approach. I will probably be bringing a "brief" that will describe how we are implementing this; it's intended audience being Rural Development's stakeholders: contract team, customers, and my management.
This turned into this Session: RemainingAgileWhileDealingWithBureaucraticNon-AgileProcesses
Somethings I Would Like to Learn
I am interested in discussing what automated tools/software folks use to support their SCRUM process (Sprint and Release Planning). I've been looking at several different packages and before I embark on any, I would like to hear what others have been using and what key features I should look for...
I am also VERY interested in finding training courses for my developers that integrate development tools into supporting agile development; I need courses that clearly show how to take a test-driven approach and show developers how to use these tools. The same rings true for continuous integration as well. Since we are predominantly a .Net shop, our plans are to use Nunit for unit testing, Selenium for functional (and load) testing, and CruiseControl.Net for continuous integration. We also use AxoSoft OnTime (issue tracking) and SourceGear Vault (source code management) with our Visual Studio environment.
My Experience
For the last 9 years, I have been customizing/implementing methodologies to be used with organizations. I would consider myself mildly successful, but each organization has had unique challenges that have prevented full-scale implementation of these methodologies. I now have a team that is extremely receptive to improvement and we have settled on a SCRUM-based methodology that we are in the process of implementing.
The Discussion
I'm interested in the discussion focusing on my experiences so far and learning about pitfalls that could come about that I haven't reached yet. While I understand SCRUM well from a learned sense, this is my first implementation of an almost pure SCRUM methodology. Additionally, this implementation is within the Federal Government and certain "things" we must do (by law and/or policy) are very non-agile and I am interested in learning more about how to accommodate thes without disrupting the team's agile approach. I will probably be bringing a "brief" that will describe how we are implementing this; it's intended audience being Rural Development's stakeholders: contract team, customers, and my management.
This turned into this Session: RemainingAgileWhileDealingWithBureaucraticNon-AgileProcesses
Somethings I Would Like to Learn
I am interested in discussing what automated tools/software folks use to support their SCRUM process (Sprint and Release Planning). I've been looking at several different packages and before I embark on any, I would like to hear what others have been using and what key features I should look for...
I am also VERY interested in finding training courses for my developers that integrate development tools into supporting agile development; I need courses that clearly show how to take a test-driven approach and show developers how to use these tools. The same rings true for continuous integration as well. Since we are predominantly a .Net shop, our plans are to use Nunit for unit testing, Selenium for functional (and load) testing, and CruiseControl.Net for continuous integration. We also use AxoSoft OnTime (issue tracking) and SourceGear Vault (source code management) with our Visual Studio environment.