• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is Agile is some thing new ? I don't think So !

 
Ranch Hand
Posts: 115
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello ,

I need to share my thoughts with you.

Am working on large scale bank environment and every one talk about Agile.

Do you use Agile ?
Who will attend next Agile training ? ect.

I read about Agile , I believe iterative approach to software delivery is not some thing new , we always doing this , we always breaking our projects down and deliver in phases.

So what is the new here ?
What exactly every one see and I can't !

Thanks in advance
 
Saloon Keeper
Posts: 27763
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There's "Agile" and there's "ongoing maintenance". The difference is that in ongoing maintenance, the application is "done", you get change requests, you update the application and it's "done" again when you put it into production.

In Agile, you don't have a "done" point. You have milestones, they are frequent and later milestones are shaped by user feedback from earlier milestones.

No, Agile isn't new. I used to do something similar as a systems support person back in the early 1980s where I'd do small projects, present them partially incomplete to users and, based on what they discovered, would update the design of the project before repeating as needed.

Then again, I did DevOps work years before they invented that term, too. It's one reason I don't get hired through HR departments. They're looking for things that "already exist."
 
Sheriff
Posts: 17644
300
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Tim Holloway wrote:In Agile, you don't have a "done" point. You have milestones, they are frequent and later milestones are shaped by user feedback from earlier milestones.


I have to disagree here. There is definitely a state of "done" when you practice Agile development. In fact, a good definition of "Done" is essential in most, if not all, agile methods, particularly if you're doing Scrum. Besides, contrasting "Agile" and "ongoing maintenance" is flawed. In fact, one Agile tenet is to get to "maintenance mode" as soon as possible because that's where most of the development effort lies. But this can be done with or without Agile; the question is, is the level of effort you put into maintenance sustainable? Agile practices help make it so.
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think you are both write on "done." Each feature absolutely has "done." There shouldn't be any doubt as to whether something like "advanced search by username" is working.

At the same time, I agree that the product itself doesn't have a definition of done that is known in advance. We have a promise to keep working on the highest value features first. (defined by product owner priority.)
 
Ranch Hand
Posts: 974
11
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ramy, in my opinion you are so very right!

I am more or less in a same situation. Also here scrum is being scrummed into a large organization.

In my opinion waterfall never existed in the way my manager thinks it did. Long before Agile and Scrum we tried to do automate testing, we tried to get intermediate releases out to demonstrate to the customer and get feedback. Maybe we did not have the tools you have now, but even in the nineties we were not that stupid that we would just flow down with the waterfall, if something planned in a previous stage just did not seem to work in practice.

In my company it also seems to be a 'sales card'. The manager here says scrum is revolutionary, and says to his boss, that with scrum you can get twice the throughput with half the people. Yeah they love that. Sounds pretty unrealistic. Just like praying five times a day with your head in the same direction, and then magically you will be happy and go to heaven. To me it seems like a new fad, sometimes with the same inflexibility and zealotry as a religion.

And while I say this, I do understand the benefits of some parts of agile. Just pushing it up to programmers like a schoolmaster, like submission, and saying it is totally new, that scrapes me. Of course agile might not be implemented in the same micro management way as they do it here, but nevertheless. It is overrated.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic