Poor Release Planning:
Too many maintenance releases not allowing adequate time to focus on new releases from dev/qa perspective.
Trying to cram too much into certain releases not allowing enough time to develop with quality and properly test.
Last minute changes to design without forethought of impact to development, testing, while making an effort to keep dates leading to poor quality in development and inability to properly test in a quality manner.
No Team:
Across the organization people don't work together for the most part. This is bad on many levels, but mostly communication across teams and projects.
Within teams people don't work together. You come in, sit down, do your work, leave. Few take time for lunch together as most feel they can't due to work load...adding to 0 sense of team. This can make it hard for new people, as training for new people is very poor. They can feel isolated. Everybody is so busy and overwhelmed with work, you feel bad asking questions.
Poor Management:
When ideas for improvement are brought forth to management they are set aside and no change ever takes place. Improvements are not prioritized due to managment being overwhelmed by the over promises to clients. The way things are done in 2017 are the same way things have been done for the last 5-10 years.
Team meetings consist of going over all the different release dates only and if people are on target to meet their dates. People rarely say no for fear of pushback
Work loads can be drastically different from person to person. They don't appear to be equitably spread.
Seems like meeting dates and how much you cram in is more important than a focus on quality product.
