Re: [leanagile] Re: [scrumdevelopment] Re: Can FDD be the first step towards agility ?
- On 12/13/11, Adail Muniz Retamal <adail.retamal@...> wrote:
> I don't know why is this thread being cross-posted, but as I'm an FDDHello Adail,
> practitioner for 8 years I agree with the initial proposition to use FDD as
> a transition step towards Agile, and I completely disagree with Andrew's
> claim that FDD has "almost disappeared".
I am not saying that FDD is not good...The only thing I am saying is
that it has become rare to find a lot of developers/experts with FDD
Just by looking at all the job advertisements, how many would you say
there are mentioning FDD and how many would you say there are
All the best,
Author of Scrum in Action, Agile Project Management and Development in
and of "Business-Driven IT-Wide Agile (Scrum) and/or Kanban (Lean)
Implementation" (reviewed and upcoming)
> FDD doesn't have a marketing organization behind it to try and make it
> popular, but nevertheless it is constantly being quoted in books, articles,
> presentations and talks.
> And don't forget that David Anderson, the proponent of Kanban for software,
> is still an FDD enthusiast. In fact, FDD already used some Kanban concepts.
> Many teams find FDD very attractive for different reasons, and maybe the
> fact that it's not so popular can play an important role in this...
> Strategic weapons are usually secrets... ;)
> Popularity and effectiveness are not always correlated.
> Adail Retamal
> Sent from my iPhone
> On 14 Dec, 2011, at 11:59 AM, Andrew Pham <andrewpham74@...> wrote:
>> On 12/8/11, John Voris <john.voris@...> wrote:
>> > I echo K.V.M. remarks. This is where LEAN thinking can help. There are
>> > equivalent terms in LEAN and plain Agile . . . that can move the
>> > transition
>> > along.
>> > Instead of Sprint, use the word Iteration.
>> > Instead of Daily Scrum, use the words Daily Meeting.
>> > How you structure your Iteration and Daily Meeting, if not actually
>> > Scrum,
>> > is none the less probably better than what you were doing before, and
>> > ANY
>> > small change promotes the mindset that "Hey, our team, our processes,
>> > our
>> > (fill in the blank) CAN change". "And we are being listened to, and we
>> > are
>> > involved."
>> > That is how I push FDD (more like insidiously introduce FDD) on a small
>> > scale in my non-Agile workplace.
>> >> Another basic problem was changing the mindset as you said...it would
>> >> become even more difficult if the team started using jargon like
>> >> "Sprint",
>> >> "Daily Scrum", etc..
>> >> So we first got FDD, introduced the same concepts gradually without
>> >> formally giving out their names, and then after around 8 months or so,
>> >> we
>> >> could make the transition to Scrum.
>> I have nothing against FDD but it has almost disappeared
>> nowadays...This is why I would rather see teams use Scrum or the
>> generic Agile rather something for which it will be difficult to find
>> Just a simple food for thoughts...
>> Author of Scrum in Action, Agile Project Management and Development in
>> the Real-World
>> and of "Business-Driven IT-Wide Agile (Scrum) and/or Kanban (Lean)
>> Implementation" (reviewed and upcoming)