Pros
Some exposure to different stages of the software development process. Opportunity to work alongside experienced developers and tech teams, although leadership often holds back the potential for growth.
Cons
The Business Analysis (BA) team is a major bottleneck. Their requirement gathering is often unclear and riddled with mistakes, forcing the development team to redo work continuously. Frequently, requirements change without proper notice, leading to confusion, delays, and rework. This lack of clear communication makes it difficult for developers to move forward with confidence. The BA team’s Software Requirements Specifications (SRS) are often incomplete or inaccurate, and instead of taking responsibility, the team shifts the blame onto others when issues arise. Leadership within the BA team seems more focused on internal politics and creating confusion between departments than addressing real business needs. This leads to a vicious cycle of project delays, with work often getting undone and redone—ultimately extending project timelines indefinitely. The constant shifting of requirements is a significant cause of stress and burnout among developers, as we find ourselves revisiting the same issues over and over without any resolution. Lack of coordination between the BA team and other departments makes it difficult to maintain consistent progress, and the development team ends up carrying the burden of missed deadlines and poor planning. Team morale suffers because the blame is continually shifted to other departments (especially development) instead of addressing the core issue: poorly defined and constantly changing requirements.