Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 3
    Whose decision was it to form this team and how did they justify the business case for its existence? i.e. what business value do they want from that team? what's the team's overall objective or mission statement as far as the business/stakeholders are concerned? It sounds like there's something missing in terms of overall direction and project ownership. Commented Sep 14, 2022 at 6:26
  • Or a lack of communication between the organization and teams. If there's such a thing as a test automation architect, then the company is making a bid or an investment on the subject. The organization cannot leave the Test Automation Team alone in the wild and hope for the best. I have seen the very same thing with QA Team. Companies build QA teams and they expect all other teams to stop working on whatever they are working on to adopt something they don't know why and where it comes from and probably no one is willing to pay the extra cost of the early adoption and the learning curve. Commented Sep 14, 2022 at 8:13
  • 1
    Red flags pop up reading this post. I see responsibilities scattered to all the wrong places, creating more problems than they could possibly solve. There are problems alright but I don't think the big ones are at the development team level. Commented Sep 14, 2022 at 11:02
  • Things like code reuse and technical dept are internal team matters. Creating a non-coding team to evaluate these things is not going to be helpful. Commented Sep 14, 2022 at 11:08