http://www.computerandvideogames.com/32 ... d-5-ideas/
... so you have liquid snake, solid snake and naked snake, who is also known as big boss, but who is different from the guy they call the boss. what the hell.
http://www.computerandvideogames.com/32 ... d-5-ideas/
... so you have liquid snake, solid snake and naked snake, who is also known as big boss, but who is different from the guy they call the boss. what the hell.
dude brings up the internet is for porn song
other dude says, "are the lyrics printable"
lmao
Quote from Rick_D[Blocked Image: http://i.imgur.com/p50eB.png]
lmaooooooooooo
thanks for the post furyo. it wasn't my intention to make it sound like you were a nutjob, but i had trouble finding the right words for asking the right question.
actually furyo do you have any plans to settle somewhere?
i ask more in the sense of how your mental state is and how traveling so much has affected it.
c&c: now made by bioware on bf3 engine
WAT
lol rick i don't understand how you're not a 9ft tall cyborg called GOD yet
you know, if only his stuff made sense, i think it'd actually be pretty enjoyable
quest added: save cain.
skjalg, really, stop bullshitting.
so if you took in the quote i used, he explains how everything is connected, and how, my friends, design isn't linear. he explains how you can go back and forth between cycles, which is very similar to agile development. the point i've been trying to make all this time, which you have been apparently misunderstanding deliberately, is that agile development is iteration and reflection based. i did even say that maybe it was restructured for creative heads, but that doesn't mean that this isn't the same fucking thing. then you take in details like management, or show concrete examples of other frameworks such a scrum, and expect all agile development to equate to that. agile development doesn't have a tight fucking definition, because agile development depends on how you want to structure your framework. the framework then may be more tightly defined, but there are so many frameworks out there that STILL derive from agile development.
and everyone is trolling again....
Quote from Pericolos0agile is more about development and this is more about design.As usual with you, this is a discussion of semantics (your loose interpretation of agile vs my very strict interpretation of the development methodology that it really is), and pointless lol.
you know, if there was actually something worthwhile in that article i'd be all over it, but it just seems to rehash what agile development, or perhaps, as a better example, prototyping does already. development is an abstraction of design, because in design you fucking develop your design as well, whether it is a creative process or not. besides that, agile development is a methodology that can be abstracted to be used in everything (as a testament to the modularity in software development).
i mean, fuck, look at this quote:
QuoteDesign is not linear, my friends, because it flows in four cycles. They are cycles, not steps, because you spin around inside them, picking up speed, excitement, and eventually, if it passes the test, you fling yourself out of that cycle to the next; where, like before, the process of building up speed continues and, most importantly, if you fail to maintain your speed, you fall back to a previous cycle — possibly out of the loop completely, which means, guess what, that idea didn’t make the cut.
compare it to:
[Blocked Image: http://i.imgur.com/ubJFY.jpg]
it's not exactly rocket science in spotting the similarities, i don't know why you are so vehement in saying that it ISN'T an agile development process, or why you bring shit like management and other details into it, when that is not even a necessary part of agile development. this tells me that you do not understand agile development processes more than anything else.
i'm trying to say that agile development isn't a management philosophy? if anything it is a framework for developing something, just like GRIP is. what that article essentially states is an agile development process, perhaps just optimized for creative heads. i mean the first drawing in itself describes an agile process that goes back and forth between iteration cycles. i don't think this is missing the point, i think it's just abstracting it to where the idea for it came from.
i don't think agile development cycles are the problem, i rather think that people do not understand how they should be used. the main reason for having agile development is to make the most of a reflective process. it seems you're having more of a problem with management of these processes than with the processes themselves. i never spoke of task lists or whatever other details you have in this, because agile development doesn't necessarily encompass them.
i look at valve's cabals and think of them as agile development processes, simply because they let many people iterate over the same chapters, levels, objects, etc. as far as i understood it, it is also a fairly unmanaged process, where people add whatever they think fits, and where they discuss about what they are doing in the individual cabals.