Why So Long To Release the Apple Watch?

Developers need watches. Developers are the ones that can't keep secrets :o) It is also pretty hard to beta test a watch in the real world world without going into the real world. At some point you have to go public. Of course there are other reasons, like some issue with production (odd the demo units at event were true demo units), but these other issues are just as likely. Even with build issues, you still need to get the watches that do work out into the world to see what else breaks.

Musings of the Sorry State of Developer Accountability

Things I see...

5 minute change takes three days.
Screens developed don't look like screens delivered.
Data developed is only marginally like data specified.
Developers concentrate on code, not understand what they are coding and why.

It all falls down to this: Developers don't take the time to plan, they just code and make things up rather than understand why, create a plan, execute and validate.

Why is this happening? Management... But that's just pointing fingers. Management has not really caused a problem. Yes management wants it right now. The problem is that programmers are fighting for their jobs and feel like they must do everything that management says. There is no give and take. There is no negotiation. Programmers don't think and push or pull to get it right, they just do what management says and the blame customers/mangers for being unreasonable and causing the errors.

This is akin to war crimes. Really. Sorry. I just did what my superior said. I am but a soldier and not responsible for the crimes of my superiors.

Projects fail, applications crash, customers complain, data is corrupted, core capabilities don't exist or are so wrong that they are so poorly executed that they can't even be compared to wrong, let alone close to right.

Nothing can fix this but personal responsibility and pride in your work. Agile, Scrum or any other process is useless. If you can't fight for doing it right, please go home.