Comments on: Agile Anyone? http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/ for f in *;do echo | sed 'i\rtc' >> $f;done; java programming et al Thu, 19 Jan 2012 04:32:32 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Priyatam http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-39 Priyatam Tue, 09 Jan 2007 06:23:17 +0000 http://reverttoconsole.com/archives/62#comment-39 Called Uncle Louie, he's busy fixing his Guitar. Btw Uncle Sam says Agile works for him :) Called Uncle Louie, he’s busy fixing his Guitar. Btw Uncle Sam says Agile works for him :)

]]> By: eokuwwy http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-38 eokuwwy Fri, 05 Jan 2007 14:34:53 +0000 http://reverttoconsole.com/archives/62#comment-38 Give uncle Louie a call. He might be able to help. Give uncle Louie a call. He might be able to help.

]]> By: eceppda http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-37 eceppda Thu, 04 Jan 2007 23:39:37 +0000 http://reverttoconsole.com/archives/62#comment-37 Ok, so getting back to my question in the post... So could you see a one-man agile show happening? Would it be a useful methodology to use to gain control over the development cycle or manage ineffective managers with? I want something to bring more order to this mess of a development initiative I'm in right now. Any resources for agile you've found useful? Ok, so getting back to my question in the post…
So could you see a one-man agile show happening? Would it be a useful methodology to use to gain control over the development cycle or manage ineffective managers with?
I want something to bring more order to this mess of a development initiative I’m in right now.
Any resources for agile you’ve found useful?

]]> By: eokuwwy http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-36 eokuwwy Thu, 04 Jan 2007 17:15:11 +0000 http://reverttoconsole.com/archives/62#comment-36 Instead of "I hate change", I'm more of a "Let's do what we can to minimize unnecessary changes" kinda guy. If that incorporates some agile, fine, if not, fine. I agree that nothing is right or wrong. Everything is situational. I'm just not a fan of idiot managers coming in and saying "We HAVE to use this new methodology, because I read an article in e-week and it sounds great." Instead of “I hate change”, I’m more of a “Let’s do what we can to minimize unnecessary changes” kinda guy. If that incorporates some agile, fine, if not, fine.

I agree that nothing is right or wrong. Everything is situational.

I’m just not a fan of idiot managers coming in and saying “We HAVE to use this new methodology, because I read an article in e-week and it sounds great.”

]]> By: Priyatam http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-35 Priyatam Thu, 04 Jan 2007 16:09:40 +0000 http://reverttoconsole.com/archives/62#comment-35 There is nothing right or wrong! Agile suits a different set of people, environment, nature of project. For instance for a large onsite-offshore development Agile methodology would be extremely difficult to incorporate, thats why one relies heavily on processes and larger iterations with upfront A&D. For smaller teams and technically challenging projects where the Requirements gathering can be impossible in well-defined phases, developers are experienced - Agile would prolly suit the best fit. One more thing about Agile is that the whole paradigm shifts from "I hate changes Vs I know I will change tomorrow" :) You write a test & code and you very well are prepared with a mindset you will refactor it very soon! There is nothing right or wrong!

Agile suits a different set of people, environment, nature of project. For instance for a large onsite-offshore development Agile methodology would be extremely difficult to incorporate, thats why one relies heavily on processes and larger iterations with upfront A&D.
For smaller teams and technically challenging projects where the Requirements gathering can be impossible in well-defined phases, developers are experienced – Agile would prolly suit the best fit.

One more thing about Agile is that the whole paradigm shifts from “I hate changes Vs I know I will change tomorrow” :)

You write a test & code and you very well are prepared with a mindset you will refactor it very soon!

]]> By: eokuwwy http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-34 eokuwwy Thu, 04 Jan 2007 14:54:32 +0000 http://reverttoconsole.com/archives/62#comment-34 Why don't you just shell out a couple of grand and get your team to attend an Agile "retreat?" You guys can sing Kumbaya and hold hands while pair-programming. OK, well that sums up my feelings on the matter. Actually, I do like some aspects of Agile, and I can definitely see how it is a relief after working within a CMMi environment. I prefer customized development methodologies that are developed over time through trial and error. And maybe they borrow pieces from the Agile or CMMi doctrine, and maybe they don't. What I HATE, is some big-wig idiot coming in, when things are already running pretty well, and just says "We need to drop all of this and re-do everything because it's not good enough." And then all of the sudden, you have to start over. Everyone needs to adapt to th e new changes, which are sometimes quite drastic, add tons of overhead, and are often completely unnecessary, and EXPENSIVE! It would have been easier and much more efficient to just fine-tune the existing processes and methodology. Just because a process is formally recognized doesn't mean it is a good choice for a given development group. This really just amounts to dilbertization. That's all it is. Abandon your posts! RTC! Why don’t you just shell out a couple of grand and get your team to attend an Agile “retreat?”

You guys can sing Kumbaya and hold hands while pair-programming.

OK, well that sums up my feelings on the matter. Actually, I do like some aspects of Agile, and I can definitely see how it is a relief after working within a CMMi environment.

I prefer customized development methodologies that are developed over time through trial and error. And maybe they borrow pieces from the Agile or CMMi doctrine, and maybe they don’t.

What I HATE, is some big-wig idiot coming in, when things are already running pretty well, and just says “We need to drop all of this and re-do everything because it’s not good enough.” And then all of the sudden, you have to start over. Everyone needs to adapt to th e new changes, which are sometimes quite drastic, add tons of overhead, and are often completely unnecessary, and EXPENSIVE! It would have been easier and much more efficient to just fine-tune the existing processes and methodology.

Just because a process is formally recognized doesn’t mean it is a good choice for a given development group.

This really just amounts to dilbertization. That’s all it is.

Abandon your posts!

RTC!

]]> By: Priyatam http://www.reverttoconsole.com/blog/con-insulting/agile-anyone/comment-page-1/#comment-33 Priyatam Thu, 04 Jan 2007 03:24:43 +0000 http://reverttoconsole.com/archives/62#comment-33 I recently shifted my mindset from a cmm level 5 process to a agile workshop and let me tell you, agile methodology is a breather! In less than 2 months we could show to the client 2 complete use cases end-end (happy day flow) with an integration point to ESB, coding in Spring MVC (everything had to be learnt) on the fly. We have a domain driven, TDD approach; Of course the caveat is we lose on documentation but this is something we can take up ongoing as a deliverable rather than an upfront artifact. For smaller projects, where the requirements are not way too complex but the technology is, agile is the way to go because no matter what - <em>Nothing is rewarding than working software!</em> <strong>NOTHING</strong>. Would you like to show to your client a working software in 8 small releases with continuous rework and feedback or 2 huge releases with the probability of huge disappointment and overloaded documentation? I recently shifted my mindset from a cmm level 5 process to a agile workshop and let me tell you, agile methodology is a breather!

In less than 2 months we could show to the client 2 complete use cases end-end (happy day flow) with an integration point to ESB, coding in Spring MVC (everything had to be learnt) on the fly. We have a domain driven, TDD approach; Of course the caveat is we lose on documentation but this is something we can take up ongoing as a deliverable rather than an upfront artifact.

For smaller projects, where the requirements are not way too complex but the technology is, agile is the way to go because no matter what – Nothing is rewarding than working software! NOTHING.
Would you like to show to your client a working software in 8 small releases with continuous rework and feedback or 2 huge releases with the probability of huge disappointment and overloaded documentation?

]]>