Charles & Wouter,
Thank you for the book recommendations - I have read some of Cohn's work, but not that book. And I haven't read anything by Larman or Vodde yet.
I'll definitely have to check these out.
| @wavle < http://twitter.com/#!
--- In firstname.lastname@example.org, Wouter Lagerweij <wouter@...> wrote:
> Hi Mark,
> Welcome to the group!
> A belated reply from me, on the scaling issue, but since no-one has
> mentioned the excellent 'Scaling Lean and Agile' books by Craig Larman and
> Bas Vodde. They have a sample chapter available on-line on Craig's website:
> Reading that chapter on Feature Teams already should give you some great
> ideas on how to set-up your teams. And a desire to buy those books:-)
> On Tue, Mar 20, 2012 at 2:39 AM, Mark Wavle <mark@...> wrote:
> > **
> > Hello! I just joined the group in the past couple weeks and wanted to
> > introduce myself...
> > I'm a consultant for Cardinal Solutions, working in Cincinnati (and SO
> > happy my Ohio Bobcats are in the sweet 16!).
> > A BA by training and passion, I also have a love for testing and lighter
> > technical things (SQL, HTML, shell scripting). I joined a Scrum team over
> > three years ago and, since our original Scrum Master left, have grown into
> > the Scrum Master role. I just passed the PSM I yesterday. :)
> > I greatly enjoy the smaller planning cycles of Scrum, especially the daily
> > plan, and I love that I can contribute all of my skills (including
> > planning, coordinating, facilitating, testing, and those light technical
> > skills, too) to bring value to our users. Conversely, I get so excited when
> > other development team members who have a heavy technical background ask
> > excellent requirements questions. Collaboration is an amazing thing - I'm
> > so happy we're not restricted to the traditional silos! We add so much more
> > value working closely together than we would throwing documents over the
> > wall at each other.
> > I'm struggling with the expansion of Scrum, as it seems like it will be
> > challenging to split the team in two when the time comes...maintaining a
> > consistent sizing scale, coordinating our Sprint cadences, helping each
> > team individually rally to produce high-value work, and yet maintain
> > high-quality output together. Additionally, there will be some loss of
> > productivity as there will be a bit more overhead in coordination between
> > the teams that our Product Owner will be paying for.
> > I have enjoyed the discussions thus far; the questions and ponderings have
> > made me realize that I'm not alone on the journey, and I have gained great
> > insights already. I look forward to returning the favor based on the
> > experiences I've had.
> > Thanks!
> > Mark
> Wouter Lagerweij | wouter@...
> http://www.lagerweij.com | @wouterla <http://twitter.com/#!/wouterla>