Need some answers.
- I am being asked to setup agile in totality.
I know to setup agile development team.
What I don't know is:
How to migrate VPs in agile higher mgmt.
Agile HR mgmt
Agile org policy...
Helps will be appreciated.
Thank you in adv.
AgreedOn Sep 26, 2012 3:53 PM, "Kevin Callahan" <kcallahan@...> wrote:
Hi Jessica, glad that you're speaking up a bit. Here's the scoop as I see it:First, this is the Scrum Dev email list, and while I believe that there is certainly room for discussions of other methodologies here, it remains the Scrum list: a place to discuss and deepen our understanding of developing software with Scrum.Second, anyone who has been around any agile discussions for any period of time knows that there is some charge between Kanban and Scrum, sometimes this is healthy debate, other times more dogmatic politicking. As with any hot topic on a limited communication medium such as email (different time, different place, no cultural cues, no non-verbal cues, etc, etc), a higher level of conversation is required. Generally speaking, I've seen this latter point as the baseline here: people are curious about each other, and helping each other solve problems.Third, knowing these first two things, the main posts you've made on this list are basically along the lines of lobbing inflammatory grenades: a vague link to an article or book *lacking any context of what you have found useful, interesting, or otherwise contributing to the healthy debate* and then typically have gone silent for some time, or in this case responding with what I can only interpret as contemptuous and defensive replies. This behavior is very similar to those lovely folks of the inter webs also known as trolls and does little toward contributing to a collaborative context, or otherwise moving these topics toward healthy debate.Finally, I have a personal request for you. If you wish to continue to post to this list topics that you know, or even slightly suspect, will generate controversy, that you give some context about *why* you're posting and *what* you find useful/interesting/thought provoking, and *how* it applies to your understanding of Scrum. This is pretty basic stuff; and it's the anti-pattern to trolling. Hence if you're not a troll, and not here just to stir the pot for the sake of stirring the pot, seems to me you would be willing to step up your game a bit and contribute, because honestly, I've been having a hard time finding a whole lot of value in much of what you have posted.Respectfully,kevin callahanOn Sep 22, 2012, at 5:02 PM, jessicacp23 wrote:
A response from the book author to Kurt's imagination on Kanbandev...
- - - - - - -
From: Andrew Pham <andrewpham74@...>
Sent: Saturday, September 22, 2012 10:43 AM
Subject: Re: [kanbandev] Quantifying the Effect of Using Kanban vs. Scrum - IEEE
So that you can see that Jessica is not the only one who likes my book, below is another excerpt from someone I had coached on a large Agile project for Well Fargo has said about my books as well:
- - - - - -
"As I am reading through the draft, I can see that this book is brilliantly weaving the whole intention of Agile and Lean. It helps the reader analyzing what is, and strategize what should be the most important values to your overall company. Reading this recalled my thoughts of the exercise you coached us through at Wells Fargo in San Antonio of taking the user stories and tying it back to the business values with some type of priority. "
- - - - -
On Sat, Sep 22, 2012 at 10:26 AM, Andrew Pham <andrewpham74@...> wrote:
First, my name is not Spam as you wrongly wrote. Second, you are also wrong to think that I am Jessica. No, I am not her and she is not doing any paid marketing activities for me. She obviously likes my books and that is her right. I do not think that you should prevent her or anyone from saying what they like to say. That is what we call freedom of speech in America.
Likewise, you should also learn to be humble enough not to judge people and spread your wrong assessment around as you have been doing. It practically makes me laugh when I saw that you thought that I am Jessica. What an imagination.
Due to my busy professional activities (for which I live and breath Agile and Kanban everyday), I do not have time to participate in any forum and this is why I did not know about all the wrong things you have been saying during all these times...
No hard feelings against you but please learn to show more humility and respect for other people's ideas and opinions and avoid making rushed and wrong judgments like in this case.
--- In firstname.lastname@example.org, Kurt Häusler <kurt.haeusler@...> wrote:
> Is Jessica on holiday? Or did the spam checkers start to recognise her?
> Seriously Andrew, this is not the way to promote your book.
> On 18 Sep 2012, at 15:20, quang7889 <quang7889@...> wrote:
> > There is a good and detailed comparison between Scrum, generic Agile and Kanban in the book below along the line of what Ron is talking about...
> > http://www.amazon.com/Business-Driven--Wide-Agile-Kanban-Implementation/dp/1466557486/ref=sr_1_1?s=books&ie=UTF8&qid=1347972751&sr=1-1&keywords=business+driven+It+wide+agile+implementation
> > The author of the above book is also the author of this book Scrum in Action below, which was used successfully with the author being the coach of the project team (from Vietnam, India and the USA) on a large Agile project with Wells Fargo a year ago:
> > http://www.amazon.com/gp/product/143545913X/ref=kinw_rke_tl_1
> > Quang
> > --- In email@example.com, RonJeffries <ronjeffries@> wrote:
> > >
> > > It seems to me that there are important things to be aware of, including:
> > >
> > > Scrum and Kanban are not the same kind of thing, so comparing them is really difficult. Like comparing milk and coffee. Think latte.
> > > Organizations improve when they pay attention to improvement. Paying attention using one framework is better than not paying attention using the other.
> > > Organizations improve more when they pay attention to the most important things needing improvement. Kanban and Scrum call attention to issues in a different order. One or the other may find a given organization's most important concerns sooner.
> > > Scrum and Kanban can be used together. Comparisons of the two are fraught. Latte again.
> > > Limiting WIP is part of why either might succeed. Scrum's limitation of WIP is different from Kanban's.
> > > However, single-piece flow commonly works better than multiple piece. This is interesting ...
> > >
> > > Ron Jeffries
> > > www.XProgramming.com
> > > If it is more than you need, it is waste. -- Andy Seidl
> > >