Help shape the new book "Agile in the Bloodstream"
Agile 1.0 Versus Agile in the Bloodstream
I drew this while I was cooking dinner tonight to illustrate how I think Agile in the Bloodstream is different than most of Agile 1.0 being done today.
Your thoughts please.
Your thoughts please.
Comment
-
Comment by Daryl Kulak on May 6, 2009 at 10:46am - Yes, portfolio management, but not architecture.
-
Comment by Gene Johnson on May 6, 2009 at 9:29am -
Cool. My current client is even opposed to slightly tailoring - so, of course the teams are doing it covertly!
Is the book addressing items "outside of the project team", such as portfolio management, overall architecture, etc.?
-
Comment by Daryl Kulak on May 5, 2009 at 6:10pm
-
I am absolutely talking about this model "per project," not per organization.
I don't know if tailoring is the right term. It sounds like there is an assumption that 90% of the framework is great and we just need to tuck and trim here and there. I'd like the Agile Experimentation Lab to be where people are thinking it's all up for grabs.
Yes, Agile values would feed through this lab as well, good point. It's hard to argue that respect is a bad thing and we don't want it, but the meaning of respect in this instance could vary.
-
Comment by Gene Johnson on May 5, 2009 at 5:10pm
- Where would Agile values (feedback, communication, simplicity, courage, respect/humilty) be covered - seems at first blush to be just practice focused.
-
Comment by Gene Johnson on May 5, 2009 at 5:08pm
-
Cool. I think this should be your book cover.
Would "tailoring" of a practice for the organizationbe part of this? Is that what is meant by adaption? What about tailoring per project?
About
Badge
© 2009 Created by Daryl Kulak on Ning. Create a Ning Network!
You need to be a member of Agile in the Bloodstream to add comments!
Join this Ning Network