4 ms·

CMMI seems to be mostly a moneymaking scheme directed at business types with no skill. In contrast, Boeing used actually effective engineering disciplines.

by dscrd 12y ago

kamaal 12y ago
>>CMMI seems to be mostly a moneymaking scheme directed at business types with no skill. I beg to differ. I started my career working for a CMM level 5 software services company. One of the first shocks I received after I entered the web industry was total lack of discipline here. There was barely any documentation in the web industry- No way to keep a track of a impact of a particular change, no design notes, not even a change log of whom to call in case something goes wrong, in the CMM level 5 firm we would have think of roll back scenarios even before we worked on the code. In the web industry I saw, the idea of roll back planning didn't even appear to people. Yet the way I saw, a little documentation would have the whole team sane, and avoided more 50% of fire fighting we did on weekends. Rules are boring, but when something large is at stake it generally is worth the process.
- java-man 12y ago
  No one gets hurt if a web server goes down... right?
  - pjmlp 12y ago
    If it happens to monitor a life critical service...
    - ArkyBeagle 12y ago
      So don't do that. Ever.
- davidw 12y ago
  > Rules are boring, but when something large is at stake it generally is worth the process. It's all about finding the right place on the curve, and not being behind it. Add huge amounts of process to most web projects, and yeah, they might turn out a bit better, but they'll cost too much for what the customer wants to pay. You're right though in that too many web projects have virtually no process or rules, and that's not good either.
- jacquesm 12y ago
  On the web we have decided to painfully re-learn all the lessons from the last 40 years, only with in-concistent output devices.
- ExpiredLink 12y ago
  That's why Agile was invented. It codified the existing practices and redefined them as virtues.
  - Pxtl 12y ago
    Deployment is not development. You can do a lightweight development process and a heavyweight deployment process. At my company we manage our development with a scrum-ish approach but getting anything into production requires an ITIL change.
  - deleted 12y ago
    [deleted]

CMMI seems to be mostly a moneymaking scheme directed at business types with no skill. In contrast, Boeing used actually effective engineering disciplines.

by dscrd 12y ago

CMMI seems to be mostly a moneymaking scheme directed at business types with no skill. In contrast, Boeing used actually effective engineering disciplines.

kamaal 12y ago

>>CMMI seems to be mostly a moneymaking scheme directed at business types with no skill. I beg to differ. I started my career working for a CMM level 5 software services company. One of the first shocks I received after I entered the web industry was total lack of discipline here. There was barely any documentation in the web industry- No way to keep a track of a impact of a particular change, no design notes, not even a change log of whom to call in case something goes wrong, in the CMM level 5 firm we would have think of roll back scenarios even before we worked on the code. In the web industry I saw, the idea of roll back planning didn't even appear to people. Yet the way I saw, a little documentation would have the whole team sane, and avoided more 50% of fire fighting we did on weekends. Rules are boring, but when something large is at stake it generally is worth the process.

java-man 12y ago
No one gets hurt if a web server goes down... right?
- pjmlp 12y ago
  If it happens to monitor a life critical service...
  - ArkyBeagle 12y ago
    So don't do that. Ever.
davidw 12y ago
> Rules are boring, but when something large is at stake it generally is worth the process. It's all about finding the right place on the curve, and not being behind it. Add huge amounts of process to most web projects, and yeah, they might turn out a bit better, but they'll cost too much for what the customer wants to pay. You're right though in that too many web projects have virtually no process or rules, and that's not good either.
jacquesm 12y ago
On the web we have decided to painfully re-learn all the lessons from the last 40 years, only with in-concistent output devices.
ExpiredLink 12y ago
That's why Agile was invented. It codified the existing practices and redefined them as virtues.
- Pxtl 12y ago
  Deployment is not development. You can do a lightweight development process and a heavyweight deployment process. At my company we manage our development with a scrum-ish approach but getting anything into production requires an ITIL change.
- deleted 12y ago
  [deleted]