Regarding the StateAdvantage product:
Overall:
- Documentation is split in a million pieces all over the place
- The internal Product team does not really care if the services/implementation team is successful or not. They have no incentive to.
- Leadership relies on a "Break/Fix" mentality
- High turnover coupled with poor hiring choices
- Perpetually stressed out employees
- Arrogant and Aloof leadership
- Continuous confusion about what the "plan" is due to break/fix mentality, perpetual fire drills and direction from multiple sources.
- A "with us or against us" cult-like feel.
- Archaic HR policies that inhibit the company's ability to grow as fast as they need to.
- A "throw more bodies at the problem" or "work more hours" mentality is a core component of the culture at Connecture
For BAs:
- A newly appointed BA manager who bullies, has unrealistic expectations, little to no product knowledge and does not interact with the client by design.
- SCRUM Masters unfamiliar with how to be effective as a sub-prime vendor
- Exceptionally poor client expectation setting/management by leadership
- Mandatory evenings/weekend on-call schedule multiple weeks per month
- BAs are expected to have to give the client the bad news on scope and priority when leadership overpromises
- Lack of support from the internal Product team
- Overworked PMs, and cranky QA/Dev over the state of requirements and BA output.
- Constructive questioning can be seen as dissent or non-compliance
For Dev:
- Generally poor requirements documentation
- Continuous improvement efforts are obvious but tend not to stick
- Weekend and evening work required due to poor planning
- Last minute deadlines and scope changes
- Inefficient and cumbersome code merge processes due to low-grade product architecture
- Lack of knowledge mgnt causes constant re-learning
- Expect to be on-call multiple weeks per month evenings/weekends
- High BA turnover leaving requirements up to perpetual interpretation
- Lack of support from the internal Product team
- Capable but overworked technical manager
For QA:
- Often only DAYS to test a release, making the majority of testing ad-hoc
- Last minute scope decisions coupled with very high level requirements
- Expect to be on-call multiple weeks per month evenings/weekends
- High BA turnover leaving requirements up to perpetual interpretation
- Very little time and attention spent on QA needs overall