Re: [scrumdevelopment] Launching a new team on Agile / Scrum
This intro could help.On Wed, Feb 1, 2012 at 2:59 PM, Don McGreal <mail@...> wrote:Hi Michael,Two quick and powerful techniques I use all the time are:Presto Manifesto (http://tastycupcakes.org/2009/06/presto-manifesto/) where teams effectively build their own manifesto, which we can then link to the agile manifesto values.Pocket-sized Principles (http://tastycupcakes.org/2010/01/pocket-sized-principles/) which is the 'cringe-y' technique you mentioned. It gets people discussing and thinking about the agile principles for themselves.Both are great ice breakers that can set the stage for an agile and scrum talk.
On Feb 1, 2012, at 6:13 AM, Michael Jones <michaelhardwinjones@...> wrote:
We're about to launch a new team on a new stream of work and we're going to be using Scrum.
Some team members (the minority) have used Scrum before. Also, some have worked with each other, others are newbies.
So my question is, before going into the first sprint planning, do you have any ideas on how to give a team a good introduction to Agile and get them into the right mindset?
E.g. would you deliver a presentation detailing the ethos and the process artefacts etc? How do you make it more interactive and get the team to internalise the values?
Is it reasonable to ask them to read the manifesto, scrum guide, etc?
(some ideas we discussed here were getting them to convert each point in the Agile manifesto to 3 key words, etc - a bit cringe-y perhaps, but good as an icebreaker)
Thanks for any ideas!
--Thanks & Best Regards,
Eng.Mohamed Ibrahim Omar
Center of Excellence in Information Assurance (CoEIA)
- Make it easy:
On 1 February 2012 13:37, Seyit Caglar Abbasoglu <scabbasoglu@...> wrote:
- kick off meeting with the reasons why you choose scrum
- train your people on scrum
- then do it
I'd say it might be very productive to start with stating your real expectations very clearly like "I'm expecting a working software continuously", or "I'm expecting a very low bug count", or "I'm expecting a continuous productivity increase". Then ask them "how they want to handle this expectations?".
And if they can't find reliable solutions to some of the expectations you give, or they believe some of those expectations are impossible to achieve, give them the resources that they can learn how to do that (documents, coaching, training etc..).
I believe with this approach there will be no resistance problems and it might create a lot more motivation compared to saying "We're going to use SCRUM and this is why!".