- This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- The forum ‘Other’ is closed to new topics and replies.
The forums ran from 2008-2020 and are now closed and viewable here as an archive.
hi,
AGILE, I found this:
http://en.wikipedia.org/wiki/Agile_software_development
what is agile proccess in web development
or
is it just in software development ?
I dont know, saw it in a job requirement, have no idea
It’s the development cycle they use
here’s a brief overview of it
http://en.wikipedia.org/wiki/Agile_Unified_Process#Disciplines
I’ve only ever seen stuff like this as beneficial instead of required
In short — it’s a way of managing/organizing a project. For example, a “normal” project cycle could be (chronologically):
Step 1: design team designs entire site
Step 2: back-end team codes entire site
Step 3: front-end team styles entire site
With Agile, it would be more like this:
Step 1: design team designs the front page of the site
Step 2: back-end team codes the front page of the site
Step 3: front-end team styles the front page of the site
Step 4: design team designs the store section of the site
Step 5: back-end team codes the store section of the site
Step 6: front-end team styles the store section of the site
Step 7: design team designs the account section of the site
Step 8: back-end team codes the account section of the site
Step 9: front-end team styles the account section of the site
etc. etc.
Personally, not a big fan of Agile to be honest. And it shouldn’t be something a coder should require for a job — it’s mainly the job of a project manager/scheduler to handle this type of stuff, coders should just follow the lead.
If you have no experience with this whatsoever, you’ll learn automatically.