Wow - Many years ago when I took Fortran with punch cards on an IBM 370, I wondered if I should pursue this programming thing as a career.
After reading these posts, I guess I'm fortunate that I didn't. I spent enough time in little office cubicles to know it is not nourishing for your soul. So then I looked up this Agile thing. The long description follows:
Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods or Agile processes generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto. The Manifesto was developed by a group fourteen leading figures in the software industry, and reflects their experience of what approaches do and do not work for software development. Read more about the Agile Manifesto. Did you know thatAgile can also be applied to hardware projects? Learn about cPrime’s revolutionary Agile for Hardware framework.
I know I wouldn't like it. It has cost, schedule, quality, pert charts, deadlines, overtime, stress and inherent BS written between the lines. It sounds like they break the jobs into little pieces that you perform that give you little or no job satisfaction and sell you on the story that you are part of a greater team. The iterative thing is the best. It's cut and try. Keep hacking at it until it works.
Per your entries, you guys all sound so happy when you get away from that software assembly line environment. I'm glad I left the punch cards years ago.