Why does everything take so long?

[Winterclaw]

Why things take so long? Typically in a larger company you have a number of checks and balances and a certain amount of inertia to overcome.

1. Someone has a proposal
2. It gets critiqued
3. It eventually gets approved or not
4. Someone works on the design
5. The design gets critiqued
6. The design gets approved
7. Someone starts coding
8. If there is a snag in coding it has to be worked around.
9. As it is coded, people are asked if this is a good design or works (if you are a good company, you do hallway usability testing)
10. The coding is finished and sent to QA.
11. QA tests it, makes comments, submits bugs, and if you've got a good company, suggests changes.
12. It goes back to coding and design perhaps.
13. The fixes/changes are done and retested.
14. Do this until QA is happy or someone tells them to shut up.
15. The update happens.

It's a long process. Sometimes you've got multiple departments working together. Sometimes the coding breaks something else. Sometimes the code doesn't have any comments and you are forced to put together what's going on. Sometimes you are in the middle of one thing and something more important gets dropped on your desk.

[Cairdeas]

Why things take so long? Typically in a larger company you have a number of checks and balances and a certain amount of inertia to overcome.

1. Someone has a proposal
2. It gets critiqued
3. It eventually gets approved or not
4. Someone works on the design
5. The design gets critiqued
6. The design gets approved
7. Someone starts coding
8. If there is a snag in coding it has to be worked around.
9. As it is coded, people are asked if this is a good design or works (if you are a good company, you do hallway usability testing)
10. The coding is finished and sent to QA.
11. QA tests it, makes comments, submits bugs, and if you've got a good company, suggests changes.
12. It goes back to coding and design perhaps.
13. The fixes/changes are done and retested.
14. Do this until QA is happy or someone tells them to shut up.
15. The update happens.

It's a long process. Sometimes you've got multiple departments working together. Sometimes the coding breaks something else. Sometimes the code doesn't have any comments and you are forced to put together what's going on. Sometimes you are in the middle of one thing and something more important gets dropped on your desk.

This is Correct.

I work for a Healthcare EMR company. We have a massive Program already designed/built/and in production for the last two years, but the vender has proven to be unable to maintain the level of development we need.

We've instigated taking on a new vender to design us a new UI for our whole database.

Its been approximately a year and a half since we first contacted them and as far as I've been informed they haven't even started coding the new UI. Its been all up contract negotiations and designing and "Drawing" the UI so we know what it might look like.

We are not even expecting the Basic model to be functional for another year. Then the full functional model to be ready in 3 years.

And all it is, is a UI that lets you keep records of Doctor Patient Visits and the effects of wound management on a wound over time.

[BelgianRofl]

This is Correct.

I work for a Healthcare EMR company. We have a massive Program already designed/built/and in production for the last two years, but the vender has proven to be unable to maintain the level of development we need.

We've instigated taking on a new vender to design us a new UI for our whole database.

Its been approximately a year and a half since we first contacted them and as far as I've been informed they haven't even started coding the new UI. Its been all up contract negotiations and designing and "Drawing" the UI so we know what it might look like.

We are not even expecting the Basic model to be functional for another year. Then the full functional model to be ready in 3 years.

And all it is, is a UI that lets you keep records of Doctor Patient Visits and the effects of wound management on a wound over time.

Dang. FFXIV's fucked.

[Moth]

Dang. FFXIV's fucked.

consequences will never be the same.

[Visch]

consequences will never be the same.

Ya dun goof'd.

[Renshi]

I guess that we can stop... uh... "beating a dead horse" and simply wait them for an update.
And drop that "waiting painfully" since there's always something to do while waiting.

[BelgianRofl]

I guess that we can stop... uh... "beating a dead horse" and simply wait them for an update.
And drop that "waiting painfully" since there's always something to do while waiting.

April 19th, a lot of us are finding a new horse. The choice is Yoshi-P's.