What your talking about matches my complaints exactly. I dont understand.
Developers are almost never included in those stages. Your given designs that have already been completed. Then you "make them happen", you have no input in the designs because they have already been designed and signed off. They only care about the speed of implementation, not quality.
Agile means that requirements can be more easily changed from feedback in process.
Pictures = design and user experience documents.
Most product based companies I've worked for means, I actually have input into almost everything around the product. If I feel something is not a great design or is difficult to implement I can change that as I go along. Can't do that in waterfall
> "Developers are almost never included in those stages."
That's not been my experience. I've seen business analysts working closely with developers to scope out what's needed and find the the best way forward, before the coding is due to start. For all the the apparent negatives of waterfall, I've seen that it can work quite well, when it's used correctly.
Developers are almost never included in those stages. Your given designs that have already been completed. Then you "make them happen", you have no input in the designs because they have already been designed and signed off. They only care about the speed of implementation, not quality.
Agile means that requirements can be more easily changed from feedback in process.
Pictures = design and user experience documents.
Most product based companies I've worked for means, I actually have input into almost everything around the product. If I feel something is not a great design or is difficult to implement I can change that as I go along. Can't do that in waterfall