6 ms·

Nah... Lightweight processes were discussed as alternatives to waterfall way back in the 90s during my software engineering courses. "Rapid application developm

Nah... Lightweight processes were discussed as alternatives to waterfall way back in the 90s during my software engineering courses. "Rapid application development" and RAtional unified process were the "hot" lightweight methodologies when I started work in 1996. Scrum has been with us since 1995.

jacques_chester 13y ago
I'm not sure if you're aware of this, but when the Agile Manifesto was signed, a giant red button was pressed that reset the entire industry's memory. All that existed before 2001 was waterfall. Nothing else. Just waterfall. Only waterfall. You are mistaken in thinking that iterative delivery, spiral models, joint application development, daily build-n-smoke, test harnesses or any such practice or technology existed previously. Then in 2001, Agile sprung fully-formed from the brow of Zeus and saved us. Agile has no predecessors whatsoever and completely invalides decades of careful observation, discussion and investigation by generations of software developers and managers. All books and articles published before 2001 can be safely ignored, and nothing can be learned therefrom.
KevinEldon 13y ago
Agree, no debate about when you might have managed agile teams... could be you're Ken Schwaber (yeah, had to look up his name), but it then begs the 2nd question I raised... why would you want to do a startup? If you have 12+ years of experience with what is now a very hot process why, why?, WHY? would you want to work at a startup? A VP role doesn't sound like a C role. It doesn't sound like a really big equity play. You're not going to be a founder w/ a big payout (probably). So why do it? I'm repeating myself. It really doesn't matter at all... someone will apply or they will not and the company will hire the right person or they will not... you and I will go along with our lives just fine.
- el_fuser 13y ago
  I think you're overestimating how hot of a skill that actually is... But even if you could make "boatloads" of cash consulting, not everyone desires the road warrior lifestyle that goes along with consulting.

jacques_chester 13y ago

I'm not sure if you're aware of this, but when the Agile Manifesto was signed, a giant red button was pressed that reset the entire industry's memory. All that existed before 2001 was waterfall. Nothing else. Just waterfall. Only waterfall. You are mistaken in thinking that iterative delivery, spiral models, joint application development, daily build-n-smoke, test harnesses or any such practice or technology existed previously. Then in 2001, Agile sprung fully-formed from the brow of Zeus and saved us. Agile has no predecessors whatsoever and completely invalides decades of careful observation, discussion and investigation by generations of software developers and managers. All books and articles published before 2001 can be safely ignored, and nothing can be learned therefrom.

KevinEldon 13y ago

Agree, no debate about when you might have managed agile teams... could be you're Ken Schwaber (yeah, had to look up his name), but it then begs the 2nd question I raised... why would you want to do a startup? If you have 12+ years of experience with what is now a very hot process why, why?, WHY? would you want to work at a startup? A VP role doesn't sound like a C role. It doesn't sound like a really big equity play. You're not going to be a founder w/ a big payout (probably). So why do it? I'm repeating myself. It really doesn't matter at all... someone will apply or they will not and the company will hire the right person or they will not... you and I will go along with our lives just fine.

el_fuser 13y ago
I think you're overestimating how hot of a skill that actually is... But even if you could make "boatloads" of cash consulting, not everyone desires the road warrior lifestyle that goes along with consulting.